4.34.0 (Feb 18, 2026)
🗓️ Release Date: February 18, 2026
🚀 Version: 4.34.0
Data Correlation Enhancements
AGL-1095 Capture Insight should expose data even when flows are not correlated - Capture Insight now exposes data even when flows are not correlated.
AGL-1037 Inter‑correlate DNS_ENUM with SIP Registration flows - DNS_ENUM events are now inter-correlated with SIP Registration flows to identify root causes of failures.
AGL-1003 Revisit intra correlators (protocol parsers) to avoid gnerating duplicate intra sessions - Intra correlators have been revisited to prevent the generation of duplicate intra sessions.
UI/UX Improvements
AGL-1012 Part 2 [UI Implementation] Flow Details page Enhancements - Flow Details page now includes sorting by timestamp and precise frame navigation.
AGL-964 [UI/UX]: Improve analysis creation workflow to explicitly ask about including User Plane. - The analysis creation workflow now explicitly asks about including the User Plane.
AGL-946 in HTTP2 parser replace interface content with concatenation of http2_5GC_reference_point and http2_dst_service - HTTP2 parser interface content now shows concatenated service references for clarity.
AGL-800 Add a comments section for feedback in userplane - A comments section has been added to userplane for user feedback and editing.
HTTP/2 Validation
AGL-1027 Apply UI fixes to support http2 header validation - UI fixes have been applied to support HTTP/2 header validation.
AGL-963 HTTP/2 payload/header validation - HTTP/2 payloads and headers are now validated against specifications.
Bugs
AGL-1096 AGILITY Keycloak - Eliminate Unecessary Logs - Unnecessary logs in Keycloak and open-telemetry pods have been removed to reduce noise and improve troubleshooting.
AGL-1081 [backend] OOM (out-of-memory) issue in a backend user-plane service - Optimized memory usage in the backend user-plane service by implementing stream parsing and batch commits.
AGL-1071 [UI] Network Plane flow list requires page refresh to display all detected callflows - The Network Plane flow list now updates automatically without requiring a page refresh.
AGL-1052 AGILITY Restart backend Issue - Fixed the issue causing multiple pod restarts in the AGILITY instance when under higher loads.
AGL-1050 [CLI] - Missing secret in kube-system - Ensured the secret is correctly set in the kube-system to prevent upgrade issues with Strimzi or PGO.
AGL-1049 Call Split issue for voxx pcap - Resolved the call split issue for voxx pcap, ensuring correct session and subflow identification.
AGL-1048 Conference calls' "Call Part of Conference" flag setted as "No" - Corrected the "Call Part of Conference" flag to "Yes" for conference calls in the specified pcap.
AGL-1039 Fix validation error in AnalysisProfile model - Fixed a validation error in the AnalysisProfile model to prevent 500 errors during pcap uploads.
AGL-1038 Prediction is HTTP2_ERROR, it should be HTTP2_503_Service Unavailable - Corrected the prediction from HTTP2_ERROR to HTTP2_503_Service Unavailable for accurate error reporting.
AGL-1033 Incorrect body for /v1/intent-based-diagnostic/evaluation-scenarios in openapi - Fixed the incorrect body issue for /v1/intent-based-diagnostic/evaluation-scenarios in OpenAPI.
AGL-1028 camelCase not supported by v1/callflows/similarity/feedbackTransaction - Resolved the camelCase issue in the v1/callflows/similarity/feedbackTransaction API to prevent 400 errors.
AGL-983 400 Client Error for IBD Integration - Fixed the 400 Client Error for IBD Integration, ensuring successful API requests with the correct payload.
AGL-945 Data pipeline incorrectly parses interface as scpPrefix instead of downstream interface - Corrected the data pipeline to accurately parse and report the downstream interface instead of stopping at scpPrefix.
AGL-861 SIP Unfolded view is truncating frame number column - Fixed the issue causing the SIP Unfolded view to truncate frame numbers, ensuring full visibility.
AGL-249 Storage class configuration - Improved storage class configuration to allow flexibility and prevent forced default usage in Kubernetes clusters.
AGL-228 [UI] - Using different ports in the agility-proxy do not work - Resolved the issue with agility-proxy not respecting different ports, ensuring proper UI access via NodePorts or port-forwarding.
Need Help?
If you have any questions or need assistance with these updates, feel free to reach out to the AGILITY support team; we’re here to help.