Joe Adams comments

Results 155 comments of


                                            Joe Adams

memory usage: use of 100% of available RAM

If you can run the master branch, that enables pprof which would allow you to pull data at runtime about where the memory is being used. I have posted some...

Support PostgreSQL 18

If there are things that don't work in 18, it would be more helpful to list what those things are. In general the project is compatible with all current versions.

The elasticsearch exporter fetch metrics elasticsearch_process_cpu_percent is 0

I'm not sure what is going on here. I checked with elasticsearch 8.1.2 as you noted you are running and the response looks correct for that metric. Are there any...

The elasticsearch exporter fetch metrics elasticsearch_process_cpu_percent is 0

I think you need to check the response from elasticsearch itself. I would curl the elasticsearch cluster. The endpoint is `/_nodes/stats` so something like `curl 127.0.0.1:9200/_nodes/stats`. That should give you...

Require a new Release to resolve vulnerabilities

#1088 will prepare a new release. Looks like the libraries have been updated in go.mod beyond what was originally reported here so I believe the new release will include the...

Require a new Release to resolve vulnerabilities

v0.16.0 has been released

Error running query on database \"<database_host:port>\": pg_stat_statements pq: syntax error at or near \"e\"

This sounds like an error in your queries.yaml file. Is this a customer queries.yaml file?

Error running query on database \"<database_host:port>\": pg_stat_statements pq: syntax error at or near \"e\"

There is not an "official" helm chart, but there is one provided from the [prometheus-community/helm-charts](https://github.com/prometheus-community/helm-charts) repo. This is a prometheus-community project, but separate from this project. `toast_blks_re` is not a...

Create a new cluster info retriever

bump @SuperQ

Create a new cluster info retriever

@SuperQ could you expand on that? The cache in the InfoProvider contains a single cached entry - it's not a slice, it can't grow. The cached value can only be...