Agent bundle releases

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. This data can be retrieved by clicking on the Collect Support Information button in 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.