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

purefa_alert_open - severity and component_name are reversed #14

Closed
bonito2907 opened this issue Nov 24, 2022 · 1 comment
Closed

purefa_alert_open - severity and component_name are reversed #14

bonito2907 opened this issue Nov 24, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@bonito2907
Copy link

Hi,

With the pure-fa-om-exporter v1.0.2, for a host alert, severity and component_name fields are reversed.

Here an example :
purefa_alerts_open{component_name="critical", component_type="host", instance="<flasharray name>", job="<job_name>", severity="<host name>"}

image used :
"Image": "quay.io/purestorage/pure-fa-om-exporter:v1.0.2"

NB: I don't know if the same issue is present for other component types.

Error seems to be on this commit : f3c66dc where the order of parameter seems to be wrong.

@genegr genegr self-assigned this Dec 28, 2022
@sdodsley sdodsley added the bug Something isn't working label Jan 9, 2023
@chrroberts-pure
Copy link
Collaborator

Fixed in #28

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

4 participants