Build 255

Build 255 is released on 8 August 2023.


Multiple levels of grouping in Analyze Infrastructure

You can add up to 5 levels of grouping in the Analyze Infrastructure page in the Instana UI to analyze infrastructure across multiple dimensions. For more information, see Analyze Infrastructure.

Multiple levels of grouping in Analyze Infrastructure

Support for the instrumentation of go-fiber in Go Tracer

Support is added for the instrumentation go-fiber in Go Tracer. For more information, see Supported Frameworks and Libraries - Monitoring Go.

Automation Ansible sensor

With the Automation Ansible sensor, you can import Ansible playbooks from the Ansible automation controller into the Instana Action catalog. You can run Ansible actions on the Ansible automation controller. For more information, see Automation Action Ansible.


Apache HTTPd tracing

Apache HTTPd tracing modules can now dynamically enable or disable tracing by detecting for configuration changes in the agent configuration file. For more information about configuring Apache HTTPd tracing, see Apache HTTPd.

IBM Db2 LUW sensor

You can now configure the default value for both the loginTimeout property and the lockAndLongQueryInterval threshold interval for the IBM Db2 LUW sensor. For more information, see Monitoring IBM Db2.

Metric threshold warning

A warning is displayed on the dashboards of Instana to notify users that some metrics are not displayed in the Instana UI because most plugins have a limit of 3000 metrics per entity.

Metric explosion warning on a dashboard with missing metrics

Tuxedo sensor

You can run Tuxedo sensor with the non-root Instana agent user from version 1.0.2 and later. Tuxedo sensor needs the permission to switch from the agent user to the Tuxedo user. To grant this permission for Tuxedo sensor, you need to add more settings in the /etc/sudoers file if the agent user is not root. The agent user runs the script with different Tuxedo users as shown in the following example:

_agentuser_ ALL=(_tuxuser1_)       NOPASSWD:SETENV:/home/agentuser/instana-agent/data/tmp/*/
_agentuser_ ALL=(_tuxuser2_)       NOPASSWD:SETENV:/home/agentuser/instana-agent/data/tmp/*/
_agentuser_ ALL=(_tuxuser3_)       NOPASSWD:SETENV:/home/agentuser/instana-agent/data/tmp/*/


  • _agentuser_ is the Instana agent user.

  • _tuxuser1_, _tuxuser2_, and _tuxuser3_ are Tuxedo users that are defined in the agent configuration.yaml file with the parameter tuxuser.

Note: If multiple Tuxedo users are there for multiple Tuxedo domains, then all these users must be added in /etc/sudoers file to monitor the corresponding Tuxedo domains.

The Instana agent user can run the script as any other users with the setting (ALL) in /etc/sudoers file as shown in the following setting:

_agentuser_ ALL=(ALL)       NOPASSWD:SETENV:/home/agentuser/instana-agent/data/tmp/*/

Note: Use the absolute path of the Instana agent tmp directory and a wildcard as the path of the script. Usually, the Instana agent tmp directory is in the data directory of the directory where the Instana host agent is installed.

User lists

  • Now, the general user list, which can be found by clicking Settings > Team settings in the Instana UI, includes the two-factor authentication status of each user. In addition, you can sort the general user list based on the columns.
  • Previously, when you clicked Settings > Authentication > Two Factor > Users in the Instana UI, you could see the list of two-factor authentication users. Now, the list is removed because the information is included in the general user list, which can be found by clicking Settings > Team settings.


Application dependency map

The issue that caused services to be displayed as a single column is now fixed.

IBM ACE sensor

  • Previously, users failed to query entities with Dynamic Focus Query (DFQ) for message flows. For example, when you filtered with '*', nothing was returned even though some message flow entities exist. The issue is fixed now.

Synthetic Monitoring

The following fixes are included in this release:

  • Removing all assigned locations when you edit a Synthetic test was not a viable option. Now you can remove all assigned locations when you edit a Synthetic test.
  • The Create and Save buttons were enabled without validation checks for the Synthetic tests. Now the buttons are enabled only if the data that you entered for the Synthetic test is valid.
  • Consistency problems no longer occur when you change between ExpectStatus and ExpectJSON in an API Simple test in Advanced mode.
  • After the Synthetic PoP is upgraded, the link on the Location tab to the PoP sensor pages works seamlessly. It no longer stops working.
  • The Synthetic tests that were created with duplicate header elements and custom property elements failed. Now Instana supports only unique elements. You can no longer create Synthetic tests with the same name in multiple header elements or custom property elements.
  • Deleting empty script tests through the Instana UI was not a viable option. Now you can delete empty script tests by using the Instana UI.
  • Only one location was clearly visible in the Create Synthetic Test wizard. Now you can scroll and select any of the locations.
  • The Response Size KPI card on the Result Details page no longer shows an incorrect zero value.
  • The option to edit the main file name of a bundled script test for a Synthetic test was erroneous. Now the main file name of a bundled script cannot be edited. To change the main file name for a script bundle, you must delete and re-create the test and provide the correct main file name.

Temporary dynamic IBM MQ queue and service mapping

Previously, for each temporary dynamic IBM MQ queue that starts with the prefix "AMQ.", a service with the same name as the queue was created automatically.

Now, only one service with the name "jms" is created automatically for each temporary dynamic IBM MQ queue that starts with the prefix "AMQ.".

Tuxedo sensor

  • Previously, duplicated interprocess communication (IPC) message queues could appear in the IPC message queues list. This issue is fixed now.
  • Previously, the usage percentage was not displayed correctly in the IPC message queues list. This issue is fixed now.