Created by: leonore
closes #34187 (closed), which describes the issue in detail.
The issue is fixed by hacking the query a bit and adding an OR with a promql query that will get the pg metrics specifically for codeinsights-db.
codeinsights-db
this shows it working on dogfood
Locally, the codeinsights-db is integrated with the main db so this might not work- though from my local testing the metrics don't work the same, as I can only see postgres_exporter connections. The change didn't break anything though.
postgres_exporter
before:
after:
