Archived release notes for Instana agents

• agent-jvm-handling 1.0.32: Improves handling of ignored Java processes and JVM attachment.
• agent-ibmi-handler 1.0.3: Adds an API to access AS400 objects from connections.
• agent 1.1.764: Enhances log file discovery for custom log paths.

• Agent UI discovers and displays logs from custom paths that are configured in org.ops4j.pax.logging.cfg for improved visibility into application logs that are stored in nonstandard locations.
• IBM i sensor can access AS400 objects directly from AS400Connection instances for more efficient integration with IBM i systems.

• Fixed incorrect deletion of hsperfdata files for ignored Java processes; agent now stops monitoring without deleting attach files.
• Fixed misidentification of transitioning processes as JVMs that caused SIGQUIT signals to non-Java processes. Configure INSTANA_JVM_HANDLING_REQUIRE_ATTACH_FILES=true to attach only to JVMs with valid attach files (disabled by default).
• Updated Netty from 4.1.125.Final to 4.1.129.Final to address security vulnerability CVE-2025-67735.

• agent-open-telemetry-grpc 1.1.15: Adds support for a configurable legacy OTLP gRPC port.
• javaagent-loader 1.3.72: Prevents class loading errors during agent upgrades.
• agent-jvm-handling 1.0.31: Improves JVM attachment compatibility.
• agent-process-handling 1.0.36: Enhances process monitoring stability and secret masking.

• Configurable legacy OTLP gRPC port (55680) through INSTANA_AGENT_OTEL_GRPC_LEGACY_PORT_ENABLED environment variable or configuration file. Operators control port usage based on deployment needs.
  • Default value: true for agent versions earlier than 1.310.0
  • Default value: false for agent versions 1.310.0 and later

• As an alternative, you can also enable the legacy port in the configuration.yaml at com.instana.plugin.opentelemetry -> grpc -> legacy_port_enabled.

For more information, see Legacy OTLP gRPC port.

