Skip to content

Conversation

atovpeko
Copy link
Contributor

Add PostgreSQL procedure back for Cloud, clarify about labels

Copy link

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

@ramonguiu
Copy link
Contributor

@atovpeko any reason not to merge?

Copy link
Contributor

@billy-the-fish billy-the-fish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nits.

global:
scrape_interval: 15s
scrape_configs:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants