-
Notifications
You must be signed in to change notification settings - Fork 238
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
feat(otelcol/connector/servicegraph): add virtual_node_peer_attributes
setting to the component
#879
base: main
Are you sure you want to change the base?
Conversation
…es` setting to the component Signed-off-by: hainenber <[email protected]>
docs/sources/reference/components/otelcol.connector.servicegraph.md
Outdated
Show resolved
Hide resolved
Co-authored-by: William Dumont <[email protected]>
Signed-off-by: hainenber <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
waiting for @clayton-cornell feedback on the doc before merging it |
docs/sources/reference/components/otelcol.connector.servicegraph.md
Outdated
Show resolved
Hide resolved
docs/sources/reference/components/otelcol.connector.servicegraph.md
Outdated
Show resolved
Hide resolved
docs/sources/reference/components/otelcol.connector.servicegraph.md
Outdated
Show resolved
Hide resolved
…telcol-connector-servicegraph
Co-authored-by: Paulin Todev <[email protected]> Co-authored-by: Clayton Cornell <[email protected]>
Co-authored-by: Clayton Cornell <[email protected]>
Signed-off-by: hainenber <[email protected]>
…telcol-connector-servicegraph
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I opened a PR upstream for this config option to be changed upstream. It would be better to update Alloy straight to the new config, so let's put the PR on hold for now to see if the upstream PR gets accepted.
All fine by me :D |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still in passive voice, but leaving it as it gets the technical point across.
@@ -107,6 +108,19 @@ Additional labels can be included using the `dimensions` configuration option: | |||
|
|||
When `metrics_flush_interval` is set to `0s`, metrics will be flushed on every received batch of traces. | |||
|
|||
`virtual_node_peer_attributes` is useful when an OTel-instrumented client sends a request to a service which is not OTel-instrumented. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`virtual_node_peer_attributes` is useful when an OTel-instrumented client sends a request to a service which is not OTel-instrumented. | |
`virtual_node_peer_attributes` is useful when an OTel-instrumented client sends a request to a service that is not OTel-instrumented. |
|
||
If no client span is found and `virtual_node_peer_attributes` is not an empty list, | ||
then the service span will be paired with a virtual node called `client="user"`. | ||
This can be useful when a client which is not OTel-instrumented (like a web browser) sends a request to an OTel-instrumented service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be useful when a client which is not OTel-instrumented (like a web browser) sends a request to an OTel-instrumented service. | |
This can be useful when a client that is not OTel-instrumented (like a web browser) sends a request to an OTel-instrumented service. |
@@ -107,6 +108,19 @@ Additional labels can be included using the `dimensions` configuration option: | |||
|
|||
When `metrics_flush_interval` is set to `0s`, metrics will be flushed on every received batch of traces. | |||
|
|||
`virtual_node_peer_attributes` is useful when an OTel-instrumented client sends a request to a service which is not OTel-instrumented. | |||
Normally, `otelcol.connector.servicegraph` wouldn't be able to pair the client span with a service span, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally, `otelcol.connector.servicegraph` wouldn't be able to pair the client span with a service span, | |
Normally, `otelcol.connector.servicegraph` wouldn't be able to pair the client span with a service span |
This PR has not had any activity in the past 30 days, so the |
PR Description
Add the virtual_node_peer_attributes setting to otelcol.connector.servicegraph. Thanks @erikbaranowski for creating the foundation already!
The default attributes are reduced to be identical to upstream
Which issue(s) this PR fixes
Closes #861
Notes to the Reviewer
PR Checklist