Comments (14)
Hi @cmautner1 - Can you help debug this issue?
from pure-fa-openmetrics-exporter.
This should be solved by the new exporter, completely refactored in Go. Please give it a try if/when you can and provide a feedback. I am keeping the issue open for a while just for this purpose.
from pure-fa-openmetrics-exporter.
@genegr we are using the latest release. Can you provide the release name that has the fix?
from pure-fa-openmetrics-exporter.
@genegr it looks like a new version released 10 days back. Can you confirm this is the one that has the fix? https://quay.io/repository/purestorage/pure-fa-om-exporter?tab=tags&tag=latest
Also, is there any metric names or label names changed between this release and the one we are using
quay.io/purestorage/pure-fa-ome latest
Asking since the new exporter of pure blade has major changes in metric/label names and we are having to update all of our alerting and dashboards. I just want to know upfront if that is the case with block exporter as well.
from pure-fa-openmetrics-exporter.
@jmg011 the current release is 1.0.1. Starting from v1.0.0 the code has been completely refactored in Go and should not show those odd behaviors as the old code. It uses Resty to handle the communication with the FA API server and this makes the code much more adaptive to the different JSON responses returned by the API. About names and labels, we tried to keep the previous naming for the metrics but have instead changed those labels that were too generic into more meaningful names. This mainly happened for the host metrics, in which we changed the generic "name" label into "host".
from pure-fa-openmetrics-exporter.
I tested it. The metrics for volume are working on the new version. Thank you for fixing it. But many changes are made to the metric and label names which I had to map to current metrics and labels so that we can replace in production later.
Maybe going forward, the better approach would be to provide backward compatibility for new exporters. For example in rare case you need to change metric name or labels, it should be named something else and should have previous metric name as well, so that the user can determine when to cutover the alerts to new metric after upgrading the exporter. This will give flexibility to get the new metrics as part of new exporter release without having to immediately change alerting on current metrics/labels. What do you think?
from pure-fa-openmetrics-exporter.
@genegr Hi, is there a documentation on what health alert $values for purefb_hardware_health metric mean?
Current Possible values I see are 0, 1, 2
from pure-fa-openmetrics-exporter.
In the new Go version the metric is now named as purefa_hw_component_status and its value is always set to 1. There is now a specific status label that reflects the internal value returned by the REST API foe the same parameter. The same change has also been applied to the FlashBlade exporter, for which the metric is named purefb_hw_component_status
from pure-fa-openmetrics-exporter.
@genegr Thank you.
from pure-fa-openmetrics-exporter.
@genegr I just tested the new exporter with this metric change. I do not see severity label anymore for purefa_hw_component_status metric. Is there any reason why severity is removed for this new metric?
or we should use purefa_alerts_open for open alerts with severity and purefa_hw_component_status separately for component health check?
from pure-fa-openmetrics-exporter.
@jmg011 The metrics specific to hardware components have now changed into these:
purefa_hw_component_status
purefa_hw_component_temperature_celsius
purefa_hw_component_voltage_volt
from pure-fa-openmetrics-exporter.
@genegr Thanks. So if there are any hardware failures which reflects under purefa_hw_components* metrics, will those also show up under purefa_alerts_open metric as open alerts?
from pure-fa-openmetrics-exporter.
@jmg011 the arrays metric had a bug. This has been resolved in the v1.0.3 release
from pure-fa-openmetrics-exporter.
Going to close this as it has been fixed by the introduction of release 1.0.0
from pure-fa-openmetrics-exporter.
Related Issues (20)
- CVE-2023-45286 is causing issues with Quay Scanner
- Update useragent string to reflect calling platform HOT 3
- Collect Frontent WWPN Information HOT 9
- Array Load Statistics metric HOT 5
- purefa_alerts_open not reporting correctly HOT 4
- Add better error handling when the API token is incorrect. HOT 2
- PodReplicaLink is not in seconds HOT 3
- Add vendor directory to manage deps
- [new metric label proposal] - Add subscription info
- Add OME version to user_agent string
- [new metrics proposal] Volume snapshot metrics HOT 1
- Adding “volume group” metrics to pure-fa-openmetrics-exporter and pure-fb-openmetrics exporters HOT 15
- File system metrics using Pure-fa-opemmetrics-exporter HOT 8
- Сonnection path state HOT 3
- fatal error: concurrent map writes HOT 5
- The OpenMetrics exporter is incorrectly calling the /hardware endpoint HOT 3
- [new metric proposal] - Drive capacity metrics - purefa_drive_capacity HOT 1
- Enhancements to purefa_alerts_open, collect additional fields. HOT 5
- Inquiry regarding the “Purestorage” version supported by the current “exporter” and the previous “exporter” HOT 8
- Grafana not showing data as expected with multiple arrays HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pure-fa-openmetrics-exporter.