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

add trigger name as a label in Prometheus metrics #3650

Merged
merged 2 commits into from
Oct 27, 2022

Conversation

cdlliuy
Copy link
Contributor

@cdlliuy cdlliuy commented Sep 8, 2022

This PR is used to resolve #3588

  • use the existing Trigger.Name field as the scalerName
  • add scalerName to prometheus metric as a label to facilitate the grafana dashboard display

see below:
image

Copy link
Member

@JorTurFer JorTurFer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution! ❤️
I left some comments inline. Apart from them, could you open a PR against docs, explaining this new field?

pkg/metrics/prometheus_metrics.go Outdated Show resolved Hide resolved
pkg/scaling/cache/scalers_cache.go Show resolved Hide resolved
@JorTurFer JorTurFer requested a review from a team September 9, 2022 06:35
Copy link
Member

@tomkerkhove tomkerkhove left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you update our changelog please?

@JorTurFer
Copy link
Member

any update @cdlliuy ?
Could you update the changelog and solve the conflicts?

@cdlliuy cdlliuy force-pushed the ying/update_prometheus_name branch from 531c21e to 173d07f Compare October 9, 2022 09:06
@cdlliuy
Copy link
Contributor Author

cdlliuy commented Oct 9, 2022

any update @cdlliuy ? Could you update the changelog and solve the conflicts?

Done. Thanks for the reminder!

Copy link
Member

@tomkerkhove tomkerkhove left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LTGM

@cdlliuy
Copy link
Contributor Author

cdlliuy commented Oct 11, 2022

@tomkerkhove , can you help me to understand why "e2e-tests / e2e tests (pull_request_target) " is queued but not run? Thanks a lot!

@tomkerkhove
Copy link
Member

It's waiting for the label to be added on passing AFAIK.

@tomkerkhove
Copy link
Member

tomkerkhove commented Oct 11, 2022

/run-e2e *
Update: You can check the progress here

@tomkerkhove
Copy link
Member

tomkerkhove commented Oct 14, 2022

/run-e2e *

Update: You can check the progress here

@JorTurFer
Copy link
Member

JorTurFer commented Oct 14, 2022

/run-e2e
Update: You can check the progress here

@cdlliuy
Copy link
Contributor Author

cdlliuy commented Oct 27, 2022

@tomkerkhove @JorTurFer , I rebased to resolve the latest conflict on change.md, Can you help to run e2e and merge this PR?

@tomkerkhove
Copy link
Member

tomkerkhove commented Oct 27, 2022

/run-e2e
Update: You can check the progress here

@JorTurFer JorTurFer merged commit 83f882e into kedacore:main Oct 27, 2022
26tanishabanik pushed a commit to 26tanishabanik/keda that referenced this pull request Nov 1, 2022
* add trigger name as a label in prometheus metrics

Signed-off-by: Ying Liu <[email protected]>
Signed-off-by: 26tanishabanik <[email protected]>
@JorTurFer
Copy link
Member

Hello @cdlliuy ,
I didn't remember to request the documentation about this feature. It's true that the parameter was already there but it wasn't used either documented.
Could you open a PR in keda-docs repo documenting it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Same metric name with multiple scaled object defined
3 participants