Open modship opened 1 year ago
+1 I have the same issue, yace wont get DynamoDB metrics. CLoudwatch exporter with above config works.
@vinbh i have solved for now with that : (instead of "discovery")
customNamespace:
- name: AWS/DynamoDB
namespace: AWS/DynamoDB
regions:
- eu-west-3
metrics:
- name: SuccessfulRequestLatency
statistics:
- Average
- name: ThrottledRequests
statistics:
- Sum
...
@modship hi, Can you share the whole config yaml? I really need it. Thank you
@modship hi, Can you share the whole config yaml? I really need it. Thank you
im using ansible
yace_exporter_configuration:
apiVersion: v1alpha1
discovery:
jobs:
- type: AWS/EC2
regions:
- eu-west-3
period: 300
length: 300
metrics:
- name: CPUUtilization
statistics: [Average]
- name: NetworkIn
statistics: [Average, Sum]
- name: NetworkOut
statistics: [Average, Sum]
- name: NetworkPacketsIn
statistics: [Sum]
- name: NetworkPacketsOut
statistics: [Sum]
- name: DiskReadBytes
statistics: [Sum]
- name: DiskWriteBytes
statistics: [Sum]
- name: DiskReadOps
statistics: [Sum]
- name: DiskWriteOps
statistics: [Sum]
- name: StatusCheckFailed
statistics: [Sum]
- name: StatusCheckFailed_Instance
statistics: [Sum]
- name: StatusCheckFailed_System
statistics: [Sum]
- type: AWS/Lambda
regions:
- eu-west-3
period: 300
length: 300
metrics:
- name: Invocations
statistics: [Sum]
- name: Errors
statistics: [Sum]
- name: Throttles
statistics: [Sum]
- name: Duration
statistics: [Average, Maximum, Minimum, p90]
- type: AWS/ApiGateway
regions:
- eu-west-3
period: 300
length: 300
metrics:
- name: Latency
statistics: [Average, Maximum, p95, p99]
- name: Count
statistics: [SampleCount, Sum]
- name: 4xx
statistics: [Sum]
- name: 4XXError
statistics: [Sum]
- name: 5xx
statistics: [Sum]
- name: 5XXError
statistics: [Sum]
- name: IntegrationLatency
statistics: [Average]
customNamespace:
- name: Bridge
namespace: Bridge
regions:
- eu-west-3
metrics:
- name: bridge-owner-xma-balance
statistics:
- Average
period: 300
length: 300
- name: bridge-owner-eth-balance
statistics:
- Average
period: 300
length: 300
- name: tDAI-supply-diff
statistics:
- Average
period: 300
length: 300
- name: WETH-supply-diff
statistics:
- Average
period: 300
length: 300
- name: failed-burnRedeem
statistics:
- Average
period: 300
length: 300
- name: failed-lockMint
statistics:
- Average
period: 300
length: 300
- name: AWS/DynamoDB
namespace: AWS/DynamoDB
regions:
- eu-west-3
metrics:
- name: SuccessfulRequestLatency
statistics:
- Average
- name: ThrottledRequests
statistics:
- Sum
- name: UserErrors
statistics:
- Sum
- name: ConsumedReadCapacityUnits
statistics:
- Sum
- name: ConsumedWriteCapacityUnits
statistics:
- Sum
- name: ProvisionedReadCapacityUnits
statistics:
- Average
- name: ProvisionedWriteCapacityUnits
statistics:
- Average
- name: ReturnedBytes
statistics:
- Average
- name: ReturnedItemCount
statistics:
- Sum
@modship thanks for your response. below is my configuration. but it never collects SuccessfulRequestLatency metric. Do you have any doubts about what the problem might be? I really need it .
discovery:
jobs:
- type: dynamodb
regions:
- ap-northeast-2
enableMetricData: true
metrics:
- name: ThrottledRequests
statistics:
- Sum
period: 60
length: 60
- name: ConsumedReadCapacityUnits
statistics:
- Sum
period: 60
length: 60
- name: ProvisionedReadCapacityUnits
statistics:
- Sum
period: 60
length: 60
- name: ConsumedWriteCapacityUnits
statistics:
- Sum
period: 60
length: 60
- name: ProvisionedWriteCapacityUnits
statistics:
- Sum
period: 60
length: 60
customNamespace:
- name: dynamodb
namespace: AWS/DynamoDB
regions:
- ap-northeast-2
metrics:
- name: SuccessfulRequestLatency
statistics:
- Average
period: 60
length: 60
@modship thanks for your response. below is my configuration. but it never collects SuccessfulRequestLatency metric. Do you have any doubts about what the problem might be? I really need it .
discovery: jobs: - type: dynamodb regions: - ap-northeast-2 enableMetricData: true metrics: - name: ThrottledRequests statistics: - Sum period: 60 length: 60 - name: ConsumedReadCapacityUnits statistics: - Sum period: 60 length: 60 - name: ProvisionedReadCapacityUnits statistics: - Sum period: 60 length: 60 - name: ConsumedWriteCapacityUnits statistics: - Sum period: 60 length: 60 - name: ProvisionedWriteCapacityUnits statistics: - Sum period: 60 length: 60 customNamespace: - name: dynamodb namespace: AWS/DynamoDB regions: - ap-northeast-2 metrics: - name: SuccessfulRequestLatency statistics: - Average period: 60 length: 60
maybe your indentation for - Average And name : AWS/DynamoDB
@modship This is my final revision. However, the SuccessfulRequestLatency metric is still not being collected. Anyway, thank you for your help!
discovery:
jobs:
- type: dynamodb
regions:
- ap-northeast-2
enableMetricData: true
metrics:
- name: ThrottledRequests
statistics:
- Sum
period: 60
length: 60
- name: ConsumedReadCapacityUnits
statistics:
- Sum
period: 60
length: 60
- name: ProvisionedReadCapacityUnits
statistics:
- Sum
period: 60
length: 60
- name: ConsumedWriteCapacityUnits
statistics:
- Sum
period: 60
length: 60
- name: ProvisionedWriteCapacityUnits
statistics:
- Sum
period: 60
length: 60
customNamespace:
- name: AWS/DynamoDB
namespace: AWS/DynamoDB
regions:
- ap-northeast-2
metrics:
- name: SuccessfulRequestLatency
statistics:
- Average
period: 60
length: 60
Is there an existing issue for this?
YACE version
0.53.0 (docker)
Config file
Current Behavior
It might not be a bug, but I'm having trouble getting the scraping to work for AWS/DynamoDB (It works fine with: https://github.com/prometheus/cloudwatch_exporter/tree/master and this configuration: https://github.com/prometheus/cloudwatch_exporter/blob/master/examples/DynamoDB.yml).
error :
Expected Behavior
metrics of dynamoDB exported
Steps To Reproduce
No response
Anything else?
No response