feat(haproxyinstance): promote Span-based synthesis rule to production - #3223
Open
gmanandhar-nr wants to merge 1 commit into
Open
gmanandhar-nr wants to merge 1 commit into
gmanandhar-nr wants to merge 1 commit into
Conversation
Add infra_haproxyinstance_otel_span rule that maps HAProxy OTel filter trace spans to the HAPROXYINSTANCE entity using the same host.id:haproxy.addr composite identifier as existing Metric rules. This enables distributed tracing relationships (CALLS) between application services and HAProxy. - Promote staging span synthesis rule to definition.yml - Remove definition.stg.yml (now identical to production) - Promote Span.stg.json test fixture to Span.json Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
entityBot
requested changes
Sep 6, 2026
entityBot
left a comment
entityBot
left a comment
Collaborator
There was a problem hiding this comment.
beep boop bop.
I have found some errors processing these changes:
- No valid, approved ARB ticket found in the PR description. This PR has to be reviewed by the API Review Board, please include a link to the ticket of that review in the PR description. Check how to start the process here or reach
#api-review-boardchannel in case of doubts
sseif-nr
reviewed
Sep 8, 2026
| # using the same host.id:haproxy.addr composite identifier as the Metric rules. | ||
| # This ensures traces and metrics resolve to the same entity. | ||
| # Requires: resourcedetection processor (adds host.id) + resource processor (adds haproxy.addr) | ||
| - ruleName: infra_haproxyinstance_otel_span |
Collaborator
There was a problem hiding this comment.
Is there a reason why this is the only rule that explicitly omits instrumentation.provider: opentelemetry?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is simply updating the staging rules to production!
Add infra_haproxyinstance_otel_span rule that maps HAProxy OTel filter trace spans to the HAPROXYINSTANCE entity using the same host.id:haproxy.addr composite identifier as existing Metric rules. This enables distributed tracing relationships (CALLS) between application services and HAProxy.
Relevant information
Api Review Board (ARB)
Pull requests with changes to this repository might need to be linked with an ARB ticket, which has to be approved before merging.
If you are an external contributor please contact New Relic Support.
What definition changes require ARB and which do not? Guide here.
If you are new to ARB process also check this.
ARB Jira ticket:
https://new-relic.atlassian.net/browse/NR-XXXX
Checklist
identifierwill be unique and valid.