Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to see the RDS metrics in Prometheus #246

Open
ramesh-healthhelper opened this issue Oct 31, 2022 · 1 comment
Open

Unable to see the RDS metrics in Prometheus #246

ramesh-healthhelper opened this issue Oct 31, 2022 · 1 comment

Comments

@ramesh-healthhelper
Copy link

Hi,
I have deployed yace exporter and it is running fine.

I see the below messages in yace exporter logs.

{"level":"info","msg":"Parse config..","time":"2022-10-30T19:33:22Z"} {"level":"info","msg":"Startup completed","time":"2022-10-30T19:33:22Z"}

And, I see the below metrics only in Prometheus console.

image

I am looking for the RDS metrics and below are the configurations of yace exporter.

data:
config.yml: |
discovery:
jobs:

  • regions:
  • us-east-1
    type: rds
    enableMetricData: true
    metrics:
  • name: BinLogDiskUsage
    statistics:
  • Average
    period: 300
    length: 3600
  • name: BurstBalance
    statistics:
  • Average
    period: 300
    length: 3600
  • name: CPUUtilization
    statistics:
  • Average
    period: 300
    length: 3600
  • name: CPUCreditUsage
    statistics:
  • Average
    period: 300
    length: 3600
  • name: CPUCreditBalance
    statistics:
  • Average
    period: 300
    length: 3600
  • name: DatabaseConnections
    statistics:
  • Average
    period: 300
    length: 3600
  • name: DiskQueueDepth
    statistics:
  • Average
  • Maximum
    period: 300
    length: 3600
  • name: FailedSQLServerAgentJobsCount
    statistics:
  • Average
    period: 300
    length: 3600
  • name: FreeableMemory
    statistics:
  • Average
    period: 300
    length: 3600
  • name: FreeStorageSpace
    statistics:
  • Average
    period: 300
    length: 3600
  • name: MaximumUsedTransactionIDs
    statistics:
  • Average
    period: 300
    length: 3600
  • name: NetworkReceiveThroughput
    statistics:
  • Average
    period: 300
    length: 3600
  • name: NetworkTransmitThroughput
    statistics:
  • Average
    period: 300
    length: 3600
  • name: OldestReplicationSlotLag
    statistics:
  • Average
    period: 300
    length: 3600
  • name: ReadIOPS
    statistics:
  • Average
    period: 300
    length: 3600
  • name: ReadLatency
    statistics:
  • Maximum
  • Average
    period: 300
    length: 3600
  • name: ReadThroughput
    statistics:
  • Average
    period: 300
    length: 3600
  • name: ReplicaLag
    statistics:
  • Average
    period: 300
    length: 3600
  • name: ReplicationSlotDiskUsage
    statistics:
  • Average
    period: 300
    length: 3600
  • name: SwapUsage
    statistics:
  • Average
    period: 300
    length: 3600
  • name: TransactionLogsDiskUsage
    statistics:
  • Average
    period: 300
    length: 3600
  • name: TransactionLogsGeneration
    statistics:
  • Average
    period: 300
    length: 3600
  • name: WriteIOPS
    statistics:
  • Average
    period: 300
    length: 3600
  • name: WriteLatency
    statistics:
  • Maximum
  • Average
    period: 300
    length: 3600
  • name: WriteThroughput
    statistics:
  • Average
    period: 300
    length: 3600

Please helm me on fixing this.

Thanks and Regards.
Ramesh

@Mak0tin
Copy link
Contributor

Mak0tin commented Nov 4, 2022

Hi Ramesh,

Is your aws resource (RDS) tagged?

https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html

Yace only discovers tagged resources in AWS

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants