-
Notifications
You must be signed in to change notification settings - Fork 62
Open
Labels
enhancementNew feature or requestNew feature or requestsoftware-deliveryRelated to [coverage, deployment, dora, junit, measure, tag, trace]Related to [coverage, deployment, dora, junit, measure, tag, trace]
Description
Feature request description
We were trying to test out the correlate image functionality with our argocd deploys. However, service is inferred from the repo value in the image string, so it would be alot of work on our side.
We would need to
- change the base ECR repo name to update to be the service name, and update all references to this new value (e.g image builds, tagging, etc).
- We would also have to change all of our dashboards to stop embedding environment in our service names (i.e. we currently have
foo-bar-staging
,foo-bar-production
). Granted the environment in the service name is weird and on us, but I'm not sureenv
was available when we started using datadog. Regardless, this is a weird edge case.
Solution
If correlate-image
also took a service
as a parameter and used it as part of the glue to stitch argo deploys to repo/images, it would make our usage of the product a no-brainer. Since it's still in preview I was hoping this might be added.
Additional context
No response
Command
None
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestsoftware-deliveryRelated to [coverage, deployment, dora, junit, measure, tag, trace]Related to [coverage, deployment, dora, junit, measure, tag, trace]