Lukas Fittl

Hi @barillax @booleanbetrayal & @joekohlsdorf! Thanks for your patience on this. First of all, the good news: We added a workaround in the latest collector release to unblock the use...

@booleanbetrayal @joekohlsdorf Ah, I believe I know what the problem here is. All old queries that show up as `` need to be refreshed on our end (we can manually...

@llivingstone Thanks for the request - we're reviewing whether we can improve this in the collector in the future (but this requires a bit of rework of how we interact...

@caleb15 Any chance that container has been crashing and restarting multiple times? (there is a condition when the collector crashes that can leave behind files)

@caleb15 You could look in "docker ps -a" and then run "docker logs" on any instances that have run recently but have been stopped. Also, in case it's an out...

Hi @pgiraud! It depends a bit what your test scenario is - AFAIK `--dry-run-logs` only works for cases where the collector downloads the log files (e.g. from an API of...

@JordanP We don't support log collection in Kubernetes today - though looking to add this in the future. For @sebasmagri's initial question - Sebastian, were you looking to monitor Kubernetes...

@sebasmagri Ah - makes sense. You can use the following settings to override the system identifiers: PGA_API_SYSTEM_ID PGA_API_SYSTEM_TYPE PGA_API_SYSTEM_SCOPE You can see the defaults that get assigned here: https://github.com/pganalyze/collector/blob/master/config/identify_system.go#L15 (note...

@sebasmagri In the case where you are not using the instance ID in the hostname, utilizing the `AWS_INSTANCE_ID` variable should work (that, or the hostname, is what the collector checks...

@JordanP There are two ways to do that, assuming you are referring to Postgres running inside a Docker container on a VM that you manage: 1) Run the pganalyze-collector on...