• Fixed process start time changes during agent restarts that triggered false service alerts; start times now remain stable during agent updates and restarts.
• Fixed NoClassDefFoundError failures when javaagent-loader JAR is deleted at runtime by pinning loader classes at startup.
• Fixed incorrect exclusion of JVMs with custom class loaders (example, WebLogic's LaunchClassLoader); the agent now excludes only unsupported SAS custom class loaders.
• Fixed exposure of secrets in Containerd container environment variables when using CRI client; agent now correctly masks secrets in all container configuration locations.

• InstanaPCP 1.3.79
• agent 1.1.763
• agent-runtime 1.0.17
• agent-runtime-api 1.0.14

• agent 1.1.762: Improved sensor configuration visibility and validation.
• agent-backend 1.0.10: Enhanced data consistency and backend error visibility.
• agent-jvm-handling 1.0.30: Improved JVM attachment reliability in containerized environments.
• agent-process-handling 1.0.35: Enhanced Windows process monitoring stability.

• The agent now validates OSGi bundle start-levels when creating sensor configurations and provides actionable warnings when sensors fail to start due to mode mismatches. These warnings help operators quickly identify and resolve configuration issues.
• Backend connectivity errors are now logged with throttled warnings for HTTP 402 (Payment Required) and HTTP 404 (Not Found) responses, providing better visibility into endpoint access restrictions and configuration issues.
• JVMs running with custom class loaders are now automatically detected and reported through monitoring events in the agent dashboard, providing clear visibility into why dynamic attachment is not supported for these processes.

• Previously, sensor payloads from multiple sources (such as legacy and sidecar sensors for IBM MQ) might overwrite each other when arriving simultaneously, causing data inconsistencies. Now, the agent performs deep merging of JSON payloads to preserve all data from both sources.
• Previously, JVM attachment might fail in Podman containers when the /tmp directory was mounted from the host root file system, causing permission errors with OpenJ9 attach files. Now, the agent automatically retries the attachment without user switching when the initial attempt fails, ensuring successful monitoring in these environments.
• Previously, on Windows systems, orphaned InstanaPCP.exe processes might remain to run after agent crashes or forced terminations, preventing new instances from starting on agent restart. Now, the agent detects and terminates leftover processes automatically, restoring Windows monitoring capabilities.
• Previously, InstanaPCP metrics collection failed after transitioning to flexible process name handling due to inconsistent instance name formats. Now, the agent uses consistent naming formats for all lookups, restoring accurate metrics collection.
• Previously, the pollRate configuration was only sent after the first reset (10 minutes after sensor start), causing gaps in UI graphs during the initial period. Now, pollRate is sent immediately on the first sense and then on subsequent resets, ensuring continuous graph visualization.
• Previously, InstanaPCP processes on Windows did not shut down properly when the Instana Agent Service stopped, leading to multiple parallel instances on restart. Now, InstanaPCP correctly monitors the agent endpoint and terminates when the agent stops, preventing duplicate processes.

agent-process-handling 1.0.34: Improved stability of CRI-API based process monitoring.

Previously, CRI-API based process handling (used with CRI-O and containerd) might hang or leave background threads active when command output was not fully consumed. This behavior might affect long-term stability. Now, background tasks and I/O resources are properly cleaned up, which can ensure stable and reliable process monitoring for CRI-O and containerd environments.

agent-util 1.0.16

• agent-api 1.2.172: Added support for collecting Podman container details without socket access and fine-grained process execution control.
• agent-socket-server 1.0.9: Added configurable HTTP message size limits on Agent endpoint.
• agent-open-telemetry-grpc 1.1.14: Added configurable gRPC message size limits.
• agent-open-telemetry-http 1.1.15: Added configurable HTTP message size limits.
• agent-process-handling 1.0.33: Enhanced Podman monitoring with socket-less container support and improved environment variable handling.
• instana-podman-sensor 1.0.9: Added support for monitoring Podman containers without socket exposure.

• OpenTelemetry base components are now always started by default, even when OpenTelemetry is not explicitly configured, providing better readiness for telemetry collection.
• Podman containers can now be monitored even when no Podman socket is available or when the socket is reported as missing, enabling monitoring in more restrictive environments.
• Message size limits can now be configured for the Agent endpoint (:42699) by using INSTANA_AGENT_HTTP_MAX_MESSAGE_SIZE (minimum: 5 MB, maximum: 49.5 MB), allowing better control over resource usage.
• gRPC message size limits can now be configured by using INSTANA_AGENT_OTEL_GRPC_MAX_MESSAGE_SIZE or through config key grpc.max_message_size (minimum: 5 MB, maximum: 49.5 MB), providing flexibility for large telemetry payloads.
• HTTP message size limits can now be configured by using INSTANA_AGENT_OTEL_HTTP_MAX_MESSAGE_SIZE or through config key http.max_message_size (minimum: 5 MB, maximum: 49.5 MB), enabling handling of larger HTTP-based telemetry data.
• Fine-grained control is now available for running processes within the context of other processes (for example, inside containers). You can now control how environment variables are inherited and how user context is applied.
• The Agent Support Task now includes Podman socket detection details in its downloadable results, improving troubleshooting capabilities.
• The Agent now validates potential gateway endpoints inside the Podman process network namespace before applying them, ensuring more reliable network configuration.

• Previously, evaluation of performance counters and temporary directories was incorrectly bound to the InstanaPCP state (introduced in 1.0.27), causing these checks to fail when InstanaPCP was not active. Now, temp directories are always evaluated, and performance counters are queried on Windows regardless of InstanaPCP state, ensuring consistent system monitoring.
• Previously, additional information requests for user-context containers in rootless Podman monitoring might fail due to shell output contamination. Now, the Agent uses a user session without a login shell to ensure clean stdout output, enabling reliable data collection from rootless Podman containers.
• Previously, environment variables during java -version checks and JVM attachment might interfere with proper operation. Now, a cleaned-up environment is used for these operations, ensuring more reliable JVM detection and attachment.

• instana-agent-open-telemetry-base 2.2.5
• instana-agent-otel-sensor-sdk 1.1.18
• instana-agent-open-telemetry-service 1.1.13
• agent-util 1.0.15
• agent-jvm-handling 1.0.29
• agent 1.1.761
• agent-backend 1.0.28
• agent-backend-api 1.0.13
• agent-backend-util 1.0.13
• agent-configuration-integration-vault 1.0.11
• agent-grpc 1.0.13
• agent-grpc-channel-cache 1.0.13
• agent-http 1.0.13
• agent-jaeger-tracer 1.0.13
• agent-memory 1.0.13
• agent-netty-allocator 1.0.13
• agent-netty-allocator-api 1.0.13
• agent-process-handling-api 1.0.13
• agent-self-profiling 1.0.13
• agent-sensor 1.0.13
• agent-socket-server-api 1.0.13
• agent-task-orchestrator 1.0.13
• agent-zipkin-tracer 1.0.13

• agent 1.1.760: Fixed sensor heartbeat conversion timing.
• agent-process-handling 1.0.32: Fixed container detection and namespace handling issues.

• Previously, sensors with pollRate 1 had a 10-second gap before heartbeats were converted to NO_CHANGE results, even though they were expected to provide data every second. This delay caused special heartbeat workarounds to malfunction when sensors lagged. Now, the conversion threshold for pollRate 1 sensors is reduced to 3 seconds, which ensures more timely data processing and correct handling of lagging sensors.
• Previously, container ID detection could produce false positives in mixed container runtime environments, particularly when CRI-O containers were incorrectly identified by Containerd detection logic. Now, container detection uses explicit validation checks and runtime-specific patterns (including improved Podman libpod scope detection), ensuring accurate container identification across Docker, Containerd, Podman, and CRI-O environments.
• Previously, the agent could not properly interact with processes inside Podman containers, especially rootless ones, due to user namespace differences. This issues caused permission errors and failed operations when attaching to JVMs inside these containers. Now, the agent intelligently detects namespace relationships and uses appropriate mechanisms to join target namespaces, ensuring reliable JVM attachment and monitoring in Podman environments.

• agent-internal-api 1.0.18
• agent-jvm-handling 1.0.28
• agent-runtime 1.0.16
• agent-runtime-api 1.0.13

• agent-process-handling 1.0.31: Enhanced Podman POD container detection.

Previously, container ID detection for Podman POD containers was incomplete. Now, detection is enhanced to properly identify POD containers, improving container visibility and monitoring accuracy.

sensor-api 1.2.170

• agent 1.1.759: The bundle is updated to fix queue parameter usage in SensorTicker.sendResultChunk.
• agent-jvm-handling 1.0.27: The bundle is updated to clean up Java environment variables on external attach to prevent out of memory (OOM) errors.
• agent-process-handling 1.0.30: The following changes are added to this bundle:
  • Fix container ID detection to exclude conmon processes in container environments.
  • Switch process metric collection to a faster and more resource-efficient method, now enabled by default.
• agent-runtime 1.0.15: The bundle is updated to optimize by checking for /proc folder only once at startup.
• agent-task-orchestrator 1.0.7: The bundle is updated to optimize DefaultThreadWatcher with Netty HashedWheelTimer to reduce allocations and GC overhead.
• agent-open-telemetry-http 1.1.14: The bundle is updated to remove unnecessary information log for ignored pid lookup.

• The agent-process-handling bundle now enables a faster and more resource-efficient process metric collection method on Windows systems using InstanaPCP.

  Customers benefit from reduced resource usage and improved responsiveness without needing to configure environment variables.

• Previously, queue parameter usage in SensorTicker.sendResultChunk was incorrect. This could cause inaccurate handling of queued data. This issue is now fixed, ensuring correct and reliable queue management.
• Previously, Java environment variables were not cleaned up on external attach, which could lead to memory leaks and potential OOM errors. This issue is now fixed by cleaning up these variables properly, improving stability during JVM attachment.
• Previously, container ID detection incorrectly included conmon processes in container environments. This could result in misleading container attribution. This issue is now fixed by excluding conmon processes, ensuring accurate container detection.
• Previously, the agent checked for the /proc folder multiple times during startup, adding unnecessary overhead. This issue is now fixed by checking only once, reducing startup time, and improving efficiency.
• Previously, DefaultThreadWatcher had higher memory allocations and GC overhead. This issue is now fixed by using Netty HashedWheelTimer, reducing memory footprint and improving performance under load.
• Previously, unnecessary info logs were generated for ignored pid lookup in the OpenTelemetry HTTP component. This issue is now fixed by removing these logs, resulting in cleaner logs and less noise.

• agent 1.1.758: Added a new option for handling configuration file changes.
• agent-process-handling 1.0.29: The following changes are added to this bundle:
  • Reduced memory usage in the process abstraction by optimizing checks for /proc presence.
  • Improved process startup time detection on AIX by using SIGAR.
• agent-runtime 1.0.14: Added detection support for the presence of /proc in Linux paths.
• agent-runtime-api 1.0.12: Exposes whether /proc is accessible through its API.

• The agent bundle introduces a new configuration option to control how configuration file changes are detected. You can enable with the environment variable INSTANA_WATCH_CONFIG_CHANGES_WITH_HASH_POLLER (default: false; set to true to use hash-based polling instead of inotify).
• The agent-runtime and agent-runtime-api bundles improve Linux process detection:
  • The runtime now detects if /proc is present in Linux paths.
  • The API now exposes this information through the isProcPresent method.

• Previously, the process abstraction consumed more memory when it was checking for /proc presence. This issue is now fixed by optimizing these checks.
• Previously, process startup time detection on AIX was less accurate. This issue is now fixed by using SIGAR for the detection.

• agent-init 1.0.8: Enabled direct memory usage by default on AIX.
• agent 1.1.757: Improved ps probing, so that parent process information is always available.
• agent-jvm-handling 1.0.26: Updated support for JVM attachment inside Podman containers by using switchUser.
• agent-netty-allocator 1.0.2: Improved logging when direct memory is disabled.
• agent-process-handling 1.0.28: Updated support for switchUser in Podman processes that use nsenter.
• netty 4.1.125: Updated to resolve a security issue in the HTTP codec.

The agent-init bundle enables direct memory usage on AIX systems by default. This can be turned off with the environment variable INSTANA_AIX_NETTY_SET_UNSAFE (default: false; set to true to disable direct memory).

• Previously, the AgentSupportTask that executes ps might omit the parent process ID (PPID) in some cases. This issue is now fixed by probing the available ps options on startup and selecting one that reliably includes the PPID and, when possible, the process tree.
• Previously, the agent-jvm-handling bundle might not attach to JVMs running inside Podman containers. This issue is now fixed by using switchUser during the attached operation.
• Previously, the agent-netty-allocator bundle lacked visibility when direct memory was disabled. This issue is now fixed by adding an information-level log to indicate the state.
• Previously, the agent-process-handling bundle did not correctly apply switchUser in Podman processes that rely on nsenter. This issue is now fixed by implementing switchUser with the --setuid and --setgid so user changes are properly applied during execution.
• A vulnerability existed in the netty bundle’s HTTP codec (CVE-2025-58056). This issue is now fixed by updating to a patched version.

• agent-backend 1.0.8: The following changes are added to this bundle:
  • Added support for configuring the backend read timeout.
  • Improved connection handling by delaying idle state checks until after TLS is established.

The agent-backend bundle now supports configurable backend read timeouts with the environment variable INSTANA_BACKEND_READ_TIMEOUT_SECONDS (default: 10; values below 10 are ignored).

Previously, connections might reconnect too early during TLS handshakes. This is now prevented by initializing the idle state handler only after the SSL connection is fully established.

• sensor-api 1.2.169: The following improvements were added to process output handling:
  • Introduced a builder pattern for creating OsProcessOutput with configurable options.
  • Added configurable queue capacity and batch size in StreamingOsProcessOutput.
  • Added a reliable onClose callback for StreamingOsProcessOutput.
• agent 1.1.756: Improved logging for network binding operations.
• agent-cri-client 1.0.6: Now captures both imageId and imageRef from container status.
• agent-jvm-handling 1.0.25: The following internal refactorings were applied:
  • Updated to use MavenArtifact instead of AbstractMavenArtifact.
  • Now depends on the AbstractMavenArtifact API from sensor-api.
  • Removed the obsolete ByteBuddyToolsJar.java.
• agent-process-handling 1.0.27: The following enhancements were added:
  • Added information-level logging for network interface binding.
  • Improved container ID detection for CRI-containerd format.
  • Better IP address resolution for Rootless Podman containers.
  • Improved process monitoring decision tracking with the AgentSupportTask.
  • Reworked Windows service watcher with improved lifecycle management.
• agent-util 1.0.14: The following changes were added:
  • Deprecated AbstractMavenArtifact in favor of the API version.
  • Added an overload of getNestedValue returning null if path not found.
  • Introduced a more flexible optional chain builder in ValueFinder.
• agent-open-telemetry-service 1.1.12: Optimized the handling of attributes through automatic sorting.
• agent-open-telemetry-grpc 1.1.13: Updated to allow disabling PID lookup with the configuration or environment variable.
• agent-open-telemetry-http 1.1.13: Updated to allow disabling PID lookup with the configuration or environment variable.

• The sensor-api bundle provides several enhancements to process output handling:
  • Introduces a builder pattern for OsProcessOutput with configurable options.
  • Adds configurable queue capacity and batch size in StreamingOsProcessOutput.
  • Provides a reliable onClose callback for StreamingOsProcessOutput.
• The agent bundle now logs more details about network binding operations, improving troubleshooting of binding issues.
• The agent-cri-client bundle now collects both imageId and imageRef when it inspects container status, and this provides complete image metadata.
• The agent-jvm-handling bundle is refactored with the following changes:
  • Migrated from AbstractMavenArtifact to the new MavenArtifact API.
  • Now uses AbstractMavenArtifact from sensor-api instead of its own copy.
  • Removed the obsolete ByteBuddyToolsJar.java file.
• The agent-process-handling bundle improves observability and container support:
  • Logs information during network interface binding.
  • Enhances container ID detection for CRI-containerd format.
  • Improves IP resolution in Rootless Podman environments.
  • Tracks process monitoring decisions more transparently with the AgentSupportTask.
  • Provides more reliable lifecycle handling for Windows services.
• The agent-util bundle provides several enhancements:
  • A new overload of getNestedValue that returns null if a path is not found.
  • A conditional optional chain builder added to ValueFinder for more advanced value resolution logic.
  • The AbstractMavenArtifact class is now deprecated in favor of the API version.
• The agent-open-telemetry-service bundle now sorts attributes automatically by using a TreeMap, which improves performance and consistency of attribute handling.
• The agent-open-telemetry-grpc and agent-open-telemetry-http bundles now make PID lookup configurable. PID lookup is enabled by default, but it can be disabled with the environment variable INSTANA_AGENT_OTEL_GRPC_PID_LOOKUP (default: true; set to false to disable) or INSTANA_AGENT_OTEL_HTTP_PID_LOOKUP (default: true; set to false to disable). As an alternative, PID lookup can also be disabled with the configuration.yaml at:
  • com.instana.plugin.opentelemetry -> grpc -> pid_lookup .
  • com.instana.plugin.opentelemetry -> http -> pid_lookup .

agent-process-handling 1.0.26: The bundle is updated to add the missing socket to CRI-API-based process execution within ContainerD containers.

Previously, CRI-API-based process execution inside ContainerD containers failed because a required socket was missing. This issue is now fixed by adding the missing socket.

• sensor-api 1.2.168: The bundle is updated to handle null for sense result as heartbeat.
• agent 1.1.755: The following changes are added to this bundle:
  • Internal logic is removed from DefaultNetworkInterfaceSupport to use the BindAddressProvider instead of providing the list of bindable interfaces internally.
  • Annotation based logging is updated to use bundle aware loggers instead of agent-util.
• agent-api 1.0.6: The bundle is updated to add BindAddressProvider interface that returns a list of bindable interfaces.
• agent-cgroup 1.0.7: The bundle is updated to use bundle aware loggers instead of agent-util.
• agent-cri-client 1.0.5: The bundle is updated to check the default containerD socket /run/containerd/containerd.sock on startup.
• agent-grpc-channel-cache 1.0.3: The bundle is updated to use bundle aware loggers instead of agent-util.
• agent-internal-api 1.0.17: The bundle is updated to extend ProcessInterestHandler with a new method to register an interest for a given interface bound to a process.
• agent-jvm-handling 1.0.24: The following changes are added to this bundle:
  • Identify jstart.exe as a potential JVM.
  • Annotation based logging is updated to use bundle aware loggers instead of agent-util.
• agent-process-handling 1.0.25: The following changes are added to this bundle:
  • Foreign PID timeout is extended to 2 seconds.
  • A n flag is added for foreign PID lookup to mitigate resolving DNS entries.
  • The criClient is used for containerD when the agent runs in a POD, or if enabled through an environment variable.
  • Podman host interface detection is improved.
  • Multiple new BindAddressProvider implementations are added.
  • Annotation based logging is updated to use bundle aware loggers instead of agent-util.
• agent-runtime 1.0.13: The bundle is updated to use bundle aware loggers instead of agent-util.
• agent-support-karaf 1.0.1: The bundle is updated to use bundle aware loggers instead of agent-util.
• agent-task-orchestrator 1.0.6: The bundle is updated to use bundle aware loggers instead of agent-util.
• agent-util 1.0.13: The bundle is updated to use bundle aware loggers instead of agent-util.
• agent-open-telemetry-base 2.2.5: The bundle is updated to use cluster.uid as entityId if it is present in the attributes list.
• agent-open-telemetry-grpc 1.1.12: The following changes are added to this bundle:
  • Allow disabling PID lookup through an environment variable.
  • Annotation based logging is updated to use bundle aware loggers instead of agent-util.
• agent-open-telemetry-http 1.1.12: The following changes are added to this bundle:
  • Allow disabling PID lookup through an environment variable.
  • Annotation based logging is updated to use bundle aware loggers instead of agent-util.

• The sensor-api bundle now supports handling null for sense results as heartbeats.
• The agent-api bundle introduces the BindAddressProvider interface to return a list of bindable interfaces.
• The agent-cri-client now checks the default containerD socket /run/containerd/containerd.sock during startup.
• The agent-internal-api extends the ProcessInterestHandler with registration support for interfaces bound to a process.
• The agent-process-handling bundle extends the foreign PID timeout to 2 seconds and adds the n flag to mitigate DNS resolution issues.
• The agent-process-handling bundle now supports containerD through the CRI client. You can enable or disable this behavior with the environment variable INSTANA_USE_CONTAINERD_CRI_CLIENT (default: true when running in a POD).
• The agent-process-handling bundle introduces multiple new BindAddressProvider implementations:
  • AgentPublicIpBindAddressProvider : exposes the agent’s public IP as a bindable interface.
  • ContainerBridgeBindAddressProvider : exposes container bridge networks as bindable interfaces.
  • ProcessInterestBindAddressProvider : exposes process-specific network interests as bindable interfaces.
• The agent-open-telemetry-grpc bundle now allows disabling PID lookup with the environment variable INSTANA_AGENT_OTEL_GRPC_PID_LOOKUP (default is true, set to false to disable).
• The agent-open-telemetry-http bundle now allows disabling PID lookup with the environment variable INSTANA_AGENT_OTEL_HTTP_PID_LOOKUP (default is true, set to false to disable).

• Previously, annotation based logging used the generic agent-util logger. This issue is now fixed by updating all affected bundles (agent, agent-cgroup, agent-grpc-channel-cache, agent-jvm-handling, agent-process-handling, agent-runtime, agent-support-karaf, agent-task-orchestrator, agent-util, agent-open-telemetry-grpc, agent-open-telemetry-http) to use bundle aware loggers instead.
• Previously, foreign PID lookup would fail due to too short timeouts or DNS resolution. This issue is now fixed by extending the timeout and adding the n flag to mitigate DNS resolution.
• Previously, podman containers would fail to resolve host interfaces. This issue is now fixed by using host.containers.internal as a reliable host interface target.

• sensor-api 1.2.167: The bundle is updated to allow global access to RSS count in the cgroup data.
• agent 1.1.754: The bundle is updated to improve the handling of Metadata API responses.
• agent-cgroup 1.0.6: The bundle is updated to correctly handle memory cache and RSS calculation for cgroups.
• agent-jvm-handling 1.0.23: The bundle is updated to support Java 25 for tracing.
• agent-process-handling 1.0.23: The following changes are added to this bundle:
  • The bundle is updated to support custom RKE2 paths.
  • A new service is added to traverse parent process lookups.
• agent-process-handling 1.0.24: The bundle is updated to add loop detection to parent process lookups.
• agent-socket-server 1.0.8: The following changes are added to this bundle:
  • Callback to parent channels is added.
  • Thread naming is improved for better diagnostics.
• agent-socket-server-api 1.0.5: The bundle is updated to add a callback to parent channels.
• agent-open-telemetry-service 1.1.11: The bundle is updated to reduce Object to String allocation only to debug logging case.
• agent-open-telemetry-http 1.1.11: The following changes are added to this bundle:
  • The connection tracking logic is added to the parent handler.
  • The PID lookup is added to the parent handler before the channel is initialized.
  • The number of maximum channels can be limited.

• The cgroup parser now exposes RSS data with total_rss for cgroupv1 and anon for cgroupv2.
• The agent-jvm-handling bundle now supports Java 25 tracing with upgraded javaagent-loader (1.3.71), instrumentation-boot (1.1.32), and instrumentation-shared (1.0.1467).
• A service is added to traverse parent processes. This service is used on various container implementations to identify the type or containerId.
• The OpenTelemetry HTTP component now allows to configure a maximum number of concurrent active channels with the environment variable INSTANA_AGENT_OTEL_HTTP_MAX_CHANNELS (default value is 1000).

• Previously, the parser for the Metadata API did not check for error strings. This issue is now fixed by checking for error responses and limiting allowed strings for the UniqueId of the agent.
• Previously, the parent process lookup might lead to an OutOfMemory error when the processes did not end with 0. This issue is now fixed by tracking already visited process IDs and stopping when a loop is detected.
• Previously, the OpenTelemetry HTTP component caused an OutOfMemory error when too many incoming requests reached the agent. This issue is now fixed by limiting the number of concurrently active channels. In addition, the expensive PID lookup is moved into the parent handler.

agent-process-handling 1.0.21: sshd process monitoring is fixed after v1.2.32 release.

Previously, the sshd process was only added to the internal list when it ended with sshd, which is not correct for newer RHEL environments. This issue is now fixed by checking how often sshd occurs in the executable and allowing when more than 1 occurrence is counted.

• agent 1.1.753: Monitoring issue pax_url_mvn_leak is added to this bundle.
• agent-netty-allocator 1.0.1: The following changes are added to this bundle:
  • Per-channel backoff-guarded allocator with shared counters and backoff configuration are added.
  • A DefaultFlowControlManager is added to track per-channel "permits" and pause autoRead when buffer-in-flight count exceeds max concurrency.
• agent-netty-allocator-api 1.0.1: The service is extended with per-channel allocators.
• agent-process-handling 1.0.21: sshd process monitoring is relaxed.
• agent-runtime 1.0.12: The bundle is extended to read double configuration values.
• agent-runtime-api 1.0.11: The bundle is extended to read double configuration values.
• agent-socket-server 1.0.7: The bundle is extended to use the new flow control manager to limit concurrent reads.

• A service is added to control maximum number of concurrent reads. You can control the concurrency by using the INSTANA_INGRESS_CONCURRENCY environment variable (default value is 4).
• You can fine-tune the Netty ingress with the following environment variables:
  • INSTANA_NETTY_INBOUND_FACTOR (default value is 0.6): A value between 0 and 1, controls the percentage of direct memory that can be used for inbound.
  • INSTANA_NETTY_OUTBOUND_FACTOR (default value is 0.9): A value between 0 and 1, controls the percentage of direct memory that can be used for outbound, the outbound factor is always more than the inbound factor.
  • INSTANA_NETTY_INBOUND_SOFT_FACTOR (default value is 0.8): A value between 0 and 1, controls the percentage of direct memory that is used for a soft-backoff.
  • INSTANA_NETTY_SOFT_TIMEOUT_SECONDS (default value is 2): A value between 0 and unlimited, controls the seconds used for the soft-backoff after which memory is always granted.
  • INSTANA_NETTY_DIRECT_MEMORY_TIMEOUT_SECONDS (default value is 30): A value between 0 and unlimited, controls the seconds used for the hard-backoff after which an exception is thrown and the current message is dropped.
• The service to read configuration values can read values of type double.

• Previously, a leak in the pax-url component caused OutOfMemory errors. Now, if this issue is detected, Instana displays a monitoring issue pax_url_mvn_leak. You can fix this issue by reinstalling the agent.
• Previously, incoming ingress might starve the egress to the backend. This issue is now fixed by limiting the concurrent streams that are read concurrently to 4. In addition, the ingress also handles back-pressure by slowing down incoming data when the egress is not able to offload fast enough.
• Previously, the sshd process was only allowed when it is at the default location /usr/sbin/sshd. This issue is now fixed by relaxing the lookup to check if the process ends with sshd.

• agent-process-handling 1.0.20: An end reason is added for in-container process ID lookup. Also, a retry is added when /status file content is empty.
• agent-runtime 1.0.11: The service is now extended to provide Exponential Backoff handlers with an end reason.
• agent-runtime-api 1.0.10: The service is now extended to provide Exponential Backoff handlers with an end reason.

The service to handle exponential backoff now keeps track of the end reason when it is marked as done.

Previously, a race condition occurred when reading the /status file, which resulted in the failure to read the in-container PID. This issue is now fixed and the agent retries reading the /status file when the content is empty. The success and error cases are added to the Collect Support Information.

• agent-jvm-handling 1.0.22: A monitor is added to all known temporary directories on Windows.
• agent-process-handling 1.0.19: A backoff strategy for in-container PIDs is added, and related information is reported in the Collect Support Information on the agent dashboard.
• agent-runtime 1.0.10: A service is implemented to provide Exponential Backoff handlers.
• agent-runtime-api 1.0.9: A service is implemented to provide Exponential Backoff handlers.

A service is added that allows for exponential backoff.

• Previously, when a Java process stopped without a clean shutdown, files that are related to Java sensors accumulated on the user's temporary directories. This issue is now fixed by checking all known temporary directories on Windows for Java sensor files and deleting them if the Java process is stopped.
• Previously, a NullPointerException error occurred when comparing the PID with the reported PID in announce messages that are sent by tracers. This issue is now fixed. The agent always checks for null values before comparing. In addition, a backoff strategy is added to lookup the in container PID by using /status or /sched files. The number of tries and the current state of the lookup for in-container PIDs are added to the Collect Support Information.

• sensor-api 1.2.166: The following changes are included in this release:
  • A service is added to lookup the default temp directory of the agent.
  • A service is added to compress data to be forwarded to the backend.
  • Process information is extended with reported PID and process type.
  • Direct usage of Sigar is deprecated, and usage is allowed only through helpers.
• agent 1.1.752: A fallback is added to configuration changes with manual checks if inotify handles are exhausted.
• agent-cgroup 1.0.5: The lookup speed is enhanced by checking the known type of a process.
• agent-jvm-handling 1.0.21: The following changes are included in this release:
  • The lookup speed is enhanced by checking the known type of a process.
  • javaagent‑loader is updated to version 1.3.70. Log level is now reduced to INFO when the permission update for /tmp/.instana fails. Also, the folder lookup is enhanced on J9-based attachments when /tmp/.com_ibm_tools_attach is reachable instead of /proc/<pid>/tmp/.com_ibm_tools_attach.
• agent-process-handling 1.0.18: The following changes are included in this release:
  • The lookup speed is enhanced by checking the known type of a process.
  • The reported PID is now exposed for container and host processes as seen from the process.
  • PID is now validated as part of announce messages from tracers.
  • Files can be now copied into folders within rootless Podman containers.
  • The direct access to Sigar is now removed. A wait is added for Sigar to block access before the shutdown.
• agent-process-handling-api 1.0.5: The internal service for Process Type is deprecated because it was moved to the sensor API.
• agent-runtime 1.0.9: A service is implemented for files and file access for easier testing.
• agent-runtime-api 1.0.8: A service is implemented for files and file access for easier testing.

Processes now report their PID as seen from the process. This information can differ between processes that run on on host and in container because the PID namespace is different.

• Previously, if inotify handles were exhausted, configuration files were not watched. This issue is now fixed by reading the metadata of the configuration files at regular intervals and updating the configuration if the metadata has changed.
• Previously, multiple processes were checked dueing the announcement of tracers. This issue is now fixed by limiting the process list to include only the processes that have the same reported PID.
• Previously, the javaagent-loader logged changes to the /tmp/.instana always on WARN level. This issue is now fixed by only logging on WARN if the rights of the folder do not match the expected level.
• Previously, the javaagent-loader failed to attach to J9 JVMs when the /proc/<pid>/tmp/.com_ibm_tools_attach was not reachable. This issue is now fixed by checking if the folder /tmp/.com_ibm_tools_attach is reachable.
• Previously, when you copied files into a folder within a rootless Podman container, a file with a random name was created. This issue is now fixed by copying the file into an intermediate folder on /tmp on the host first and keeping the original name.

• agent 1.1.751: Implemented service to view configuration file changes.
• agent-internal-api 1.0.16: Added service to view configuration file changes.
• agent-process-handling 1.0.16: The following changes are included in this release:
  • Cache container metadata by default
  • InstanaPCP is updated to 1.3.74: Removes setting INSTANA_LOG_LEVEL environment variable
  • Added ability to ignore non-container cgroups
  • Used a known socket for ContainerD information lookup
  • Extended selective monitoring to use Kubernetes namespaces

• 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.

• 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.

• agent 1.1.750: Detects non-UTF-8 characters in the configuration.yaml file.
• agent-cgroup 1.0.4: Checks for running processes on cgroup data lookup.
• agent-jvm-handling 1.0.20: Ignores db2fmp process.
• agent-process-handling 1.0.15: Prepares Kubernetes labels cache.
• agent-util 1.0.12: Adds helper to detect non UTF-8 characters.
• agent-open-telemetry-grpc 1.1.11: ExecutionPipeline for OTel gRPC traces.
• agent-open-telemetry-http 1.1.10: Optimizes http pipeline.

• 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

• 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.

• agent 1.1.749: OpenTelemetry HTTP and gRPC components are enabled through the environment.
• agent-backend 1.0.7: Configurable deflate level for backend communication is added.
• agent-jvm-handling 1.0.19: Timing of log-level synchronization is adjusted.
• agent-runtime 1.0.8: The environment lookup methods for Integer and Boolean is now exposed.
• agent-runtime-api 1.0.7: Matching API methods for environment lookups is added.
• agent-socket-server 1.0.6: ExecutionPipeline is adopted for connections and HTTP.
• agent-task-orchestrator 1.0.5: ThreadWatcher is introduced for stuck-thread monitoring.
• agent-task-orchestrator-api 1.0.2: ThreadWatcher and ExecutionPipeline task wrappers are added.
• agent-util 1.0.11: Nested-config lookup and exception-aware callable and runnable types are added.
• agent-open-telemetry-base 2.2.4: Support for span-links is added.
• agent-open-telemetry-service 1.1.8: Support for span-links is added.
• agent-open-telemetry-grpc 1.1.10: ExecutionPipeline for OTel gRPC and configurable port are added.
• agent-open-telemetry-http 1.1.9: ExecutionPipeline for OTel HTTP and configurable port are added.

• 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

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.

• agent-netty-allocator-api 1.0.0: This bundle adds a service to provide a global ByteBuffer allocator that enables a timeout-based lookup.
• agent-netty-allocator 1.0.0: This bundle implements a service to provide a global ByteBuffer allocator that provides a timeout-based lookup.
• agent-backend 1.0.6: The bundle now uses the global timeout-based allocator to ensure that data is reported to the backend.
• agent-jvm-handling 1.0.18: The following changes are added to this bundle:
  • javaagent‑loader is updated to version 1.3.69. The in-memory ClassLoader correctly frees up the internal state when it i restarted. The javaagent-loader preloads ManagementFactory to prevent startup delays.
• agent-socket-server 1.0.5: The following changes are added to this bundle:
  • The bundle is updated to use the global allocator for ByteBuffers.
  • The bundle now restricts the internal usage of a single ChannelInitializer.

• 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.

• agent-jvm-handling 1.0.17: The following changes are added to this bundle:
  • javaagent‑loader is updated updated to version 1.3.68. The in‑memory ClassLoader is now disabled when maximum heap is lesser than the threshold value that you configured and falls back to file‑based attachment.
  • The agent now suppresses kill -3 call on Windows systems.

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.

• 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.

• agent 1.1.748: The following changes are added to this bundle:
  • The sensitive data in the ps task is now hidden when support information is collected.
  • The leading slash from the Support Information zip archive is now removed.
• agent-jvm-handling 1.0.16: The following changes are added to this bundle:
  • Support for Java 24 is added for tracing.
  • The detection of J9 JVMs with custom Java executables or attach directories is now improved.
  • The bundle is updated to suppress Byte Buddy–based attachment on Unix systems if /tmp is mounted with noexec.
• agent-process-handling 1.0.14: The bundle now checks containers for null metadata and returns an empty map instead of parsing invalid data.
• agent-runtime-api 1.0.6: The following changes are added to this bundle:
  • The bundle is updated to expose a service to load any class at runtime.
  • The bundle is updated to expose a service to inspect mount options on Unix-based systems.
• agent-runtime 1.0.7: The following changes are added to this bundle:
  • The bundle is updated to implement the “load any class” service.
  • The bundle is updated to implement the mount-options inspection service for Unix.
• agent-socket-server-api 1.0.4: The bundle is updated to expose a service to start and stop Netty-based socket servers.
• agent-socket-server 1.0.4: The bundle is updated to implement the Netty socket-server start and stop service.
• agent-task-orchestrator 1.0.4: The Scheduler is now exposed as a prototype so that each consumer gets its own instance, while threads remain shared globally.
• sensor-api 1.2.163: The following changes are added to this bundle:
  • A Streaming Process Output helper is added.
  • A JVM job-name lookup support is added for IBM i.
• agent-open-telemetry-grpc 1.1.7: The socket-server API service is now used to start and stop the OTel gRPC socket server.
• agent-open-telemetry-http 1.1.6: The socket-server API service is now used to start and stop the OTel HTTP socket server.
• agent-ibmi-handler 1.0.2: The bundle is updated to fetch the full job name on IBM i when only a PID was shown previously.

• 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.

• 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.

• agent-cri-client 1.0.4: This bundle is updated to capture and log the exceptions that occur during the activation of the CriClient.
• agent-grpc-channel-cache 1.0.2: This bundle is updated to capture and log the exceptions that occur during the creation of channel caches.

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.

• agent-support-karaf 1.0.0: This bundle holds all Karaf-related support collection data. Additionally, this bundle adds the following features:
  • A new support task is added to collect bundle tree dependencies.
  • A new support task is added to collect bundle header information.
• agent-cgroup 1.0.3: The following changes are added to this bundle:
  • The bundle now waits for the completion of process collection before performing the updates to prevent the CRI-O sensors from stopping.
  • Containers and processes are now queried without relying on selective monitoring.
  • Memory and CPU data spikes on startup are now reduced by setting negative values to 0 during the startup of cgroup data.
  • cgroup detection is started only if the host runs on Linux and the /proc folder is present.
  • Memory usage on CGroupV2 is now calculated as file + anon.
• agent-cri-client 1.0.3: The following changes are added to this bundle:
  • A version check is now performed during client initialization to preload the necessary classes.
  • The bundle now Includes io.perfmark to avoid additional external imports.
• agent-internal-api 1.0.15: An API is added to query TempDir per process that is required for attachments on Windows.
• agent-jvm-handling 1.0.14: The following changes are added to this bundle:
  • Attachment on Windows now uses the TEMP directory of each process instead of a global directory when the user is not an administrator or a service account.
  • You can now control the timeout on JVM connections by using the environment variable INSTANA_SOCKET_CONNECTION_TIMEOUT . The default value is 45, and the unit is seconds.
• agent-open-telemetry-grpc 1.1.6: A retry mechanism is added for port binding failures.
• agent-open-telemetry-http 1.1.5: A retry mechanism is added for port binding failures.
• agent-process-handling 1.0.13: The following changes are added to this bundle:
  • InstanaPCP is updated to 1.3.73: Process metrics can now be collected without changing the process name to processName_pid format.
  • Null case for environment variable maps are now handled properly when querying container specific values.
  • The ability to wait for the first process collection before updates is added.
  • The ability to query processes without selective monitoring is added.
• agent-process-handling-api 1.0.4: The following changes are added to this bundle:
  • The interface to await the first process collection is added.
  • The interface to query processes without selective monitoring is added.
• agent-runtime 1.0.6: ReentrantLock is ow used instead of synchronization for map, list, and string interning.
• agent-socket-server 1.0.3: A retry mechanism is added for port binding failures.

• 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).

