Build 125

29 May, 2017


Endpoint Monitoring

The service extraction functionality has been enhanced with Endpoints. Configuring a rule of any kind, there is now an endpoints list attached to the form as seen in the following screenshot.

Endpoints are specified paths of the service rule above. To give an example, the user specified the request path match extraction string /myRESTService(/.*|$) for the service. The rule can now be further specified with endpoints. An endpoint represents a path of the service it belongs to. For example, if a user wants to track all endpoint methods, he can create a new endpoint with the request method match expression (.*), which just matches all. For the endpoint name, there are now predefined placeholders available. Taking {method} {path}, will result in the endpoints “GET /myRESTService”, “DELETE /myRESTService”, etc.

The list of all detected endpoints can be found in the services sidebar, or even in more detail in the dashboard itself.

You can jump to the traces the endpoint was involved in to investigate the calls in more detail.


The Endpoints are also available to further break down Web EUM applications. We start with the capability to break down Web EUM calls leveraging meta tags. Just define the naming patterns in the new Web EUM Service Definition.

If you, for example, defined meta tags in your Instana Javascript agent like this:

  • ineum('meta', 'deployment', 'production');
  • ineum('meta', 'page', 'login'); you can define rules to leverage the tags in order to name the Web Application and the Endpoints in them.

Simply use the placeholder to, for example, get the value of the meta tag “deployment”: {eum.meta.deployment}

Please refer to the Web EUM documentation in order to understand how to leverage meta tags for web pages.

Timeline Filtering

With the previous release, Instana introduced the new filter and search concept “Dynamic Focus”. With Dynamic Focus, users are allowed to filter each view given a search query. This ability is now applied to the timeline as well.

This is a screenshot showing a typical Instana state: There are currently two open issues and a lot of changes happened in the timeline. With the given query example, the timeline is filtered to the following state:

The search query is analysed to the given selected moment, so moving this time indicator will have an effect of the result, too.

OS Process environment variables

We have enhanced our process sensor, so that it automatically captures the environment variables of any monitored process.

Because the environment often contains sensitive data, it is of course filtered with the configured secrets.

Group by Host Tags

Some customers make extensive use of Tags to organize their hosts. Now you can also group your hosts on the Infrastructure Map leveraging the tags.

You can define a prefix that shall be used to determine the groups.

You might have set “hostGroup=” as a prefix and now want to group the hosts accordingly.

Simply open up the grouping menu, select Tag prefix and set it. The result will be a grouping by tags. In case more than one tag matches we will take the first tag and ignore the rest.

Newly supported Technologies



  • Improved support for Rancher and Weave networks in Kubernetes
  • Trace time skew adjustments are much more reliable
  • Improve .Net tracing performance
  • Capture request params and uncaught exceptions thrown from http handlers in Java
  • Support for Etcd running multiple api endpoints, and improved performance
  • Support “Show source” for PHP
  • Reduced memory consumption in the agent process for tracing
  • The containerized agent will automatically configure itself for docker pre 1.10
  • StatsD sensor now supports consuming Nomad StatsD data
  • Httpd sensor respects vhost name based resolution
  • Go: Better Error reporting and translation for the backend #27
  • Search for process arguments is now possible

Fixed Issues

  • Oracle Prepared statement could show up as [email protected]
  • No longer produce empty changes for Websphere data sources
  • Nging Sensor did not work when using a complex custom log_format
  • Go: X-Instana-S and X-Instana-T context conversion and handling #29
  • Ruby: ActionView span description #67
  • Ruby: HTTP Header values should not contain leading zeros #72
  • Ruby ActiveRecord: Accessing adapter name triggers DB connection #73

Known Issues

Search for terms that include white spaces and wildcards is not supported yet (e.g. ‘entity.label:”Shop *Service”’ does not work). If you remove the whitespace the search works (e.g. ‘entity.label:”Shop*Service”’ results in a working query).