Feature Request : Allow specific commands to run so that we can define what metrics to be fetched

[arjun-udaan]

Hi,

This works great, thank you for providing this here,

One feature i think which would help is to allow specific commands to run on AOS so that we have more control on what metrics are exported

[slashdoom]

Can you provide examples of what you're looking for?

It does run specific commands, for example for interface stats on a non-CX switch...
https://github.com/slashdoom/aruba_exporter/blob/main/interfaces/interface_collector.go#L115
it runs both "show interfaces ethernet all" and "display interface".

But the hard part is parsing. Once run, its has to so all of this to parse those outputs into metrics...
https://github.com/slashdoom/aruba_exporter/blob/main/interfaces/parser.go#L314-L507

[arjun-udaan]

Yes, I understand; thank you for responding.
The point I make here is that we don't always want to export all of the metrics. For example, let's say we have 2000+ apps and simply want to capture up status and connected client count (ignoring RF). As it is a waste of infra resources to repeatedly pull RF data that is never utilized, could you suggest a means for us to configure which metrics to export even within a category (wireless)?

I do understand this is not a common use case.