Release notes¶
Release notes for F5 Insight 1.1.1, the on-premises observability and operational strategy solution for F5 Application Delivery and Security Platform.
Version 1.1.1 | June 2026
| Product | F5 Insight |
| Version | 1.1.1 |
| Release date | June 2026 |
| Deployment model | On-premises / self-hosted |
| Document revision | 1.1.1 |
About this release¶
Important
This is a patch release, not a full feature release.
System requirements¶
Host platform¶
| Component | Requirement |
|---|---|
| Operating system | F5-supported image |
| Architecture | x86_64 (AMD64) |
| CPU | Minimum eight vCPUs |
| Memory | Minimum 16 GB RAM |
| Storage | 500 GB minimum for default retention policy |
| Hypervisor images | QCOW and OVA |
Managed BIG-IP devices¶
| Component | Requirement |
|---|---|
| BIG-IP version | 17.5.x |
| Modules | Local Traffic Manager (LTM) required; DNS, Advanced Web Application Firewall (AWAF), Advanced Firewall Manager (AFM), Access Policy Manager (APM), Carrier-Grade NAT (CGNAT), and SSL Orchestrator (SSLO) supported |
| Management access | iControl REST API enabled; HTTPS reachable from F5 Insight host |
| Telemetry iRule | High-speed logging (HSL) enabled; syslog reachable from collector listener |
Fixed issues¶
This section details the bugs and issues resolved in this release.
DNS resolver cache metrics displayed internal names instead of DNS profile names
Issue: DNS resolver cache metrics (cache hits, misses, and updates) on the Local Traffic Manager (LTM) DNS dashboards displayed internal cache component names instead of the DNS profile names you configure. This made it difficult to correlate performance metrics with specific DNS profiles.
Fix: Updated the OpenTelemetry Collector to map cache components to DNS profile names during metrics collection. The collector now:
- Retrieves the DNS profile name from the BIG-IP API.
- Maps it to the associated cache component.
- Labels metrics with the correct DNS profile name instead of the internal cache name.
Impact: You now see the DNS profile names you configured (such as
/Common/MacDaddyor/Common/dns) directly on the LTM DNS dashboards.
Known issues¶
This release includes the following known issues.
- DNS zone NS detail data may not appear in F5 Insights after you configure DNS zone NS details and enable Analytics and Visibility Reporting (AVR) in BIG-IP. A fix is planned for an upcoming release.
- End-to-end throughput comparison dashboards in OTel Collector overview may not display data. This issue will be fixed in upcoming release.