Feature Request: Add Custom REST endpoints option #243
Description
The default metrics OTEL collector exports are great, but there will always be cases where F5 customers have something in their REST API they would like as a metric.
Custom metrics (based on REST endpoints) could be helpful for temporary troubleshooting or as a permanent metric for something OTEL collector does not export by default, but is valuable for a specific customer.
This would be something similar to Telemetry Streaming custom_endpoints: https://clouddocs.f5.com/products/extensions/f5-telemetry-streaming/latest/custom-endpoints.html?highlight=custom
Ideally, customers could add a TMOS API path to their .yaml file (global or per-Big-IP) that OTEL could use as an extra REST API endpoint to query and export metrics from.
Some REST API endpoints may have lots of data, so supporting REST query filters would be helpful, such as /mgmt/tm/sys/version?$select=Version.
Wish-list would be the ability to do the same but for CLI commands like tmctl.