Description
Is there an existing issue for this?
- I have searched the existing issues
YACE version
0.53.0
Config file
apiVersion: v1alpha1
discovery:
jobs:
- type: AWS/NetworkELB
regions:
- us-east-1
period: 60
length: 300
metrics:
- name: ActiveFlowCount
statistics: [Minimum,Average,Maximum]
- name: NewFlowCount
statistics: [Maximum]
- name: UnHealthyHostCount
statistics: [Maximum]
- name: ProcessedBytes
statistics: [Maximum]
- type: AWS/NATGateway
regions:
- us-east-1
period: 60
length: 300
metrics:
- name: ActiveConnectionCount
statistics: [Maximum]
- name: BytesInFromDestination
statistics: [Maximum]
- name: BytesInFromSource
statistics: [Maximum]
- name: ErrorPortAllocation
statistics: [Maximum]
- name: IdleTimeoutCount
statistics: [Maximum]
- name: PacketsDropCount
statistics: [Maximum]
- name: PacketsInFromDestination
statistics: [Maximum]
- name: PacketsInFromSource
statistics: [Maximum]
- type: AWS/ElastiCache
regions:
- us-east-1
period: 60
length: 300
metrics:
- name: EngineCPUUtilization
statistics: [Maximum,Average]
- name: DatabaseMemoryUsagePercentage
statistics: [Maximum]
- name: CurrItems
statistics: [Maximum]
- name: NetworkBytesIn
statistics: [Maximum]
- name: NetworkBytesOut
statistics: [Maximum]
- name: CurrConnections
statistics: [Maximum]
- name: NetworkPacketsPerSecondAllowanceExceeded
statistics: [Maximum]
- name: NetworkConntrackAllowanceExceeded
statistics: [Maximum]
- name: CacheMisses
statistics: [Average]
- name: CacheHits
statistics: [Average]
- name: ReplicationLag
statistics: [Average]
- type: AWS/RDS
regions:
- us-east-1
period: 60
length: 300
metrics:
- name: FreeStorageSpace
statistics: [Average]
- name: FreeableMemory
statistics: [Average]
- name: CPUUtilization
statistics: [Maximum]
- name: ReadIOPS
statistics: [Average]
- name: WriteIOPS
statistics: [Average]
- name: NetworkReceiveThroughput
statistics: [Average]
- name: NetworkTransmitThroughput
statistics: [Average]
- name: DatabaseConnections
statistics: [Average, Maximum]
- name: OldestReplicationSlotLag
statistics: [Average]
- name: DBLoad
statistics: [Average]
- type: AWS/MemoryDB
regions:
- us-east-1
period: 60
length: 300
metrics:
- name: EngineCPUUtilization
statistics: [Maximum]
- name: DatabaseMemoryUsagePercentage
statistics: [Maximum]
- name: CurrItems
statistics: [Maximum]
- name: NewConnections
statistics: [Maximum]
- name: NetworkBytesIn
statistics: [Maximum]
- name: NetworkBytesOut
statistics: [Maximum]
- name: DBLoad
statistics: [Average]
- name: OldestReplicationSlotLag
statistics: [Average]
- type: AWS/S3
regions:
- us-east-1
period: 60
length: 300
metrics:
- name: BucketSizeBytes
statistics: [Average]
- name: NumberOfObjects
statistics: [Average]
- type: AWS/EBS
regions:
- us-east-1
period: 60
length: 300
metrics:
- name: VolumeReadOps
statistics: [Average]
- name: VolumeWriteOps
statistics: [Average]
Current Behavior
when elasticache add node , i saw cloudwatch has updated new replicas data, but yace didn't. i tried to restart yace, but didn't work
Expected Behavior
yace update elasticache as soon as cloudwatch updated
Steps To Reproduce
No response
Anything else?
No response