Build 287

Adding entity names in the alert titles for custom or built-in event alerts

You can now enable the Include entity name in alert title, when you configure alerts for custom or built-in events. This feature adds the name of the triggering entity to the alert title. It adds more context and allows customers, including Site Reliability Engineers (SREs), to quickly identify the triggering entity of the alert at a glance. For more information, see Configuring and managing alerts.

Business monitoring stack

You can now view the application, Kubernetes, and infrastructure stacks that are supporting your business processes and activities.

Concert integration

The Instana integration with IBM Concert is now generally available (GA). With this integration, you can now view the vulnerability information from Concert in Instana. For more information, see Integrating Concert with Instana.

Custom call metrics (public preview)

Instana now supports adding custom metrics to calls through SDK. You can use these metrics to filter calls numerically and chart aggregated values. For example, you can track the mean or max value of a custom buffer size in your request handling over time. For more information, see Custom call metrics.

Download custom dashboard

You can now download a custom dashboard as a PDF file. For more information, see Downloading custom dashboards as PDF files.

Enable Subresource Integrity (SRI)

Enabling Subresource Integrity (SRI) for the JavaScript agent is now generally available (GA). You can change configurations under the website configuration tab to enable or disable Subresource Integrity. For more information, see Enable Subresource Integrity.

Integration package management (public preview)

Instana users can now extend the observability capabilities through integration packages, which bundle reusable custom dashboards for monitoring new systems or technologies. This approach is combined with OpenTelemetry, eliminates the need to wait for new product releases to support observability for these systems. For more information, see Integration package management (public preview).

Logging

The Logs feature is now available from the navigation menu in the Instana UI. For more information, see Logging.

Service Level Objectives for Synthetic Monitoring (public preview)

You can now create an SLO for synthetic tests. For more information, see Creating an SLO. Use the Synthetic Tests tab on the Create Service Level Objective (SLO) dialog, then select one or more synthetic tests. Create an SLO for the results of synthetic tests over a time window you define, by selecting the Availability Blueprint. To create an SLO for the response time of synthetic test results, use the Latency Blueprint. To set an objective for tests being attempted, use the Traffic Blueprint.

Snowflake sensor

The Snowflake sensor is now generally available (GA). For more information, see Monitoring Snowflake.

Support for HAProxy 3.0

The HAProxy sensor supports HAProxy 3.0. For more information, see Monitoring HAProxy.

Synthetic monitoring

• Credentials tab is added on the Synthetic monitoring page. The list of credentials is displayed on the Credentials tab. For more information, see Viewing credentials.

• A new Synthetic monitoring endpoint is available to retrieve the metric definitions for Synthetic monitoring. For more information, see OpenAPI.

• Synthetic monitoring PoP can be installed in an online environment. For more information, see Deploying self-hosted Synthetic PoP with popctl.

Turbonomic integration

The Instana integration with IBM Turbonomic is now generally available (GA). With this integration, you can collect, view, and run the actions that are recommended by Turbonomic for your applications in Instana. For more information, see Integrating Turbonomic with Instana.

Alerts based on severity

You can now configure different alert channels for different severities in Smart Alerts for infrastructure and applications. Alert notifications are sent to different alert channels based on the severity of the issue.

Ansible actions

You can now import and run Ansible workflow job templates from your Ansible Automation Controller as Ansible actions. For more information, see Automation Action Ansible.

Business monitoring - Analytics

The span details on a business analytics call page now contains hyperlinks to the respective activity and process summary pages.

Business monitoring - Top services

The Top Services chart on the Business activity dashboard now displays more than one supporting service, when applicable.

Event disablement and alert suppression

When you close an issue or incident manually, you can now mute alerts and disable event configuration. For more information, see Manually closing issues and incidents.

Run action - Recommended actions

The capability to run an action is now added in the Recommended Actions tab. For more information, see Recommended actions.

Synthetic monitoring

• The New Location button is accessible only from the Locations tab.

• A custom environment variable for the Browser Script Playback is added in the Synthetic monitoring PoP Helm chart. You can specify which web driver version to use with the custom environment variable.

Thresholds for application Smart Alerts

You can now set thresholds for the warning and critical severities in Smart Alerts for applications. For more information, see Smart Alerts for Application monitoring.

Erroneous status code for Webpage Simple tests

The test execution status of the Synthetic monitoring Webpage Simple test was displayed as Successful even when the status code was not 200. This issue is now resolved.

Now, the status code 200 is displayed only when the test execution is successful. If the test execution fails, a different status code is displayed.

Improved reliability of ARN tagging for AWS lambda calls

AWS lambda calls were only tagged with an AWS function ARN if the call could be correctly linked to the corresponding function entity from infrastructure monitoring. The AWS ARN is now directly extracted from call monitoring data and does not depend on matching infrastructure monitoring.

Unable to view calls

No calls were displayed when you access the Analytics page from the Top List widget on the Custom Dashboard page. This issue is resolved.

Unable to view source code of errors

The source code of errors was not visible in the stack trace in call details. This issue is resolved.