Skip to content

Commit

Permalink
update copy based on feedback
Browse files Browse the repository at this point in the history
Co-authored-by: Maciek Sakrejda <m.sakrejda@gmail.com>
  • Loading branch information
jensy and msakrejda authored Aug 30, 2024
1 parent 0b03db4 commit d6ac46c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ To continue, select in which environment you are running your Postgres database:

<OverviewInstallChoice />

If you're interested in integrating pganalyze with your database hosting provider but don't see it listed as officially supported, you can follow the [installation guide for self-managed databases](/docs/install/self_managed/00_choose_setup_method). You will need to run the pganalyze collector on a server that can reach your database in order to connect it to your provider. Note that [Log Insights](/docs/log-insights) and other features that depend on it will have some limitations.
If you're interested in integrating pganalyze with your database hosting provider but don't see it listed as officially supported, you can follow the [manual installation guide for self-managed databases](docs/install/self_managed/01_create_monitoring_user). You will need to run the pganalyze collector on a server with network connectivity to your database in order to monitor your database. Note that system-level statistics (memory usage, I/O, etc.) cannot be collected this way and will not be available in pganalyze. [Log Insights](/docs/log-insights) (and the features that depend on it) is only available if your provider exports Postgres logs for your database server [via syslog](https://pganalyze.com/docs/log-insights/setup/syslog-server).

## Explore how pganalyze works

Expand Down

0 comments on commit d6ac46c

Please sign in to comment.