Closed spirrello closed 5 months ago
Interesting enough is that if I rerun the job it succeeds.
2024-01-17 16:45:24,297 INFO [job_logger] [main.py:171] [trace_id=257532a2e173c31f498e25ce2afc7d5c span_id=d95619dafa638749 resource.service.name= trace_sampled=True] -
2024-01-17 16:45:24,298 INFO [job_logger] [main.py:171] [trace_id=257532a2e173c31f498e25ce2afc7d5c span_id=d95619dafa638749 resource.service.name= trace_sampled=True] -
2024-01-17 16:45:24,299 INFO [job_logger] [main.py:171] [trace_id=257532a2e173c31f498e25ce2afc7d5c span_id=d95619dafa638749 resource.service.name= trace_sampled=True] -
All data sent to New Relic for pipeline: 74235
Terminating...
The error usually means the parent trace timestamp is incorrect format, can happen when pipeline hasn't finished. gitlab exporter -> needs to be run as part of your pipeline as triggered job more information here https://newrelic.com/blog/how-to-relic/monitor-gitlab-with-opentelemetry The reason it works when you re-run is because the json returned from gitlab api already contains the end timestamp(finished_at), so it's parsed correctly.
gitlab metrics exporter -> can be run on schedule outside your normal pipelines, as pipeline schedule or as standalone container
no activity for over 5 months, if you still having issues, please re-open
Hello,
I've tried versions 1.0.13, 1.0.14 and will probably continue down the list but I keep getting this error. Can you suggest a fix?
Here is how I'm running the container in my pipelines: