Feature Request for Volume Exports Metrics about pure-fb-openmetrics-exporter

[sdodsley]

@jmg011 could you expand on this? I'm not sure what you are referring to.

[jmg011]

@sdodsley - I meant to request the metrics for export policy on the volumes in Pure Blade Exporter.

[genegr]

I am assuming you mean an info-style metric that shows the NFS export rules. Would something like this work for you?

purefb_nfs_export_rule{policy="mypolicy01",client="10.0.0.2",permission="ro",security="krb5i, krb5p",access="no-squash",anon_uid="1000",anon_gid="1001",secure="false",fileid-32bit="true",atime="true",index="3"} 1

That is certainly feasible.

[jmg011]

Hi @genegr - Correct. Something like this where I have policy name and other labels you have mentioned. For the given client though, that can be in different data-point. For example, note client label with different clients for the given policy and other associated labels like index.

purefb_nfs_export_rule{policy="mypolicy01",client="client-1",permission="ro",security="krb5i, krb5p",access="no-squash",anon_uid="1000",anon_gid="1001",secure="false",fileid-32bit="true",atime="true",index="3"} 1

purefb_nfs_export_rule{policy="mypolicy01",client="client-2",permission="ro",security="krb5i, krb5p",access="no-squash",anon_uid="1000",anon_gid="1001",secure="false",fileid-32bit="true",atime="true",index="4"} 1

purefb_nfs_export_rule{policy="mypolicy01",client="client-3",permission="ro",security="krb5i, krb5p",access="no-squash",anon_uid="1000",anon_gid="1001",secure="false",fileid-32bit="true",atime="true",index="5"} 1

[jmg011]

@genegr - We will also need another metric called purefb_volume_export_policy. In this metric, we will have just the volume and policy name.

This way I can have policy metric with all the client rules and volume policy metric that I can join to get additional details.

Let me know if it is something that can be provided as a nightly build and possible ETA for this feature.

[genegr]

Both metrics can be exported. Will try to work at that the next days and hopefully have it done by the end of the week.

[jmg011]

@genegr - Perfect. Thank you so much!!

[jmg011]

Hi @genegr - Any update on this feature?

[jmg011]

Hi @genegr - Any update on this feature request?

[jmg011]

Hi @sdodsley - Can you help get the status update on this request?

[sdodsley]

@jmg011 I'll chase and see where we are at.

[jmg011]

@sdodsley - Thank you. Appreciate it.

[jmg011]

Hi @sdodsley - Any update on this?

[sdodsley]

@jmg011 this work is apparently done. Just a few other things to complete for other customer requests

[jmg011]

@sdodsley - Thanks for the update. Any ETA on the release?

[sdodsley]

We expect to cut a new release next week

[jmg011]

@sdodsley - Thank you. Please let me know when the new version is released so I can test it and deploy.

[genegr]

The new release with the requested enhacement is available

[jmg011]

Hi @genegr - I tested the new exporter version (v1.0.3) and I get this error:

2023/05/17 13:51:01 Error in token file: unknown arguments --host 0.0.0.0
2023/05/17 13:51:13 Error in token file: unknown arguments --host 0.0.0.0

I noticed another hotfix was released 5 days ago, so I tested this exporter version as well: v1.0.3.hotfix1
This version runs fine, but I do not see exports metrics in on my test cluster. What is the export policy metric called?

I have configured below metrics paths.
/metrics/array
/metrics/clients
/metrics/usage

These are the only metrics I see. No exports metrics:

purefb_alerts_open
purefb_array_http_specific_performance_latency_usec
purefb_array_http_specific_performance_throughput_iops
purefb_array_nfs_specific_performance_latency_usec
purefb_array_nfs_specific_performance_throughput_iops
purefb_array_performance_average_bytes
purefb_array_performance_bandwidth_bytes
purefb_array_performance_latency_usec
purefb_array_performance_throughput_iops
purefb_array_s3_performance_latency_usec
purefb_array_s3_performance_throughput_iops
purefb_array_space_bytes
purefb_array_space_data_reduction_ratio
purefb_array_space_parity
purefb_array_space_utilization
purefb_clients_performance_average_bytes
purefb_clients_performance_bandwidth_bytes
purefb_clients_performance_latency_usec
purefb_clients_performance_throughput_iops
purefb_file_system_usage_groups_bytes
purefb_file_system_usage_users_bytes
purefb_file_systems_performance_average_bytes
purefb_file_systems_performance_bandwidth_bytes
purefb_file_systems_performance_latency_usec
purefb_file_systems_performance_throughput_iops
purefb_file_systems_space_bytes
purefb_file_systems_space_data_reduction_ratio
purefb_hardware_connectors_performance_bandwidth_bytes
purefb_hardware_connectors_performance_throughput_pkts
purefb_hardware_health
purefb_info
purefb_shardware_connectors_performance_errors

[chrroberts-pure]

Hi @jmg011 , In 1.0.3 ( #23 ) a new URI was added for this specific feature.

Please query the new URI that was created in that release /metrics/policies . The new URI is documented in README.

Please let us know if you have further issues.

v1.0.3.hotfix1 was released specifically for that bug with the error message. See issue #24 , and PR #25

[jmg011]

Thank you @chrroberts-pure

@genegr - I see purefb_nfs_export_rule policy metric but I do not see that policy name added to any of the filesystem/volume metric.

So the idea is to have one metric with all the policy rules and one of the filesystem metric should have one more label with policy name. That way I can join both the metrics to get all the exports rules for a given volume/filesystem.

Let me know if I missed looking at any filesystem metric. I looked for policy label and I could not find it on any filesystem metric.

Adding a screenshot from previous discussion on this thread.