• 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.

• agent 1.1.746: The Log4j2 pattern is now updated on startup.
• agent cgroup 1.0.2: The cgroup data lookup issue is now fixed by using any available process in a container.
• agent process handling 1.0.12: The following updates are added to this bundle:
  • PID 1 is now correctly identified as a process on the host instead of a container process.
  • A null check is added to resolve the NullPointerException error in ContainerD process when the namespace is null.
  • Additional debug information is provided for process objects when support information is collected.
• agent util 1.0.10: A trace logger is added for annotated methods.

• 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.

• 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.

• agent grpc 1.0.17: Additional io.grpc components (io.grpc.util and io.grpc.inprocess) are now exported to improve the agent’s communication capabilities. Also, startlevel is lowered to 70.
• agent optional API 1.0.8: This bundle is updated to run the configuration steps in a defined order.
• agent 1.1.745: This bundle is updated to read configurations from the agent through environment (by using agent_env) and file (by using agent_file) and combine sensor data from multiple sensors that share the same name and entityId.
• agent cri client 1.0.2: This bundle is updated for compatibility with the agent grpc 1.0.17 bundle update.
• agent JVM handling 1.0.13: This bundle is updated to evaluate environment variables (IBM_JAVA_OPTIONS, JAVA_TOOL_OPTIONS, and _JAVA_OPTIONS) when checking J9 JVMs for the com.ibm.tools.attach.directory startup parameter and update attach-tools to version 1.17.2 to correctly handle handle explicit directory definitions.
• agent process handling 1.0.10: The following changes are added to this bundle:
  • Selective monitoring is added for container environment variables (supported for Podman, Docker, and CRI-O), which enables the agent to decide if a process should be monitored or ignored.
  • The jail toot process handling is restricted to Linux systems.
  • Memory footprint for processes is reduced by interning strings, arguments, and environment variables from processes that share the same values.
  • The file permission issue that occurred when copying files into a rootless Podman container with strict umask settings is fixed.
  • The native CriClient is enabled, which is controlled by the environment variable INSTANA_USE_CRI_CLIENT.
• agent process handling 1.0.11: This bundle is updated to always use a mutable environment map when executing process calls.
• agent runtime API 1.0.5: Interfaces to intern lists and maps are added.
• agent runtime 1.0.5: Interning of lists and maps is implemented.
• agent util 1.0.9: Two helpers are added to handle and list the file permissions and to iterate through a collection of Optional supplier objects.

• 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.

• 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.

• agent 1.1.744: javaagent-loader is updated to version 1.3.66. Also, instrumentation‑shared is updated to version 1.0.145 to add the ability to ignore specific packages during instrumentation.
• agent internal API 1.0.14: A new method to query all known process IDs (PID) for process‑based sensors is added.
• agent‑cgroup 1.0.1: The bundle is updated to perform cgroup version checks only on Linux systems.
• agent‑jvm‑handling 1.0.12: The monitoring issue jvm_tmp_not_available is updated to agent_tmp_directory_missing when /tmp is unavailable. Also, the bundle is updated to support constant monitoring for /tmp availability for jail root-based JVMs.
• agent‑process‑handling 1.0.9: The bundle is updated to add the following changes:
  • log level for exceptions during symbolic link checks is lowered to DEBUG.
  • event‑based handling mechanism replaces the timer‑based approach to update the iptables of Garden‑based containers.
  • The parsing issue that occurred during the normalizing of broken paths on Windows is fixed.

• 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.

• 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.

• agent 1.1.743: javaagent-loader is updated to 1.3.65. Also, instrumentation-shared is updated to 1.0.144 to fix the memory leak in the instrumentation logs.
• agent backend 1.0.5: Handling for capabilities endpoint is added.
• agent JVM handling 1.0.11: Support for jail root for JVMs is added. Also, the bundle now supports monitoring jvm_tmp_not_available when /tmp is not available for a JVM.
• agent process handling 1.0.8: Support for jail root for processes is added. Also, the bundle now supports retrieving environment variables for WebSphere on z/OS.
• agent process handling API 1.0.3: The bundle is updated to add support to jail root processes on an internal API level.
• agent util 1.0.8: The bundle is updated to add a new helper for FilePermissions.
• agent grpc 1.0.16: The gRPC server is removed from the bundle.
• agent open telemetry service 1.1.5: The bundle is updated to use MachineId to link OpenTelemetry entity with host entity.
• agent open telemetry grpc 1.1.5: The gRPC server is added to the bundle.

• 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.

• 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.

• grpc core 1.0.15: This bundle updates protobuf-java to version 4.29.3, protobuf-java-util to version 4.29.3, and proto-common-google-common-protos to version 2.50.1.
• agent process handling 1.0.7: This bundle adds the logic to identify the location of ctr on a Tanzu Cluster.

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.

