Smoke tests for distribution channel monitoring

Open
#96 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, java
Domain
ci-cd, observability, testing

Research direction

Start by reading .github/workflows/continuous-monitoring.yml and trace how the hard-coded Java agent version is downloaded from Maven Central. Define the distribution-channel smoke test and the binary metric it should produce; done means the workflow verifies the distribution and publishes that metric.

Written by the indexing model from the issue text.

Description

enhancement

Currently continuous-monitoring workflow uses wget to get the hard coded version of java agent from Maven Central. We should probably add a smoke test for distribution channel and set up a binary metric based on that distribution channel smoke test.

Dominant language
Java
Stars
46
Forks
20
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-xray-java-agent

All issues in aws/aws-xray-java-agent

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.