Skip to content

Otel timeseries go missing #261

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

Open
phbnf opened this issue Apr 14, 2025 · 2 comments
Open

Otel timeseries go missing #261

phbnf opened this issue Apr 14, 2025 · 2 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@phbnf
Copy link
Collaborator

phbnf commented Apr 14, 2025

Image

From the logs:

"W0414 08:59:47.563558       1 handler.go:30] rpc error: code = InvalidArgument desc = One or more TimeSeries could not be written: timeSeries[0-106]: write for resource=generic_node{namespace:,node_id:,location:global} failed with: Points must be written in order. One or more of the points specified had an older start time than the most recent point."
@phbnf phbnf added the bug Something isn't working label Apr 14, 2025
@phbnf phbnf added this to the alpha milestone Apr 14, 2025
@phbnf
Copy link
Collaborator Author

phbnf commented Apr 14, 2025

After speaking with Al about this and digging a bit more into it, I come to the conclusion that this is because there are multiple tasks exporting the same metric, and Otel cannot make any difference between them. Unfortunately, I don't think that this is supported: GoogleCloudPlatform/opentelemetry-operations-go#946.

@phbnf
Copy link
Collaborator Author

phbnf commented Apr 14, 2025

In the meantime, it should be doable with a sidecar, I think it's just not supported yet in https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

2 participants