-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[processor/servicegraph] remove deprecated component #30149
[processor/servicegraph] remove deprecated component #30149
Conversation
|
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.
Need to update feature gate registry too https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/7286377802/job/19855077048?pr=30149
@songy23 i moved the flags from the processor to the connector.... not sure if i should have renamed them or not. maybe the code owners can weigh in on this @mapno @jpkrohling |
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.
Needs make generate-gh-issue-templates
|
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.
Thanks for taking this on this 🙏 Left a couple of comments.
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.
Making a file comment because I can't reference the lines I want.
IMO, naming should be migrated as well. So it'd be serviceGraphConnector
, newConnector
, etc.
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.
The tracesConsumer
can also be removed. It was used in the processor only.
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've updated the code to reflect this feedback. One more question what about the metrics generated by the component itself? Currently it looks like:
processor_dropped_spans
processor_total_edges
processor_expired_edges
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 personally would change them as well. The processor is deprecated, and my assumption is that those metrics as well.
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.
Having a connector emit metrics that have processor
in name is confusing in the long run, I agree those metrics should be renamed. I'd be fine with renaming them in a separate pull request though.
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.
A note on the renaming of the internal components - if I understand correctly, this is a refactoring (no change in behavior) and not needed to remove the Service Graph processor. I believe in future it's better to do it in a separate pull request. Makes the PRs smaller and easier to review.
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.
@astencel-sumo fair enough. i was moving the code from the processor over and needed to rename a few things to make it all work.
15b251a
to
339fc5b
Compare
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
339fc5b
to
183e212
Compare
8930949
to
c56e183
Compare
c9964e5
to
d953a6b
Compare
This component was replaced by the servicegraphconnector, which was a wrapper around the servicegraphprocessor. This PR moves the processor code into the connector component and removes the processor altogether. Note that as part of this PR I added the traces_to_traces support as it was supported by the processor before (with the development status). Fixes open-telemetry#30041 Fixes open-telemetry#26091 Signed-off-by: Alex Boten <aboten@lightstep.com>
Signed-off-by: Alex Boten <aboten@lightstep.com>
Signed-off-by: Alex Boten <aboten@lightstep.com>
Signed-off-by: Alex Boten <aboten@lightstep.com>
Signed-off-by: Alex Boten <aboten@lightstep.com>
Signed-off-by: Alex Boten <aboten@lightstep.com>
d953a6b
to
83ee263
Compare
This follows the comment from open-telemetry#30149 (comment) Signed-off-by: Alex Boten <aboten@lightstep.com>
This follows the comment from #30149 (comment) --------- Signed-off-by: Alex Boten <aboten@lightstep.com>
This PR adds tests which were previously added in open-telemetry#17350, but got removed in open-telemetry#30149.
This component was replaced by the servicegraphconnector, which was a wrapper around the servicegraphprocessor. This PR moves the processor code into the connector component and removes the processor altogether. Note that as part of this PR I added the traces_to_traces support as it was supported by the processor before (with the development status).
Fixes #30041
Fixes #26091