Skip to content

[BUG] Metrics from PrivateLinkEndpoints not working #1579

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

Open
1 task done
vitormazali opened this issue Nov 21, 2024 · 2 comments
Open
1 task done

[BUG] Metrics from PrivateLinkEndpoints not working #1579

vitormazali opened this issue Nov 21, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@vitormazali
Copy link

vitormazali commented Nov 21, 2024

Is there an existing issue for this?

  • I have searched the existing issues

YACE version

v0.61.2

Config file

apiVersion: v1alpha1
customNamespace:
  - name: VPCSubnetMetrics
    namespace: VPCSubnetMetrics
    regions:
      - us-east-1
    roles:
      - roleArn: arn:aws:iam::<account-id>:role/<role-name>
    dimensionNameRequirements:
      - AccountId
      - AccountAlias
      - SubnetId
      - SubnetName
      - VpcId
    delay: 240
    period: 300
    metrics:
      - name: TotalIps
        statistics:
          - Maximum
      - name: PercentAvailableIps
        statistics:
          - Minimum
new metrics of vpce
static:
  - namespace: AWS/PrivateLinkEndpoints
    name: vpc-endpoint
    regions:
      - us-east-1
      - us-east-2
      - us-west-1
      - us-west-2
      - sa-east-1
    roles:
      - roleArn: arn:aws:iam::<account-id>:role/<role-name>
    metrics:
      - name: BytesProcessed
        statistics: [Sum,Average,Minimum,Maximum]
        period: 600
        length: 600
        nilToZero: true

Current Behavior

the metrics obtained from customNamespace are ok, however, the ones from static are retuning only NaN values (0 after enabling nilToZero). We've tried different options, specifying dimensions, single region, same issue - example of config tested below:

    dimensions:
     - name: EndpointType
       value: Interface
     - name: ServiceName
       value: com.amazonaws.us-east-1.s3
     - name: SubnetId
       value: subnet-<subnet-id>
     - name: VPCEndpointId
       value: vpce-<vpce-id>
     - name: VPCId
       value: vpc-<vpc-id>
    metrics:
      - name: BytesProcessed
        statistics:
        - Maximum
        period: 600
        length: 600

Expected Behavior

Have the same metric values that we are able to see in the Cloudwatch console (we do have metrics from VPC endpoints there) in the YACE.

Steps To Reproduce

No response

Anything else?

No response

@vitormazali vitormazali added the bug Something isn't working label Nov 21, 2024
@ahmedelmelegy
Copy link

ahmedelmelegy commented Feb 6, 2025

I have the same issue that it can`t export metrics for PrivateLinkEndpoints but it can be seen in AWS CloudWatch
YACE version v0.61.2

                - type: AWS/PrivateLinkEndpoints
                  regions:
                    - eu-central-1
                  dimensionNameRequirements:
                    - Service Name
                  searchTags:
                    - key: Project
                      value: ^SOL$
                  metrics:
                    - name: PacketsDropped
                      statistics:
                        - Average
                        - Sum
                        - Maximum
                      period: 300    # 5-minute intervals, matching the reporting frequency
                      length: 900   # Query 15-minutes of data
                    - name: RstPacketsReceived
                      statistics:
                        - Average
                        - Sum
                        - Maximum
                      period: 300     # 5-minute intervals, matching the reporting frequency
                      length: 900   # Query 15-minutes of data`

@ahmedelmelegy
Copy link

I read all latest releases features and bugfixes, but this issue seems to be not fixed yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants