Build 277

Amazon Timestream

Instana now automatically discovers and monitors Amazon Timestream databases. For more information, see Monitoring Amazon Timestream.

Manually closing issues and incidents

You can now manually close issues and incidents. To manually close issues and incidents, go to the event page where you can select the issue or incident that you would like to close.

For more information, see Manually closing issues and incidents.

Numeric tags for grouping

In the Instana UI, you can now use numeric tags like CPU count to group entities in Analyze Infrastructure and on custom dashboards.

Probable Root Cause (public preview)

Probable Root Cause is now available in public preview. The Incidents page in Instana for Smart Alert on the following entity types is now enhanced with the Probable Root Cause section, when a Probable Root Cause is identified for an incident:

• Application perspectives
• Services
• Endpoints
• Service Level Objectives on application perspectives

The Probable Root Cause section includes an identified Probable Root Cause entity that can be any entity that is monitored by Instana, from a process to an endpoint to a service. The section also includes the following information:

• Statistics about trace data around the entity that provides some reason for selecting a certain Probable Root Cause
• Events, such as Change events, Issues, or Incidents that occurred on the identified Probable Root Cause entity and a probability level for the result

To see Probable Root Causes that are identified on Smart Alerts on applications, services, or endpoints, go to the Incidents page of a Smart Alert.

For more information, see Root Cause Analysis.

Processes and perspectives in Business Monitoring

Navigating to the Business Monitoring page now directs you to the Business Perspectives list, where you can view and create perspectives with descriptions, related processes, and health status. The Configuration tab allows editing of perspective filters, names, and descriptions.

Additionally, the Business Process list page now supports filtering processes without needing to create a perspective.

For more information about business perspectives, see Business Monitoring dashboard

SAP HANA sensor

Instana now supports both local and remote monitoring of the SAP HANA database.

For more information, see Monitoring SAP HANA.

Share and invite

The Short Link icon in the Instana UI is now replaced with the Share button. Use Share to add a custom message and direct invitees to a specific area where collaboration is needed. You can use it while you set up the product, analyze the application performance, or investigate incidents with colleagues. For more information, see Working with the user interface.

Synthetic monitoring

The Multi-tenant Synthetic PoP is now available in private preview. For more information, see Deploying a Multi-tenant Synthetic PoP (private preview).

API tokens and personal API tokens

Both the API Tokens and Personal API Tokens sections are now enhanced with more details. The Created, Created by, and Last used fields are now available for API Tokens. The Created and Last used fields are available for Personal API Tokens. You can now sort tokens by these fields. These fields are automatically populated on creating new tokens. The existing tokens show the Created by and Created fields as Unknown, while only the Last used field gets updated based on the usage.

IBM i sensor: Wildcard support for Active Jobs and Inactive Jobs

The use of * wildcard character for monitoring IBM i instances:

• Active Jobs wildcard support for metrics: You can * as a wildcard character in any part of JOB_NAME within the user_specification:activeJobs:jobs section of the Instana agent configuration file.
• Inactive Jobs wildcard support for custom events: You can use * as a wildcard character in any part of JOB_NAME to identify and trigger events based on inactive job states within the user_specification:activeJobs:event:inactiveJobs section of the Instana agent configuration file.

For more information, see Monitoring IBM i instances.

Monitoring Clickhouse

Instana now supports Clickhouse 24.6 and earlier versions.

Logging

In the Analytics page, the filter option in the Analytics tab for Logs now supports case-insensitive filtering. Previously, you could filter only with exact case matching. For example, previously, filtering by log_level="ERROR" returned results but all other cases "Error" or "error" returned zero results.

Running components

Running components did not render enclosing components, such as an IBM MQ Queue Manager. They displayed only the underlying components of the Queue Manager, such as Queues, Topics, and Channels. Now, the system displays enclosing components, along with the components they enclose if they contain more than one element. For example, the system does not display Docker containers with only one process. However, it now displays Docker containers with more than one process as running components.

SAP ABAP sensor

The SAP ABAP sensor dashboard includes the following enhancements:

• A line chart is added to visualize user login successes and failures.
• The Work Process column is added in the System instance Summary page (Platforms > SAP > System > System Summary).
• Task Type filtering options are added in the following tables: User Statistics, Memory Statistics, Database Connections, and Jobs Information.
• Poll rate can be modified for fetching metrics from the SWNC_GET_WORKLOAD_SNAPSHOT function module based on client requirements in the configuration.yaml file.
• Exceptions that are caused by missing the JAR files or native libraries are highlighted. The exception list sourced from templates is removed.

Synthetic monitoring

The Synthetic Monitoring section includes the following enhancements:

• In the Summary tab for a Synthetic test, the Results tile includes several filters and a link to the Results tab. When you filter test results in the Results widget, the test results in the Results tab are sorted based on the filter that you selected.
• For the RBAC Improvements private preview, the group definition allows you to view which tests the users in the group can access based on the access inherited from the Applications permissions in the same group definition.
• You can set the trace level for the Redis pod in the Synthetic PoP. For example, to set the DEBUG trace level for the Redis pod, pass --set redis.traceLevel=“DEBUG” when you install the PoP.
• The console logs for webpage script now logs each SeleniumIDE command for better troubleshooting.
• The pdcollect tool is enhanced to collect the pod list information of Synthetic PoP.

Trace detail view

The readability of metrics is enhanced by formatting Service Endpoint List.

Instantaneous initial loading

Loading times of all views have been improved.

Broken layout

A layout issue which affected many was introduced. Although clearing up the browser cache would fix the layout, a fix was applied so that a simple refresh was necessary

Dataset axis selection

Previously, moving a dataset from one axis to another or within the same axis was not possible in a time series configuration in the custom dashboard. This issue is now fixed.

IBM ACE Tracing

When the MQRFH2 header was created for an IBM MQ message, the Format attribute could be empty. This issue is now fixed.

Metric selection for many plugins

The infrastructure metric catalog only showed metrics for 250 plug-ins maximum. The issue is now resolved and the infrastructure metric catalog displays metrics from all the plug-ins used.

SAP ABAP instance

Previously, SAP ABAP instance showed unconnected upstream and downstream calls in the Context Guide. This issue is now fixed.

Synthetic monitoring

• Synthetic tests that use a script could not be created if the script contained comments that include missing credentials or credentials that are not valid. This issue is now fixed.
• When an API script failed due to an unknown error, no error message was displayed on the result details page. This issue is now fixed.
• The error message module 'signal' has no attribute 'SIGTSTP' was displayed when the synctl CLI was run on a Windows server. This issue is now fixed.