This repository was archived by the owner on Dec 3, 2025. It is now read-only.
Setup OpenTelemetry & our CI #1
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR adds support for OpenTelemetry based tracing, with automatic links between job creation, and processing. It also adds instrumentation to most db functions, except get_job, as that one seemed to be called a lot, so it felt a bit excessive. I've tried to follow the related OTel semantic conventions, which seems to be these: https://opentelemetry.io/docs/specs/semconv/messaging/messaging-spans/ But I'm open for using other conventions, and/or change which tags are exposed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of an ongoing issue in the GPT repository I need to debug why we suddenly stop processing events. I've tried to get information using PostgreSQL logs, pg_stat_ tables, tokio console, LLM analysis, reading a fuckton of docs myself, and I cannot figure it out.
Some time ago I created a PR in the library we use for worker processing ( leo91000#314 ) with support for OpenTelemetry, which, through traces, will give me a lot of useful information.
Ideally I would never need to fork the repo, but the maintainer seems a bit inactive. What I long for is something like resque for Rust. This seemed the best alternative I could find, and I liked that it was just using PostgreSQL, as that made it fit well within our existing infrastructure, and that it was based on a popular NodeJS library with the foundational SQL re-used, so that part had already been quite well tested and verified. A lot of projects in the Rust world just seems like they're made by one person in their spare time.