-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
Argo CD Agent: Agent and principal should integrate with opentelemetry
-
False
-
-
False
-
To Do
-
0% To Do, 100% In Progress, 0% Done
-
-
Epic Goal
- See https://github.com/argoproj-labs/argocd-agent/issues/119 for upstream description
- Slack thread containing my (jonathan) brief initial investigation: https://redhat-internal.slack.com/archives/C01RQH8KQ87/p1762189141681809?thread_ts=1762186008.219379&cid=C01RQH8KQ87
- High level sketch of the work required, would be:
- 1) Enabling opentelemetry in argo cd agent (probably by following upstream argo cd, see thread for links)
- 2) Determining what kind of data we want to generate from it. (I assume trace data, which is what Argo CD generates, but Jann seem non-committal?)
- 3) Generating that data (for example, Argo CD generates data by instrumenting grpc calls)
- 4) Manually test that the data is received as expected by opentelemetry (probably by sending it to red hat opentelemetry operator)
More Information on open telemetry:
- https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html-single/red_hat_build_of_opentelemetry/index#otel-collector-receivers
- https://www.youtube.com/watch?v=9kJbXXBvnrA
Definition of Ready
- The epic has been broken down into stories.
- Stories have been scoped.
- The epic has been stack ranked.
Definition of Done
- Code Complete:
- All code has been written, reviewed, and approved.
- Tested:
- Unit tests have been written and passed.
- Integration tests have been completed.
- System tests have been conducted, and all critical bugs have been fixed.
- Tested on OpenShift either upstream or downstream on a local build.
- Documentation:
- User documentation or release notes have been written.
- Build:
- Code has been successfully built and integrated into the main repository / project.
- Review:
- Code has been peer-reviewed and meets coding standards.
- All acceptance criteria defined in the user story have been met.
- Tested by reviewer on OpenShift.
- Deployment:
- The feature has been deployed on OpenShift cluster for testing.
- Acceptance:
- Product Manager or stakeholder has reviewed and accepted the work.