You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#29 may also be of interest since it's requesting the ability to configure everything via environment variables, so you wouldn't need to inject a config file when using Docker.
@oppianmatt Is the database you're looking to monitor in the cloud (e.g. RDS), or an on-premise database?
If its on RDS, all you need to set is PGA_ENABLE_LOGS. If its on-premise, 515202d might be the fix (allowing you to mount a volume that has the log files, and then monitor that), that will be in the next collector release.
I'm also adding a TODO item here to update the documentation, as this is currently confusing to read when using the Docker container.
The README describes how to run a dockerized collector and uses environment variables to configure it. But how do we configure a pganalyze-collector.conf as needed by insights? https://app.pganalyze.com/docs/guides/setup_log_insights_on_self_hosted_server
If we create a local conf and volume mount it where? And will that override any default conf file that is needed?
The text was updated successfully, but these errors were encountered: