purefa_alerts_open not reporting correctly about pure-fa-openmetrics-exporter HOT 4 CLOSED

Hi @imperatives @BadrZef - I've just submitted PR #109 to help us resolve this issue. It will be included in the next release.

from pure-fa-openmetrics-exporter.

Hi! Thank you for the issue.

I think this MAY be an issue with the JSON that's returned from the Purity API causing a major break in the string.

It would be very very helpful to get some of the raw output from /alerts from your array so I can test this further.

Can you please send us an email at [email protected] to schedule a call to gather this debug information? Thanks!

from pure-fa-openmetrics-exporter.

@chrroberts-pure We are experiencing the same label value mismatching in the purefa_alerts_open metric. Let me know if you need any additional information.

from pure-fa-openmetrics-exporter.

@imperatives , yes that would be very helpful to grab the Alerts endpoint from your array.

// Get API versions available 
curl -k https://gse-array01/api/api_version

// Use latest API version (this example is 2.30) and paste in Array API token
curl -k -D --location --request POST 'https://<array-mgmt-vip>/api/2.30/login' --header 'api-token: <api-token>'

// From the headers of the login, grab the x-auth-token and query Alerts
curl -k -D - --location 'https://<array-mgmt-vip>/api/2.30/alerts' --header 'Accept: application/json' --header 'x-auth-token: <x-auth-token received from headers from the login>'

I would recommend NOT to paste the output from your array on here, but please email us the results. Thank you!

from pure-fa-openmetrics-exporter.