You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
\* Introduced in version 1.1.0 of the FB OpenMetrics exporter, a change to the filesystem and bucket URI's was made to split off separate endpoints to ensure performance metrics for the /metrics/array endpoint remains quick to scrape in large environments.
142
-
143
-
Depending on the target array, scraping for the whole set of metrics could result into timeout issues, in which case it is suggested either to increase the scraping timeout or to scrape each single endpoint instead.
144
141
145
142
### Usage examples
146
143
@@ -161,10 +158,42 @@ Please have a look at the documentation of each image/application for adequate c
161
158
162
159
A simple but complete example to deploy a full monitoring stack on kubernetes can be found in the [examples](examples/config/k8s) directory
163
160
161
+
### Upgrade Information
162
+
163
+
v1.1.0 - New URIs `filesystem` and `objectstore` were added to split off these metric instruments to ensure metrics in the `array` URI remain quick to scrape in large environments to comply with the limitations recommendation set below in [Bugs and Limitations](#bugs-and-limitations).
164
+
165
+
If you require the following metrics for your dataset for your observability toolset, please add the new endpoint(s) as required.
166
+
167
+
168
+
The following metrics have been moved from `array` to `filesystem`
* Pure FlashBlade REST APIs are not designed for efficiently reporting on full clients and objects quota KPIs, therefrore it is suggested to scrape the "array" metrics preferably and use the "clients" and "usage" metrics individually and with a lower frequency than the other.. In any case, as a general rule, it is advisable to do not lower the scraping interval down to less than 30 sec. In case you experience timeout issues, you may want to increase the Prometheus scraping timeout and interval approriately.
196
+
* Pure FlashBlade REST APIs are not designed for efficiently reporting on full clients and objects quota metrics. Therefore, it is suggested to scrape the `array` metrics most frequently and use the `clients`, `filesystem`, `objectstore`, `policies`, and `usage` endpoints individually and with a lower frequency. As a general rule, it is not advisable to lower the scraping interval to less than 30 seconds for for any endpoint. In case you experience timeout issues, you may want to increase the Prometheus scraping timeout and interval appropriately. It is very important to have the collection interval (frequency) safely higher than the scrape duration.
0 commit comments