Conversation
|
Allow 10 minutes from last push for the staging site to build. If the link doesn't work, try using incognito mode instead. For internal reviewers, check web-documentation repo actions for staging build status. Link to build for this PR: http://docs-dev.timescale.com/docs-revert-prometheus-docs |
|
@atovpeko any reason not to merge? |
…heus-docs # Conflicts: # _partials/_prometheus-integrate.md
| global: | ||
| scrape_interval: 15s | ||
|
|
||
| scrape_configs: |
There was a problem hiding this comment.
In scrape configs, if you are using Tiger Cloud, I would highly recommend they add service id and project id as labels as it was explained in the original version of the documentation. That allows them to correlate metrics from Tiger Cloud Prometheus exporter and from the PostgreSQL exporter.
There was a problem hiding this comment.
Thanks, added the labels in the scrape config (also added region since we are telling them to configure service id, project id, and region labels in the postgresql exporter step).
| 1. Copy the exporter URL. | ||
| 1. Copy the exporter URL. | ||
|
|
||
| 1. In your Prometheus installation, update `prometheus.yml` to point to the exporter URL as a scrape target: |
There was a problem hiding this comment.
@rahilsondhi have we already changed the Console to provide the snippet to be used in Prometheus? I would point the user to copy from there which will already have all the correct parameters set up
4 participants
Add PostgreSQL procedure back for Cloud, clarify about labels