Skip to content

Postgres Host showing as Down in Nodes section #5

Open
@mudasirmirza

Description

@mudasirmirza

Hi,

I am using the all in one installation with helm which installs everything, after that I am using https://coroot.com/docs/metric-exporters/aws-agent/installation to install aws-agent.

I have provided AWS Access and Secret key and added a Tag Filter for rds and elasticache.

Everything installed fine, after that it is showing one of the RDS instance as down which is not the case.

Screenshot 2023-11-20 at 9 48 24 AM

Also the logs below are in the aws-agent

aws-agent-755448458d-hkkwt aws-agent I1120 05:50:44.951581       1 logs.go:59] example-db-1: logs refreshed in: 221.912097ms
aws-agent-755448458d-hkkwt aws-agent W1120 05:50:45.593281       1 collector.go:291] coroot-db-instance-1: probe failed: pq: password authentication failed for user "root"
aws-agent-755448458d-hkkwt aws-agent I1120 05:50:45.593323       1 collector.go:227] coroot-db-instance-1: db metrics collected in: 12.024672ms
aws-agent-755448458d-hkkwt aws-agent W1120 05:50:45.598183       1 collector.go:291] example-db-1: probe failed: pq: password authentication failed for user "root"
aws-agent-755448458d-hkkwt aws-agent I1120 05:50:45.653792       1 collector.go:217] coroot-db-instance-1: os metrics collected in: 72.252563ms

The example-db-1 in this case is a RDS Aurora Cluster. When I click on the RDS Node all graphs are empty.

I have no idea why is this happening and any help will be appreciated.

Regards.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions