Release notes for Instana agent bundles

Features

This release adds the following features:

• Selective monitoring now supports Kubernetes namespaces when NAMESPACES_DETAILS_PATH is present. The Operator sets this environment variable that contains the location to a yaml file.
  • When the environment variable is set, the agent caches content for each namespace by using the instana-workload-monitoring label.
  • The following values are evaluated: <absent>, true, false, apm, and infra.
  • If INSTANA_SELECTIVE_MONITORING is set to DEFAULT or has an empty value, the agent operates in normal mode. All namespaces with instana-workload-monitoring=false are ignored.
  • If INSTANA_SELECTIVE_MONITORING is set to OPT_IN, the agent operates in the selective monitoring mode. The agent monitors only the processes that are in a namespace, which have instana-workload-monitoring=true, instana-workload-monitoring=apm, or instana-workload-monitoring=infra. All processes with instana-workload-monitoring=false are ignored.
• An internal service is added to monitor configuration file changes and notify if there is a change. This service uses the scheduler to reduce the overall thread count.

Fixes

• Previously, only successful container metadata was cached. This issue is now fixed, and also a failure to look up container metadata is cached.
• Previously, cgroups, such as /init.scope and /mde, were identified as potential containers. This issue is now fixed after adding a table of known non-container cgroup names.
• Previously, ContainerD lookup failed when multiple sockets were present on the host. This issue is now fixed by using the socket that is assigned to the ContainerD process.

Features

This release adds the following features:

• Caching Kubernetes labels for the following container types to support selective monitoring: ContainerD, CRI-O, Docker, and Podman
• Counting tasks for OTel gRPC by using the ExecutionPipeline

Fixes

• Previously, the system might fail reading the configuration.yaml file if the file contained non-UTF-8 characters. This issue is now fixed by checking for non-UTF-8 characters.
• Previously, the system might display incorrect data while reading cgroup data for container metrics. This issue is now fixed by checking if any process is still active for this cgroup.
• Previously, OTel HTTP connections were cached forever. This issue is now fixed by removing closed connections from the internal cache.
• Previously, OTel HTTP connections might overload the thread pool. This issue is now fixed by only evaluating open connections.

Features

This release adds the following features:

• You can now enable OpenTelemetry HTTP and gRPC components by using the INSTANA_AGENT_OTEL_HTTP and INSTANA_AGENT_OTEL_GRPC environment variables (default value is null).
• You can now configure default deflate level (0–9) by using INSTANA_BACKEND_DEFLATE_LEVEL variable (default value is null).
• Integer and Boolean settings (with null fallback) are now fetched from the agent environment through the new runtime and runtime-api methods.
• The agent now uses ExecutionPipeline for both JVM connections and HTTP endpoint handling in the socket-server.
• The new built-in helper ThreadWatcher monitors stuck threads. (default is 60 s. You can configure this by using the environment variable INSTANA_THREAD_WATCHER_TIMEOUT_SECONDS).
• Tasks are now wrapped with pre/post hooks, thread-watching, pool statistics, and task monitoring by using the orchestrator-API interfaces.
• The agent now looks up nested configuration values and returns checked exceptions in callables and runnables by using the new helpers in the util bundle.
• Span-links support is added for both OpenTelemetry base and service bundles.
• OTel gRPC and HTTP components now support stuck-thread detection and task counting by using ExecutionPipeline. You can override their default ports either by using INSTANA_AGENT_OTEL_GRPC_PORT and INSTANA_AGENT_OTEL_HTTP_PORT environment variables (default value is null) or by modifying the configuration.yaml file. For more information, see OpenTelemetry configuration

Fixes

• Previously, log-level synchronization with JVMs began immediately, which resulted in race conditions in internal test validation. This issue is now fixed by delaying the log-level sync start by one minute.

Fixes

• Previously, when you reloaded the in-memory ClassLoader, the stored classes were removed, which resulted in missing definitions after reloading a sensor. This issue is now fixed by preserving the class-holding data structure in a global in-memory representation.
• Previously, when a Spring-Boot Java agent was started, the javaagent-loader thread was blocked if ManagementFactory was not initialized. This issue is now fixed by preloading a default ManagementFactory before starting any sensor agents in the javaagent-loader.
• Previously, when a backend connection was reset, the direct-memory guards were left in an inconsistent, non-thread-safe state, which caused the threads forwarding metrics or traces to hang. This issue is now fixed by introducing the globally shared ByteBuffer allocator with built-in timeouts.

Features

• You can now configure a minimum heap threshold for the in‑memory classloader by using the INSTANA_AGENT_LOADER_MIN_IN_MEMORY_HEAP_MEGABYTES environment variable (default value is 100 MB), which is enabled by the the upgraded javaagent‑loader 1.3.68. Make sure that you set the environment variable in the target JVM.

Fixes

• Previously, when you used the in‑memory ClassLoader on JVMs with limited heap, OutOfMemory errors occurred. This issue is now fixed by disabling the in‑memory ClassLoader when maximum heap is below the configured threshold (100 MB by default) and falling back to file‑based attachment.
• Previously, the agent issued a Unix-specific command kill -3, which failed on Windows systems. This issue is now fixed by suppressing the kill -3 call on Windows systems.

Features

This release adds the following features:

• The agent-jvm-handling bundle now supports Java 24 tracing with upgraded javaagent-loader (1.3.67), instrumentation-boot (1.1.31), and instrumentation-shared (1.0.146).
• A new runtime service is added to inspect mount options on Unix-based systems.
• A dedicated socket-server API service is now available to start and stop Netty-based socket servers.
• The task-orchestrator’s Scheduler is now provided as a prototype, giving each consumer its own instance while using a shared global thread pool.
• The sensor API now includes a Streaming Process Output helper and JVM job-name lookup on IBM i.

Fixes

This release fixes the following issues:

• Previously, sensitive fields could be exposed in the output of the process-listing (ps) task and included in support bundles. This issue is now fixed by hiding all sensitive data during support information collection.
• Previously, Support Information ZIP archives included a leading slash, which prevented file extraction on Windows. This issue is now fixed by removing the leading slash.
• Previously, determining which JVMs to ignore could enter an infinite loop when following parent-process chains. This issue is now fixed by breaking the circular lookup loop.
• Previously, applications running on J9 JVMs with custom executables or attach directories were not detected correctly. This issue is now fixed by enhancing the J9 detection logic to recognize custom paths.
• Previously, Byte Buddy attachments would fail on Unix hosts with /tmp mounted noexec, causing tracing setup to break. This issue is now fixed by detecting noexec on /tmp and falling back to JDK-based attachment.
• Previously, if container metadata was null, the agent attempted to parse invalid data and returned errors. This issue is now fixed by checking for null metadata and returning an empty map instead of parsing invalid data.
• Previously, all consumers of the Scheduler shared a single instance, which resulted in new tasks being blocked when one consumer stopped. This issue is now fixed by exposing the Scheduler as a prototype so that each consumer gets its own instance.
• Previously, shutting down the Otel gRPC socket server could hit a race condition that blocked termination indefinitely. This issue is now fixed by using the new socket-server API service to coordinate the shutdown, which ensures a stable, deadlock-free termination.
• Previously, shutting down the Otel HTTP socket server could hit a race condition that blocked termination indefinitely. This issue is now fixed by using the new socket-server API service to coordinate the shutdown, which ensures a stable, deadlock-free termination.
• Previously on IBM i, only the numeric process ID was shown instead of the full job name. This issue is now fixed by fetching and displaying the complete job name.

Fixes

This release fixes the following issues:

• Previously, exceptions that occurred during the activation of the CriClient and channel caches were not captured, which led to unhandled errors during startup. This issue is now fixed by capturing and logging the exceptions during the activation of these components.

Features

This release adds the following features:

• A dedicated support bundle for Karaf-related support collection data is added. The new agent-support-karaf bundle also adds support tasks to collect bundle tree dependencies and header information.
• The agent-jvm-handling bundle now supports a configurable timeout for JVM connections by using the INSTANA_SOCKET_CONNECTION_TIMEOUT environment variable (default value is 45 seconds).

Fixes

This release fixes the following issues:

• Previously, CRI-O Sensors stopped functioning during updates because process collection was delayed. This issue is now fixed by making sure that that process collection is fully completed before proceeding with updates.
• Previously, an exception occurred during an upgrade if CRI-O containers were stopped immediately after startup. This issue is now fixed by performing a version check during client initialization to preload necessary classes.
• Previously, the use of selective monitoring sometimes resulted in incomplete data collection for containers and processes. This issue is now fixed by querying all containers and processes without relying solely on selective monitoring.
• Previously, negative values processed during startup of cgroup data led to spikes in memory and CPU usage. This issue is now fixed by normalizing any negative values to zero.
• Previously, cgroup detection was attempted on non-Linux systems and systems without a proper /proc directory, which caused errors. This issue is now fixed by restricting cgroup detection to Linux hosts with a valid /proc folder.
• Previously, memory usage for CGroupV2 was calculated inaccurately. This issue is now fixed by correctly calculating memory usage as the sum of file and anon memory.
• Previously, Windows JVM attachments used a single global TEMP directory regardless of user privileges, which caused conflicts and failing attachments. This issue is now fixed by making sure that the attach process uses the TEMP directory of the user.
• Previously, there was no mechanism to control the timeout for JVM connections, which sometimes led to connection issues. This issue is now fixed by adding an environment variable that you can use to configure the JVM connection timeout.
• Previously, failures to bind ports for ingress communications did not trigger any retry attempts, leading to connectivity problems. This issue is now fixed by implementing a retry mechanism for port binding failures.
• Previously, null values in environment variable maps during container-specific queries could lead to errors. This issue is now fixed by adding proper handling for null cases.

Features

This release adds the following features:

• The agent framework now supports method-based trace logging. Although this feature is available through framework, currently one must annotate individual methods to enable trace logging. The full adoption is planned to be released in the future releases.
• The Log4j2 pattern is now automatically updated on startup to include the method information by using the pattern, | %replace{%X{method}}{^(.+)$}{$1 | }.
• Enhanced debug logging for processes is now available during support information collection. Every process type now provides detailed internal debug data to facilitate troubleshooting and analysis.

Fixes

This release fixes the following issues:

• Previously, PID 1 was misidentified as a container process. This issue is now fixed by correctly identifying PID 1 as a host process.
• Previously, the tracer announce procedure failed on containerized workloads. This issue is now fixed by relaxing the container environment lookup for ContainerD processes and correctly handling PID 1 as a host process.
• Previously, a NullPointerException error occurred in ContainerD processes when the namespace was null. This issue is now fixed by adding a null check.
• Previously, the cgroup data lookup did not correctly utilize available processes within a container. This issue is now fixed by using any process within the container for cgroup data lookup.

Features

This release adds the following features:

• Additional gRPC components are now exported to extend the agent’s communication capabilities.
• The agent configuration steps are run sequentially in a predefined order to improve the configuration process.
• The agent can now replace configurations from both environment variables and files within the agent context.
• Automatically merges sensor data from sources that share the same name and entityId.
• The agent now provides selective monitoring for container environments.
• Activates the internal CriClient by default, ensuring seamless integration with modern container runtimes.

Fixes

This release fixes the following issues:

• Previously, the JVM attachment process would fail on J9 JVMs when any of the environment variables (IBM_JAVA_OPTIONS, JAVA_TOOL_OPTIONS, or _JAVA_OPTIONS) defined the com.ibm.tools.attach.directory explicitly. This issue is now fixed by evaluating these environment variables and updating the attach-tools (v1.17.2) to correctly handle an explicit directory definition.
• Previously, when the host had a large number of processes with identical arguments and environment variables, the agent would run out of memory. This issue is now fixed by interning strings, arguments, and environment variables, which reduces the memory footprint.
• Previously, a file permission issue occurred when copying files into a rootless Podman container under strict umask settings. This issue is now fixed by applying file permissions to the intermediate file before it is copied.
• Previously, in Red Hat OpenShift Container Platform 4.18 environments where crun is the default container runtime, the agent did not use the internal CriClient by default. This issue is now fixed by handling INSTANA_USE_CRI_CLIENT as true if the variable is absent, which ensures compatibility with the new container runtime default.
• Previously, a jail root lookup issue on Solaris caused all processes to be incorrectly identified as jail root. This issue is now fixed by restricting jail root process handling to Linux systems only.

Features

This agent release adds the following features:

• A new method is added to query all known process IDs (PID) for process‑based sensors. This new method improves the tracking and monitoring of processes.
• The process handling bundle now uses an event‑based update mechanism instead of the previous timer‑based approach to update iptables in Garden-based containers.

Fixes

This release fixes the following issues:

• Previously, the cgroup bundle conducted unnecessary cgroup version checks on non‑Linux systems. This issue is now fixed by limiting the version check to Linux environments.
• Previously, the memory parsing process in the cgroup bundle added wrong limits. This issue is now fixed by adding two new helpers, parseMemoryDataCgroupV1 and parseMemoryDataCgroupV2 to read the correct memory files.
• Previously, the JVM handling bundle reported a jvm_tmp_not_available monitoring issue when the /tmp directory was unavailable for jail root-based JVMs. This issue is now fixed by updating the monitoring issue to agent_tmp_directory_missing and adding support for the continuous monitoring of jail root JVMs.
• Previously, the exceptions that were identified in the symbolic link checks on Linux were logged at a high level of detail, which cluttered the logs. This issue is now fixed by reducing the log level to DEBUG.
• Previously, the process handling bundle encountered issues with normalizing broken paths on Windows. This issue is now fixed by enhancing the logic for Windows path normalization.

Features

This agent release adds the following features:

• Support for jail root is added for both JVMs and processes.
• Handling of the capabilities endpoint in the agent backend is enhanced.
• OpenTelemetry integration is improved by linking the host and OpenTelemetry entities by using MachineId.

Fixes

This release fixes the following issues:

• Previously, instrumentation logs experienced a memory leak. This issue is now fixed by updating instrumentation-shared files to 1.0.144.
• Previously, the gRPC server started as part of the agent grpc bundle even when it was not required. This issue is now fixed by moving the the gRPC server from the agent grpc bundle to the agent open telemetry grpc bundle.

Fixes

This release fixes the following issues:

• Previously, the location of ctr on Tanzu Clusters was not identified correctly, which caused issues with container operations. This issue is now fixed by adding the logic to accurately detect the ctr location in such environments.

Features

This agent release adds the following features:

• The UnifiedProcess abstraction is added to offer extended functionalities to manage normal processes and CRI processes.
• CriClient and its associated configurations are added for seamless interaction with CRI API gRPC endpoints.
• The agent cgroup bundle is added to enhance container metric management.
• The agent util bundle now provides improved resource and thread management.

Fixes

This release fixes the following issues:

• Previously, entities in the backend were marked as offline due to missing data. This issue is now fixed by keeping entities alive with empty data.
• Previously, the agent's handling of empty files caused unexpected behavior. This issue is now fixed by returning a zero-length byte array when empty files are encountered.
• Previously, the asynchronous process for adding public IP gateway interests caused delays. This issue is now fixed by changing the operation to be synchronous.
• Previously, in rootless Podman environments, temporary files that were created with the correct set of permissions were overwritten because of the umask settings. This issue is now fixed by explicitly setting the file permissions after the temporary file has been created.

Features

This agent release adds the following features:

• The Instana agent has stopped the support for Java 8. You must use Java 11. When you start newly installed agents with Java 8, the agent now shows a monitoring event. This monitoring event is relevant only if you install or use your own JVM. Containerized or package-based agents already use Java 11.

Fixes

This release fixes the following issues:

• Previously, in rootless Podman environments, copying files to the target container might fail as the agent did not define a permission set for the temporary file. This issue is now fixed, and the temporary files are created with rwxr-xr-x.
• Previously, the agent failed to set any socket information for a ContainerD instance when multiple sockets are present. This issue is now fixed, and the agent sets the correct socket information for a ContainerD instance.
• Previously, the agent had a race condition on JVM connections and kept a connection open even though it was internally already marked as closed. The wrong connection was removed only when the agent was restarted. This issue is now fixed, and the agent correctly closes the broken connection.

Fixes

This release fixes the following issues:

• Previously, in rootless Podman environments, the df command failed a check that is used to verify the available size within a container before a JVM attachment. This issue is fixed, and the df command is now run by the user as required.
• Previously, during the startup, the agent failed to execute some commands that are necessary to identify if the agent is running on a host that supports various container environments. The failure occurred because the default timeout to run the command was one second, which was not sufficient. This issue is fixed, and you can now control the timeout by using a new environment variable INSTANA_COMMAND_RUNNER_TIMEOUT_SECONDS=5, which has a default duration of 5 seconds.
• Previously, the agent did not include the --user argument while executing a nsenter command when the environment variable NSENTER_MODE_ENABLED=true was set. This issue is fixed, and the agent now uses the --user argument when required.

Fixes

This release fixes the following issues:

• Previously, the uniqueId from the agent on Linux was not deterministic when the main interface identified by Sigar was a vlan interface. This was because these interfaces are not ordered by the host. This issue is fixed, and the vlan interfaces are now sorted first if names that start with vlan are identified.
• Previously, the uniqueId from the agent on Windows used the KM-TEST Loopback Adapter interface. Because this is a loop-back interface, the MAC address was not unique. This issue is fixed, and the agent now ignores the KM-TEST Loopback Adapter interface when other interfaces are available.
• Previously, the agent did not log when the agent key for a backend was wrong. This issue is fixed, and the agent now logs a warning every 10 minutes when it receives a 403 error report from the backend, which indicates that the agent key is wrong.

Features

This agent release adds the following features:

• The agent now has a Selective Monitoring mode. This mode adds the ability to monitor only the processes that hold specific environment variables.

  The agent checks if the process is started with the environment variable INSTANA_SELECTIVE_MONITORING.

  • If INSTANA_SELECTIVE_MONITORING is set to DEFAULT or has an empty value, the agent operates in normal mode. All processes with INSTANA_MONITORING=false and INSTANA_IGNORE=<any value> are ignored.

  • If INSTANA_SELECTIVE_MONITORING is set to OPT_IN, the agent operates in Selective Monitoring mode. The agent monitors only the processes that have INSTANA_MONITORING=true, INSTANA_MONITORING=apm, or INSTANA_MONITORING=infra. All processes with INSTANA_MONITORING=false and INSTANA_IGNORE=<any value> are ignored.

  Currently, there is no differentiation between apm or infra modes.

Fixes

This release fixes the following issues:

• Previously, the agent always executed the id command in the context of the agent, which could fail if the agent was running in a container. This issue is fixed, and the id command is now executed on the host.
• Previously, the agent failed to start because of Snakeyaml imports that required a minimum version of 2. This version was not present in the agents with agent bootstrap version earlier than 1.2.9. This issue is fixed, and the agent util now imports Snakeyaml versions 1 to 3.

Fixes

This release fixes the following issue:

• Previously, the agent only checked if the /etc/passwd file contained a user ID to identify a user. This issue is fixed, and the agent now correctly identifies a user by using the id command instead.
• Previously, the agent had a fallback setting to use the sudo command on AIX for the JVM attachment. However, the fallback was not always possible as the sudo command is not available on AIX by default. This issue is fixed, and the agent now only uses the su command on AIX for the JVM attachment.

Features

This agent release adds the following features:

• The agent now has a dedicated bundle to handle all activities that are related to processes. These activities also include the abstraction around containerized processes.
• The agent now collects a validation of the confiugration.yaml. You can retrieve this data by clicking on the Collect Support Information button on the agent dashboard.

Fixes

This release fixes the following issues:

• Previously, the agent did not check if the /etc/passwd file had more characters to evaluate when a user ID was not found in the file. This issue is now fixed, and the agent correctly identifies when the checking of the file is finished.
• Previously, the agent did not evaluate all the available namespaces of the host system when executing the nsetner -a command. This issue is fixed, and the agent now checks all available namespaces and adds them explicitly to the nsenter command.

Features

This agent release adds the following features:

• The agent now collects a thread dump of all agent threads. You can retrieve this data by clicking on the Collect Support Information button on the agent dashboard.

Fixes

This release fixes the following issue:

• Previously, the agent did not use the correct PATH when it was run in a container on RKE2. This issue is now fixed, and the agent correctly identifies when it is run on RKE2. The agent also adds /var/lib/rancher/rke2/bin to the PATH if it is missing.
• Previously, the agent used a thread from the scheduler during rebooting or resetting. When the agent installed other features at the same time, the agent could get stuck on the reboot or reset. This issue is now fixed, and the agent uses a thread from the main group and finishes the reboot or reset.
• Previously, the agent used the su command to change the user on IBM i when the agent was run as the root user QSECOFR. This attachment failed because IBM i does not support su. This issue is now fixed, and the agent uses the custom ibmi-sudo executable to change the user.
• Previously, the agent used the sudo command to change the user on z/OS as a fallback. This attachment failed because z/OS does not support sudo. This issue is now fixed, and the agent only uses the su command to change the user.
• Previously, the agent did not provide details about the threads that are stuck when the scheduler and executor stopped the threads for the agent to stop, restart, or update. This issue is now fixed, and the agent writes a thread dump into the logs when the threads are stopped.
• Previously, the agent attached to JVMs that are part of a buildah step. This issue is now fixed, and the agent ignores JVMs that have a parent process with the name buildah-chroot-exec.

Fixes

This release fixes the following issue:

• Previously, the agent returned a NumberFormatException error in the PodmanUtil service and failed to start most of the internal services on AIX systems. This error occurred because the UIDs on AIX exceeded the maximum integer range that was specified in the Agent 1.2.6 release. This issue is now fixed, and the agent parses long UIDs and starts up correctly.

Features

This agent release adds the following features:

• The agent now supports rootless Podman to identify if a process is started by the root or a user. To use this feature, make sure that Podman sockets are available for both root and user.
• The agent now provides an abstraction layer to access files for rootless Podman. The abstraction is required because the existing Java Nio-based file access has the same user as the agent and therefore cannot interact with the user file system.
• You can now configure the agent to send less data to the backend from the sensors that collect data at lower granular intervals. For example, process sensors and container sensors. Decreasing the amount of data that is sent to the backend reduces the counted traffic and the computation on the backend.
• The agent now generates lesser number of metrics on the backend to debug traces and logs. This reduces the load on the backend.

Fixes

This release fixes the following issues:

• Previously, the agent marked a process as not running after an update of the agent feature. This was because the configuration service that is used to determine whether a process must be ignored is not ready at startup time. This is now fixed and the agent awaits the configuration service before deciding whether a process is ignored.

Fixes

This release fixes the following issues:

• Previously, the agent failed to run a docker exec command with a user switch. This was because the agent added the -u flag after containerId, which is invalid. This issue was noticed in the Agent 1.2.3 release. This issue is now fixed.
• Previously, the agent created a jvm_instrumentation_shared_absent monitoring issue when a JVM was absent or when the connection to the JVM was already closed. This issue is now fixed and the agent creates the jvm_instrumentation_shared_absent monitoring issue when the JVM is still active.

Fixes

This release fixes the following issues:

• Previously, the agent became unresponsive if multiple restart requests were raised at the same time. This issue is now fixed and the agent ignores incoming restart requests in the first minute.
• Previously, the agent did not check whether the instrumentation-shared files exist. If the files were absent, the java-tracer did not start and a NoSuchFileException was added to the logs. This issue is now fixed and the agent checks if the instrumentation-shared file is present. The agent also creates a monitoring issue with the name jvm_instrumentation_shared_absent if the instrumentation-shared is absent.
• Previously, the agent generated multiple logs when an update occurred while the agent was forwarding logs to the backend. This issue is now fixed and logs are not created when the agent is updated.

Features

This agent release adds the following features:

• The agent now collects the configurations that are shared with a sensor at startup time or as part of a configuration update. You can retrieve this data by clicking on the Collect Support Information button on the agent dashboard.
• The agent now supports JDK-based attachments along with Byte Buddy-based attachments. You can specify to use JDK-based attachments by setting the environment variable INSTANA_JVM_BYTEBUDDY_ATTACHMENT_ENABLED as false.

Fixes

This release fixes the following issue:

• Previously, the agent created a new string when comparing the inventory as part of the discovery check. This issue is now fixed and new strings are not created anymore.

Fixes

This release fixes the following issue:

• Previously, the vault configuration integration failed to start and became unusable when the agent bundle was updated after the vault was started. This issue is now fixed, and the vault configuration integration works after an update.

Bundle split

This release splits the agent bundle into multiple bundles. The splitting of bundles reduces the duration of agent downtimes during an update and ensures that the components that are not updated are run without interruption. This agent release contains the following bundles:

• agent 1.1.729: The main agent bundle.
• agent backend API 1.0.0: Services required for other agent bundles for backend connection.
• agent backend 1.0.0: The implementation of the backend connection.
• agent backend util 1.0.0: Utility bundle for backend-related components.
• agent internal API 1.0.8: Services required for other bundles that are provided by the agent bundle.
• agent Jaeger tracer 1.0.0: The Jaeger Tracer component.
• agent memory API 1.0.0: Services required for other bundles for memory access.
• agent memory 1.0.0: Implementation of the memory access.
• agent runtime API 1.0.0: Services required for other bundles of the agent that allow access to the runtime-related data.
• agent runtime 1.0.0: Implementation of the runtime-related data.
• agent self profiling 1.0.0: Self-profiling capability of the agent.
• agent socket server API 1.0.0: Services required for other bundles of the agent for the main agent socket server 42699. Mainly holds counter related information.
• agent socket server 1.0.0: The implementation of the main agent socket server that runs on port 42699.
• agent task orchestrator API 1.0.0: Services required for other bundles for task orchestration.
• agent task orchestrator 1.0.0: The implementation for the task orchestration. Holds the Scheduler and Executor services.
• agent util 1.0.0: Helper bundle with static helpers that are not part of any API.
• agent Zipkin tracer 1.0.0: The Zipkin Tracer component.

Features

This agent release adds the following features:

• Java Instrumentation now supports Java 23.
• The agent now supports a special environment variable INSTANA_BIND_ALL_INTERFACES. If this environment variable is set to true, the agent binds to all interfaces and announces the interfaces when the agent monitors Java workloads. This feature is required when the container uses Macvlan.
• The agent now tracks aborted requests on the 42699 endpoint for internal monitoring.

Fixes

This release fixes the following issues:

• Previously, an internal service of the agent would be absent if a temporary directory on the host was corrupted. Now, the agent catches this exception and the internal service remains intact.
• Previously, the agent would time out on the java -version check after 5 seconds. This timeout is now increased to 10 seconds.

Features

This agent release adds the following feature:

• The agent now runs on AS400/IBM i OS.

Fixes

This release fixes the following issues:

• Previously, the agent showed the agent-bundle version on the / path. This issue is now fixed, and the agent now displays the agent version.
• Previously, the agent ignored connections from JVMs if they were marked as unstable. These markings did not timeout. The timeout for the markings is now fixed, and the potential unstable connections are retried again after 5 minutes of the timeout.

Features

This agent release adds the following feature:

• An internal API is added to the host agent that enables the sensors to request for the process environment configuration that is already in discovery.

Fixes

This release fixes the following issue:

• Previously, J9-based JVMs were excluded from the new attachment that was added with Agent 1.1.721 because these JVMs required the stat command, which was not available on AIX. This issue is now fixed and the JVMs are included in the new attachment because the stat command is replaced with the istat command.

Fixes

This release fixes the following issues:

