Add SQL exporter as sidecar container #5
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 exporter can expose Prometheus metrics from SQL statements executed against CrateDB.
The default collector config exposes metrics from the sys.health and sys.shards tables.
The SQL exporter is enabled by default and listens on port 8181.
Update: I think it would make more sense to run the SQL exporter as separate
Deployment. The sidecar approach has the benefit of being able to use thecrateuser to connect to CrateDB. However, that means that all metrics are also exposedntimes, wherenis the number of CrateDB nodes. This is not desired.Running as a separate
Deploymentrequires to bootstrap a dedicated CrateDB user with necessary permissions.