-
Notifications
You must be signed in to change notification settings - Fork 604
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
Add an OpenTelemetry Collector for logs and metrics #4087
Merged
Merged
Conversation
This file contains 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
Co-authored-by: Benjamin Blattberg <[email protected]> Co-authored-by: Drew Sessler <[email protected]> Co-authored-by: Tony Landreth <[email protected]>
Issue: PGO-2043
cbandy
force-pushed
the
otel-collector
branch
from
February 6, 2025 17:12
c86ec3b
to
154646b
Compare
benjaminjb
approved these changes
Feb 6, 2025
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.
LGTM, but might like to hear that it works still
A generator converts YAML with comments to JSON to avoid errors at runtime and comments in the binary. Co-authored-by: Chris Bandy <[email protected]> Issue: PGO-2054
Postgres can log in two structured formats: CSV and JSON since Postgres 15. The two formats are very similar semantically, so this parses them in a shared OTTL transform processor. Co-authored-by: Chris Bandy <[email protected]> Issue: PGO-2033 Issue: PGO-2065
Issue: PGO-2059
Issue: PGO-2056
Collect JSON-formatted logs from pgAdmin when the feature gate is enabled. Issue: PGO-2057
Issue: PGO-2058
This strips comments and formatting from SQL files. It might be useful, and we already have the necessary dependencies.
cbandy
force-pushed
the
otel-collector
branch
from
February 7, 2025 18:28
154646b
to
f92e114
Compare
tony-landreth
approved these changes
Feb 7, 2025
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.
LGTM
In testing, we found that a running pgbackrest container wouldn't get the permissions adjusted with a mkdir; so we're switching to an install for now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Checklist:
Type of Changes:
What is the current behavior (link to any open issues here)?
Postgres and pgBackRest are multi-process and log to files. Metrics are collected using postgres_exporter.
What is the new behavior (if this is a feature change)?
Postgres and pgBackRest logs are parsed using the OTel Collector. Patroni and PgBouncer metrics are exported in the Prometheus format. Other exporters and formats will come later.
Other Information:
Issue: PGO-16
Issue: PGO-2033
Issue: PGO-2043
Issue: PGO-2056
Issue: PGO-2057
Issue: PGO-2058
Issue: PGO-2059
Issue: PGO-2065