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

[BUG] Not a valid metric name when using statistics with brackets like 'PR(:10)' #1564

Open
1 task done
nixargh opened this issue Nov 14, 2024 · 2 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@nixargh
Copy link
Contributor

nixargh commented Nov 14, 2024

Is there an existing issue for this?

  • I have searched the existing issues

YACE version

0.61.2

Config file

discovery:
  jobs:
    - type: AWS/ELB
      regions:
        - eu-central-1
      period: 60
      length: 60
      dimensionNameRequirements:
        - AvailabilityZone
        - LoadBalancerName
      metrics:
        - name: Latency
          statistics: ["PR(:10)"]

Current Behavior

Shows error, like:

$ curl -s http://localhost:5000/metrics
An error has occurred while serving metrics:

4 error(s) occurred:
* "aws_elb_latency_pr(_10)" is not a valid metric name

Expected Behavior

Show metrics, like:

$ curl -s http://localhost:5000/metrics

aws_elb_latency_pr__10_{account_id="***...

Steps To Reproduce

No response

Anything else?

I've created the pull request - #1563
At least it works that way in my case.

@nixargh nixargh added the bug Something isn't working label Nov 14, 2024
@nixargh nixargh changed the title [BUG] Not a valid metric name when using statistics with brackets like 'PR(:300)' [BUG] Not a valid metric name when using statistics with brackets like 'PR(:10)' Nov 14, 2024
@Littensven83
Copy link

licenses.md

@Littensven83
Copy link

$ curl -s http://localhost:5000/metrics

aws_elb_latency_pr__10_{account_id="***...

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