• agent cgroup 1.0.0: This bundle parses control group (cgroup) data, which can be used as a service for container metrics.
• agent cri client 1.0.0: This bundle interacts with Container Runtime Interface (CRI )API gRPC endpoints. The interactions include the functionality for listing containers, reading container statuses, retrieving image statuses, and executing commands within a container.
• agent grpc channel cache api 1.0.0: This bundle exposes the access to Unix domain socket endpoints through ManagedChannels.
• agent grpc channel cache 1.0.0: This bundle provides a caching mechanism to access Unix domain sockets through ManagedChannels.

• agent backend 1.0.4: A null check is added for the messageId field in the JSON data that is received from the backend.
• agent JVM handling 1.0.10: A new process, UnifiedProcess, for JVM attachments is added.
• agent process handling api 1.0.2: The method to retrieve a UnifiedProcessBuilder with extended capabilities is added.
• agent process handling 1.0.6: This bundle is updated to enhance the file permission settings to copy the temporary files in rootless Podman environments. The podman info command is now used to locate Podman sockets for individual users. Also, the following changes are added:
  • CRI processes are now handled by utilizing the new UnifiedProcess abstraction, which enables support for CrioProcess.
  • CrioUtil is now extended to work with CriClient when configured.
  • The environment variable, INSTANA_USE_CRI_CLIENT (default: false) to enable the CriClient is added.
• agent util 1.0.7: The bundle is updated to add the following components:
  • a helper for exception-throwing functions
  • a utility for managing Futures
  • a helper for stopping ThreadPools Also, LinuxProcFileParser from the process handling bundle is migrated to this bundle.
• agent 1.1.742: The bundle is updated to improve entity management by keeping entities alive with empty data to prevent them from being marked offline. The handling of empty files is enhanced by returning zero-length byte arrays. Also, the process to add public IP gateway interests is modified to be synchronous instead of asynchronous.

• 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.

• 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.

• agent JVM handling 1.0.9: The bundle is updated to improve logging when a JVM connection cannot be used.
• agent process handling 1.0.5: The bundle is updated to fix an issue where wrong sockets were set for ContainerD instances. Also, the agent ignores the control region on z/OS now. Copying files into Podman containers is improved.
• agent socket server 1.0.2: The bundle is updated to fix a race condition for JVM connections.
• agent 1.1.741: The bundle is updated to add a monitoring event when the agent uses an incompatible Java version.

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.

• 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.