1.10.0 — 22nd July
Resolved Issues
Truncated JSON payloads are no longer dropped
Previously, when a captured payload contained truncated JSON, either because the payload itself was truncated or because the agent truncated it for exceeding the allowed payload size limit, the agent treated it as invalid JSON and dropped it. The agent now recognizes truncated JSON and processes it, so these requests are captured rather than discarded.
Spans are no longer dropped when body decompression fails
Resolved an issue where a span could be dropped when a request or response body could not be decompressed, for example, when the body used an unsupported compression encoding. Such spans are now exported correctly rather than lost; only the body that could not be decompressed is dropped.
1.9.5 — 25th June
Resolved Issues
Updated Go dependencies to address security vulnerabilities
Updated the Mirroring Agent's system, networking, and cryptography libraries to newer versions that resolve several known security vulnerabilities.
1.9.4 — 24th April
Updates
Detection configuration support added to the mirroring agent
The mirroring agent now includes an updated Go Agent that supports detection configuration. This enables the mirroring agent to apply detection rules configured in the Traceable platform, ensuring consistent security evaluation across mirroring-based deployments alongside other agent types.
1.9.2 — 25th March
Resolved Issues
Improved handling of missing packets in TLS stream with configurable recovery
Improved how the mirroring agent handles gaps caused by missing packets in TLS streams. A new configuration option is also available to enable faster recovery when packets are missed. Previously, missing packets in a TLS stream could cause decryption to stall or fail. The agent now handles these gaps more gracefully, and the faster recovery option allows deployments with frequent packet loss to recover TLS decryption state more quickly.
Resolved the incorrect configuration for the libtraceable metrics exporter
Resolved an issue where the libtraceable metrics exporter was not correctly wired to the reporting configuration in the mirroring agent. The metrics exporter configuration is now correctly applied, ensuring that metrics are exported as expected when libtraceable metrics are enabled.
1.9.1 — 21st March
Updates
Added environment configuration support
The mirroring agent now supports configuring the environment name as part of the agent configuration. This allows you to associate captured traffic with a specific environment in the Traceable platform, consistent with how other Traceable agents identify environments.
Added support for installation as a user-level systemd service
The mirroring agent can now be installed and run as a user-level systemd service, enabling deployment on Linux machines without requiring root privileges. This makes it possible to run the mirroring agent under a non-root user account, improving security posture for deployments where root access is restricted.
Added CloudFormation templates and Terraform scripts
CloudFormation (CF) templates and Terraform scripts are now available for deploying the mirroring agent. These templates simplify infrastructure-as-code deployments, allowing you to provision and configure the mirroring agent as part of your existing cloud automation workflows.
TLS key server now uses TCP4-only listener
The TLS key server in the mirroring agent now listens exclusively on TCP4 (IPv4), replacing the previous behavior that could bind to both IPv4 and IPv6. This provides more predictable network binding behavior and avoids connectivity issues in environments where dual-stack networking is not required or desired.
Updated Terraform scripts to use aws_lambda_invocation resource
The Terraform scripts for the mirroring agent now use the native aws_lambda_invocation resource instead of a custom Terraform provider for invoking AWS Lambda functions. This removes the dependency on a custom provider, improving compatibility with standard Terraform tooling and reducing maintenance overhead for infrastructure deployments.
Added cloud host metadata to spans
The mirroring agent now captures and includes cloud host metadata in spans for deployments running on AWS, ECS, GCP, and Azure. This enriches span data with cloud context such as instance identifiers and resource attributes, making it easier to correlate captured traffic with specific cloud resources in the Traceable platform.
Libtraceable metrics now enabled by default
Libtraceable metrics are now enabled by default in the mirroring agent. This allows operational metrics from the agent to be exported automatically without additional configuration, improving observability for mirroring agent deployments out of the box.
Added Server-Sent Events (SSE) support
The mirroring agent now supports collecting traffic data via Server-Sent Events (SSE). This enables the mirroring agent to capture and forward SSE-based API traffic to the Traceable platform, thereby extending coverage to applications that use SSE to stream data to clients.
1.8.1 — 22nd January
Traceable’s Mirroring Agent 1.8.1 provides the following:
Updates
Set TA_DATA_DIR for All Deployment Methods
Set the TA_DATA_DIR environment variable by default across rpm, deb, install script, and Terraform deployments for consistent data directory handling.