[BUG] <Using a 60s interval to collect AWS NLB metrics, the /metrics endpoint only retrieves aws_networkelb_info data, while other defined metrics cannot be obtained.> #1545
Labels
bug
Something isn't working
Is there an existing issue for this?
YACE version
v0.61.2
Config file
apiVersion: v1alpha1
discovery:
jobs:
- type: AWS/NetworkELB
regions:
- us-east-1
- ap-southeast-2
- ap-southeast-1
- sa-east-1
roles:
- roleArn: "arn:aws:iam::043660463074:role/cloudwatch-exporter-role"
- roleArn: "arn:aws:iam::596009647310:role/cloudwatch-exporter-role"
- roleArn: "arn:aws:iam::992382840335:role/cloudwatch-exporter-role"
period: 60
length: 60
addCloudwatchTimestamp: true
metrics:
- name: HealthyHostCount
statistics: [Minimum, Average]
- name: UnHealthyHostCount
statistics: [Maximum, Average]
dimensionNameRequirements:
- LoadBalancer
- TargetGroup
- type: AWS/NetworkELB
regions:
- us-east-1
- ap-southeast-2
- ap-southeast-1
- sa-east-1
roles:
- roleArn: "arn:aws:iam::043660463074:role/cloudwatch-exporter-role"
- roleArn: "arn:aws:iam::596009647310:role/cloudwatch-exporter-role"
- roleArn: "arn:aws:iam::992382840335:role/cloudwatch-exporter-role"
period: 60
length: 60
addCloudwatchTimestamp: true
metrics:
- name: NewFlowCount
statistics: [Sum]
- name: ProcessedBytes
statistics: [Sum]
- name: ProcessedPackets
statistics: [Sum]
- name: ConsumedLCUs
statistics: [Sum]
- name: RejectedFlowCount
statistics: [Maximum]
- name: PeakPacketsPerSecond
statistics: [Maximum]
- name: PortAllocationErrorCount
statistics: [Sum]
- name: ActiveFlowCount
statistics: [Average]
- name: ActiveFlowCount_TCP
statistics: [Average]
dimensionNameRequirements:
- LoadBalancer
Current Behavior
When configuring a 60-second interval to collect AWS Network Load Balancer (NLB) metrics, the /metrics endpoint only returns the aws_networkelb_info metric. The other metrics that were defined in the configuration are not being captured or displayed.
Expected Behavior
expect get other metric: aws_networkelb_un_healthy_host_count_maximum in /metrics API
Steps To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: