loud crest
Hi Team,
Would it be possible to have Harvest pulling some metadata from Active IQ (AIQ) especially EOM/EOSL details for NetApp devices and expose it as Prometheus metrics?
The goal is to combine lifecycle info (like EOM/EOSL) with performance/capacity data that Harvest already collects, so it can be visualized or alerted on in Prometheus/Grafana.
Is this something that could be added natively or considered as a plugin/exporter integration?
vale harness
I don’t think that’s feasible because of SSO and OTP on support site.
Mmmm… well, MAYBE if you provide an API key and refresh it when it expires.
loud crest
yeah by providing API key using this GQL query
query hardwareSupportReport($customerGroup: String, $pageSize: Int) {
systems(customerGroup: $customerGroup, pageSize: $pageSize) {
systems {
customerGroup
hardwareModel {
name
endOfSupport
}
systemShipmentDate
contract {
hardwareContractEndDate
hardwareServiceLevel
hardwareWarrantyEndDate
nrdContractEndDate
overallContractEndDate
softwareContractEndDate
}
endOfSupport {
earliestDiskEndOfSupportDate
earliestEndOfSupportDate
earliestShelfEndOfSupportDate
latestEndOfSupportDate
latestPVRDate
}
}
}
}
vale harness
That would be cool indeed.
Let’s see what the boys think. @cunning ibex ? It could be a NAbox thing otherwise. Can’t commit to anything though.
cunning ibex
@loud crest it would require building a new collector and it's not clear how good a fit it would be with how frequently AIQ rotates auth tokens and limits how often you can make API calls. Does the cluster itself have any of this information? Please open a Github issue with the details and we can take a look https://github.com/NetApp/harvest/issues
unkempt ember
There's also a new Support site API which also provides some System Entitlement infos: https://mysupport.netapp.com/site/support/support-api/catalog#operations-tag-entitlement-controller
vale harness
<@1002001094760730634> it would require building a new collector and it's not cl...
It's a bit tricky indeed. I think that as long as you renew the token using the refresh token, you're good, but if you let it expire the user as to make a new one.
loud crest
let me take this up internally to build the collector and figure out a way how to handle token refresh