docs: add IvorySQL 5.4 pgnodemx integration guide - #297
Open
messere1 wants to merge 1 commit into
Open
Conversation
Assisted-by: OpenAI:gpt-5
|
🚀 IvorySQL-Docs Preview Ready
|
Contributor
|
Thank you for your contribution. We will review it as soon as possible. |
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
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.
Summary
Why
pgnodemx exposes Linux node and IvorySQL process metrics through SQL, but users lacked an IvorySQL-specific build and configuration guide. The new documentation also records important environment boundaries that are easy to miss, including hybrid cgroup support and matching the OpenSSL ABI used by IvorySQL.
Fixes IvorySQL/IvorySQL#1105
Validation
Environment: Ubuntu 22.04 x86_64, source-built IvorySQL 5.4 / PostgreSQL 18.4, pgnodemx 1.7.
/procmemory and disk queries, executable-path lookup, and cgroup-mode detection returned expected dataivorysql.compatible_mode = oracle--failure-level WARNgit diff --checkpassesUser impact
Monitoring users gain SQL access to host, process, filesystem, container, and Kubernetes metadata using a dedicated
pg_monitoraccount. The guide clearly separates supported/procmetrics from environment-dependent cgroup and Downward API facilities.