Build 164


On-Premises Release Notes

For an upgrade to the new version please follow the Packaged Based Operations manual.

Note: The minimum default heap requirements for our appdata-writer component changed from 2GB to 4GB:

      kafka: '3G' # (string) Virtual memory size assigned for the Kafka service. |
      elastic: '3G' # (string) Virtual memory size assigned for the Elasticsearch service. |
      cassandra: '3G' # (string) Virtual memory size assigned for the Cassandra service. |
      zookeeper: '2G' # (string) Virtual memory size assigned for the Zookeeper service. |
      acceptor: '2G' # (string) Virtual memory size assigned for the Acceptor service. |
      eum-acceptor: '1G' # (string) Virtual memory size assigned for the EUM Acceptor service. |
      cashier: '1G' # (string) Virtual memory size assigned for the Cashier service. |
      filler: '3G' # (string) Virtual memory size assigned for the Filler service. |
      groundskeeper: '1G' # (string) Virtual memory size assigned for the Groundskeeper service. |
      issuetracker: '2G' # (string) Virtual memory size assigned for the Issuetracker service. |
      processor: '2G' # (string) Virtual memory size assigned for the Processor service. |
      uibackend: '2G' # (string) Virtual memory size assigned for the UI-Backend service. |
      butler: '1G' # (string) Virtual memory size assigned for the Butler service. |
      appdataprocessor: '2G' # (string) Virtual memory size assigned for the AppData Processor service. |
-     appdatawriter: '2G' # (string) Virtual memory size assigned for the AppData Writer service. |
+     appdatawriter: '4G' # (string) Virtual memory size assigned for the AppData Writer service. |
      appdatareader: '2G' # (string) Virtual memory size assigned for the AppData Reader service. |
      appdatalegacyconverter: '2G' # (string) Virtual memory size assigned for the AppData Legacy Converter service. |

Cumulative Features from Release #162, #163, #164

  • We've introduced "Starts With" and "Ends With" operators for use in Analyze and the Application Perspective creation dialogue.
  • Exclude specific website data from being transmitted to Instana using the ignoreUrls API:

    • additionally suppresses any data transmission when the document URL matches one of the regular expressions, and
    • suppresses data transmission for resources when the resource URL matches one of the regular expressions while
    • continuing to suppress data transmission for XMLHttpRequest and fetch requests when the called URL matches one of the regular expressions.

URL Shortener

Instana supports deep linking to complicated view configurations, e.g. to the analyze views. While this means that it is easy to share / bookmark points in the Instana user interface, it also means that these deep links need to encode a lot of information and can therefore be quite long. It can be disrupting in communication tools to paste these long links. In order to reduce disruptions we now offer the option to generate short URLs.

The short URL dialog is shown when using the go to address bar shortcut in your browser, i.e. CMD+L on MAC and CTRL+L on Windows and Linux.

URL shortener prompt shown when using the address bar shortcut


Instana now supports monitoring Spark applications running on AWS EMR. See more information here.

Splunk Logging

Configure your Splunk Instance and see a direct link to your logs from views in Instana. For configuration details, see Splunk.

Humio Logging

Configure your Humio Instance and see a direct link to your logs from views in Instana. For configuration details, see Humio.

Kubernetes CPU and Memory Usage

You can now view CPU and memory usage for Kubernetes Namespaces, Deployments, Services, Nodes and Pods. The usage is calculated from the containers that are running as part of these resources. The usage is displayed alongside the total resource requests and limits and can help gain insights into how well-specified your limits and requests are.

Improved Call Details

Enhanced Call Details now help to clarify the structure of calls further by providing additional insights into the spans of each call - such as which span the errors belong to and the infrastructure relating to the span. Improved Call Details


  • If the root call of a trace correlates with EUM information, the relevant information is now displayed in the Call Details.
  • Support messaging spans coming from Instana Trace SDK, Jaeger or Zipkin and transform them into calls of type MESSAGING.
  • Improve PHP wordpress and error spans labels using action and error message.
  • Add service mapping for CockroachDB.
  • PHP Tracer 1.4: SDK now allows setting of a Service name
  • PHP Tracer 1.4: now supports Couchbase
  • PHP Tracer 1.4: Instrumentation for Predis and PHPRedis now collect method arguments
  • The user interface no longer forces phones and tablets into responsive modes and therefore results in a more usable mobile experience.
  • You can now search for for all aws services that run in a specific AWS account.
  • Filter boxes on top of tables responded in unexpected ways to user input. This is now fixed.
  • The user interface now loads slightly faster.
  • Typeahead and autocompletion components were reworked to cope with large amounts of data.
  • Add service mapping rule for Cockroach DB.
  • Users are now enabled to have more control over their privacy preferences thanks to a finer range of settings. Furthermore, users can decide to participate in the User Testing Group to help Instana improving the product.
  • Improvements to settings page: Users can now select more than one application when scoping the Custom events, Alert configurations or Maintenance windows in the "Application Perspective". The new "Application Perspective" scope is similar to using the Dynamic Focus query "". If more than one application is selected in the new "Application Perspective" scope, then an OR operator is used between the Dynamic Focus queries.
  • Instana works with Istio 1.2+ out of the box. If it doesn't, please consult Kubernetes > Istio for additional configuration.
  • The Instana Agent helm chart now supports the enablement of a PodSecurityPolicy. Users can specify their own, or have the helm chart create one. For users that install the Instana Agent using instana-agent.yaml, please see the Instana docs instead.
  • Improved the reliability of the alerting of incidents in situations where there are extreme spikes in change or presence events.
  • S3 sensor: buckets now have an identifier of whether the bucket is public.
  • EBS sensor: optimized number of describeVolumes call towards EC2 API.


  • JBoss Sensor: Prevent change events firing when metrics change.
  • Change events: Sometimes partial data received by sensors got incorrectly merged, leading to very short (typically 1 sec) interruptions and "change events". This is fixed and change events are only created when data gets updated.
  • Custom Events API: Values for time-window and grace-period are only restricted to any full second value in the valid range.
  • Mule Sensor: Added support for Application stats for older Mule versions.
  • Varnish Sensor: Absolute paths in includes are now correctly handled.
  • Alerts: container-specific labels were missing in alert notifications for container entities, such as Docker.
  • Analyze: merged the call.technologies and tags to technology.
  • Renamed the Cloud Foundry tags from cf.XXX to cloudfoundry.XXX.


  • Dynamic Focus: Queries with a leading wildcard in the default context without a specified keyword, for example, *server, are not supported anymore as they lead to poor performance. However, when specifying a keyword, leading wildcard queries are still supported, for example,*server.
  • We are deprecating support for the extensions/v1beta1 and apps/v1beta2 API versions for DaemonSet, Deployment, and ReplicaSet in our Kubernetes Sensor, following the announcement from Kubernetes that these deprecated API versions will soon be removed in Kubernetes v1.16. Please update to our latest helm chart, Kubernetes agent YAML or OpenShift agent YAML.
  • Unmonitored Hosts removed: With more users transitioning to containers we have received many questions of the accuracy of Unmonitored Hosts in the Infrastructure Map. As this functionality relies on inaccurate and incomplete data we have decided to remove it. Instead, we advise users to use the services dependency map which gives a precise view based of the unmonitored services and the underlying infrastructure.