• Previously, the Host Agent added a dedicated Thread Pool for discovery requests. An edge case was identified when the Agent was receiving too many discovery requests on startup. In that case, the Host Agent might not handle any other Request and failed to respond to health checks. This overload might lead to restarts on Kubernetes. This issue is now fixed and the Host Agent is no longer restarted.
• On Solaris, the Host Agent checks if the <java-home>/jvm/jre/lib/sparcv9/jspawnhelper is executable. Now, the Host Agent notifies the user with a Monitoring event.
• Previously, the Host Agent showed the command that is used on the java -version process in an error case. As this command can display secrets, the used command is no longer shown.

Changes

• Previously, Opentelemetry monitoring was deactivated by default. The new default is activated. For more information, see Configuring OpenTelemetry data ingestion.

Fixes

This release fixes the following issue:

• Previously, the Host Agent verified incoming data on the connection and closed it if no traffic was observed within 600 seconds. An edge case was identified when the Agent loses connection to the Instana backend every 30 seconds. Closing the connection led to extra load within the JVM. This issue is now fixed and the Host Agent now checks the incoming data at 200, 400, and 600 seconds. If no data reaches the agent for 600 seconds, the connection is marked as unstable and closed.

Fixes

This release fixes the following issues:

• Previously, the Host Agent ignored a process after reading the content in /proc/<pid>/<something> had a timeout. The default timeout was 5 seconds, which got triggered mistakenly in Host Agents running on overloaded hosts. In such cases, the Agent mistakenly ignored the process and did not retry it. This issue is now fixed, and the Host Agent handles potentially broken processes with a staged approach. The Host Agent now supports multiple stages for a process. Successful reading of process data resets the counter. The list of the ignored processes is reset every 10 minutes.
• Previously, in some cases within the Host Agent, the flow expected a connection to be removed to run a full reattachment. This reattachment is only possible if the connection is removed and is not added back within a timeout of 20 seconds. This issue is now fixed, and the connection between the Host Agent and JVM is now removed, if the connection is marked as closed.
• Previously, a regression with J9 based JVMs occured that required the stat command, which was not available on AIX. This issue is now fixed and now the JVMs that run on AIX are excluded from the new attachment that is added with Agent 1.1.721. The new attachment is enabled again when stat command is replaced with istat command.

Fixes

This release fixes the following issues:

• An environment variable CONTAINERD_SUPPRESS_DEPRECATION_WARNINGS with the value true is added to the ctr exec operations. This environment variable is to exclude deprecation warnings that might interfere with parsers in the Agent.
• The evaluation of a process and the PID that reaches the 42699 port of the Agent is delayed. Computation is completed when the field is requested in code. When you make computation optional, the Agent executes other important tasks.

Fixes

This release fixes the following issues:

• Process with Arguments on Windows were ignored if they contained characters outside of the UTF-8 area.
• The Javaagent Loader inside a JVM leaks on Exit Hooks for file references of the Agent when the attachment works, but the communication to the Agent failed afterward
• When the agent attaches to a JVM, the Agent places files in <TMPDIR>/.instana with read and execute permissions and excludes the write permission for everyone.
• The Agent now parses the output of docker info when Docker is available to save the location of the Docker Root Dir. This information is used to correctly identify Docker containerIds.

Fixes

This release fixes the following issues:

• Better logging when java -version fails. The log now contains the command and the output that failed to be parsed.
• JVM attachments now always use the attach-tools-<version>.jar, which is placed in <TMPDIR>/.instana to allow attachments against JREs and 32-bit JVMs on Windows.
• The Agent monitors the Metaspace and issues a restart if the available space is under 10 MB for over 30 minutes. This restart reduces the risk of an OutOfMemoryError:Metaspace.

Fixes

This release fixes the following issue:

• JVM monitoring: Ignore SAP NetWeaver classes to mitigate class loading issues.

Fixes

This release fixes the following issues:

• JVM monitoring: Support for Virtual Threads.
• Reduction in Memory by deduplicating Strings on internal tasks.
• Vault is available to other Sensors by an internal Service.