fix: use the proper views for pgmonitor-extension queries. doc update. new table stat metric #412
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.
Description
Have sq_exporter actually use the new views in pgmonitor-extension instead of full queries.
Update docs to provide links to upstream Prometheus & Alertmanager configuration docs.
Please indicate what kind of change your PR includes (multiple selections are acceptable):
PRs should be against existing issues, so please list each issue using a separate 'closes' line:
closes #339
If this PR depends on another PR or resolution of another issue, please indicate that here using a separate 'depends' line for each dependency.
depends on #
If you have an external dependency (packages, portal updates, etc), add the 'BLOCKED' tag to your PR.
Testing
None of the testing listed below is optional.
Code testing
Have you tested your changes against:
If your code touches postgres_exporter, have you:
If your code touches node_exporter, have you:
If your code touches Prometheus, have you:
promtool check config
promtool check rules
If your code touches Grafana, have you:
Checklist: