Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make parent trace names consistent between runs #23

Merged
merged 1 commit into from
Jul 10, 2024

Conversation

nsheaps
Copy link
Contributor

@nsheaps nsheaps commented Jul 10, 2024

With tracing in newrelic, groups are done via the name on the parent trace. With each run having a unique name (due to the run ID being unique each time), it makes it hard to use the traces and compare runs over time. If the previous functionality is desired by consumers of this action, it is easy enough to restore by updating the GHA_RUN_NAME environment variable, which is only used in the context of the name of the parent trace.

Screenshot 2024-07-09 at 9 38 52 PM

The top group of traces were collected by github.com/inception-health/otel-export-trace-action and feature very similar results. This change is necessary for us to replace that action with this one. (note the difference in the service name, which this action achieves better by naming it after the repo)

With tracing in newrelic, groups are done via the name on the parent trace. With each run having a unique name (due to the run ID being unique each time), it makes it hard to use the traces and compare runs over time. If the previous functionality is desired by consumers of this action, it is easy enough to restore by updating the GHA_RUN_NAME environment variable, which is only used in the context of the name of the parent trace.
@CLAassistant
Copy link

CLAassistant commented Jul 10, 2024

CLA assistant check
All committers have signed the CLA.

@dpacheconr dpacheconr merged commit cbe475a into newrelic-experimental:main Jul 10, 2024
1 check passed
@nsheaps nsheaps deleted the patch-1 branch July 10, 2024 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants