Some F5 metrics are not being collected or exposed in Prometheus

[mink0119]

Describe the bug

Several F5-related metrics that are documented as available are not being collected or exposed in Prometheus at all.
When querying Prometheus (even with only the instance label), these metrics do not appear, which suggests that the metrics are not emitted by the collector or not exported from BIG-IP.
This is confusing because some of these metrics appear to represent fundamental runtime values that should exist when traffic is present.

To Reproduce
Steps to reproduce the behavior:

1. Deploy Application Study Tool (AST) with the OpenTelemetry Collector.
2. Ensure BIG-IP is actively processing TEST traffic (HTTP, TCP, DNS).
3. Open Prometheus UI. Run queries for the following metrics (with or without label filters):

f5.pool.availability.threshold
f5.pool.connection.max
f5.pool.queue_age.average
f5.pool.queue_age.recent_max
f5.profile.http.requests.passthrough
f5.profile.dns.server_queries
f5.profile.dns.server_responses
f5.profile.dns.tcp_bits_in
f5.profile.dns.tcp_bits_out
4. Observe that none of these metrics are returned.

Questions:

1. Why are these metrics not being collected or exposed?
2. Are these metrics conditional (profile-based, feature-based, or traffic-type–based)?
3. Are these metrics deprecated or not implemented in AST / OTEL Collector?
4. In addition to that, a detailed explanation of the metric itself would be very helpful.
   In the case of receiver_metrics.md, the descriptions are effectively just restating the metric names in sentence form. Because of this, it is very difficult to understand what these metrics actually represent in practice.