1.37.4 — 16th June
Resolved Issues
Resolved custom attributes not captured in PreFlows or included in blocked spans
Resolved an issue where custom attributes configured in Apigee were not being captured during PreFlow execution and were not included in blocked request spans.
Custom attributes are now correctly captured and sent to the Traceable platform regardless of whether the request is blocked, ensuring complete span data for security analysis and observability.
1.37.3 — 12th May
This release includes internal improvements.
1.37.2 — 2nd May
Resolved Issues
Resolved fail-open behavior in blocking policy
Resolved an issue with the Apigee blocking policy to ensure it behaves correctly in fail-open mode.
When the blocking policy encounters an error or is unable to reach the Traceable platform, it now fails open, allowing traffic to pass through rather than blocking requests. This prevents service disruptions when the policy cannot complete its evaluation.
1.37.1 — 14th April
Updates
Configurable header export using prefix string matches
The Apigee agent now supports configuring which headers are exported using prefix string matches.
Previously, the header export behavior was fixed. You can now specify prefix strings to control which request and response headers are included in exported data, giving you finer-grained control over what is captured and sent to the Traceable platform.