-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Update receiverhelper for requests that failed to be received #12802
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
Conversation
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
@gizas Are you still working on this? Or should it be marked as ready for review? |
@jade-guiton-dd I will try to fix the linting errors and will open it as ready for review. thanks for the ping |
Signed-off-by: Andreas Gkizas <[email protected]>
@jade-guiton-dd I think I have made some progress. I have made the choice to add a new flag additional to existing telemetry.newPipelineTelemetry otelcol --config=config.yaml --feature-gates=+telemetry.newPipelineTelemetry,+telemetry.distinguishDownstreamErrors Screenshot with some manual testsI have even built and run some manual tests and I can see e2e the metrics appear:![]() Let me know wdyt |
exporter/exporterhelper/internal/queue/persistent_queue_test.go
Outdated
Show resolved
Hide resolved
Signed-off-by: Andreas Gkizas <[email protected]>
No are not related to my changes. But are indirect refernces. See the links above. Ok I will also remove them. I agree will be cleaner |
…nder fg Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[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.
Looking pretty good, although there are still a few issues to fix. The go.mod
required versions are also still wrong.
Signed-off-by: Andreas Gkizas <[email protected]>
I'm surprised that test fails considering the feature gate should be disabled by default 🤔 |
Signed-off-by: Andreas Gkizas <[email protected]>
Looking at the contrib-tests currently running in CI, I don't see any failures for receiver/awsxrayreceiver. I'm wondering if you weren't testing against an older version of your code, with the incorrect logic in obsreport? |
Signed-off-by: Andreas Gkizas <[email protected]>
Indeed @jade-guiton-dd our comments crossed. I wrote it the comment for the contrib-tests before seeing yours to update the logic. So later I did the updates. (I saw some errors today but unrelated to our changes). I have fixed the lint errors and retriggered the CI. Let's see now |
Signed-off-by: Andreas Gkizas <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
@jade-guiton-dd do you think are we ready to merge? anything else missing? |
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 think we're about done, I just have a few more suggestions regarding documentation. Thank you for your patience with all these back-and-forths.
Co-authored-by: Jade Guiton <[email protected]>
Signed-off-by: Andreas Gkizas <[email protected]>
a3ff02b
otelcol_receiver_failed_metric_points was added upstream in open-telemetry/opentelemetry-collector#12802 and is enabled by default. This test is failing because it expected 17 metrics, but is now receiving 18.
* Update OpenTelemetry Dependencies to latest * Update test to account for new internal telemetry metric otelcol_receiver_failed_metric_points was added upstream in open-telemetry/opentelemetry-collector#12802 and is enabled by default. This test is failing because it expected 17 metrics, but is now receiving 18. * Same as 43d812b but for smart agent receiver teset --------- Co-authored-by: Curtis Robert <[email protected]>
Description
This is an ongoing work to add :
Link to tracking issue
Fixes #12207
Testing
Only added the integration tests.
Documentation
See updated receiver/receiverhelper/documentation.md