Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature Request: Add Custom REST endpoints option

Open
#243 2 comments 0 reactions 1 assignee View on GitHub

@mikempw is already working on this.

Since Sep 11, 2025.

Assessment

This issue has not been assessed yet.

Description

enhancement

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.

Dominant language
Python
Stars
106
Forks
43
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from f5devcentral/application-study-tool

All issues in f5devcentral/application-study-tool

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.