Add Almanac - observability package to streamline usability patterns#332
Merged
Conversation
oskardudycz
changed the title
oskardudycz
added
open telemetry
almanac
observability
enhancement
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The reason I'm adding this package is that I don't want to always depend on Otel and want the ability to export observability and OTel data to other places, for instance, logging tools (console, pino, Watson, etc.) and analytics (DuckDB, ClickHouse, etc.).
I also want to group usability patterns, as I want to use them without all the Otel bloat immediately.
We'll see if the idea stands the test of time, but here we go.
Eventually, it'll be moved to a dedicated repo, as it'll also be used in Pongo, but until the API settles, let's keep it here.
I took those changes more or less as they were from #324, restructuring the codebase to be more organised around abstractions.
The code will also need to be refactored to be more focused, but let's keep it moving, finally.