Build 170

2020-03-06

On-Premises Release Notes

The 170 build is the first new release that utilizes docker as an abstraction layer. We retire the Chef Cookbooks and replace them with an installer binary instana-console. It contains all the commands required for the Instana operations.

To update to 170, follow these three steps:

  1. Verify that your package-based installation is version 164.
  2. Install Docker.
  3. From the new installer, execute instana containerize.

For more details, see our container-based documentation.

To enable on-prem PCF or vSphere, you need to set feature toogles in the settings.hcl file.

toggle "pcfEnabled"{
  value="true"
}
toggle "vsphereEnabled"{
  value="true"
}

Cumulative Features from Release #165, #166, #168, #169, #170

  • Prometheus alerting.
  • Coralogix log integration.
  • Faas tags like function name and version are now available on the source and destination of each call. This can be used in AP configuration as well as in Unbounded Analytics. The following AWS services also have an ARN field included:

    • Beanstalk
    • DynamoDB
    • EBS
    • EC
    • ELB
    • EMR
    • ES
    • Kinesis
    • Lambda
    • MQ
    • RDS
    • S3
    • SQS
  • [Node.js] support for Apigee Microgateway (edgemicro).
  • [Node.js] support for older Winston versions (<= 2.x) and express-winston.
  • [Node.js] support for pg-native.
  • When downloading the details of a trace into a JSON file, some fields have been re-ordered to improve readability and additional fields have been added, such as the span's parentId.

Cloud Foundry Application

A new built-in health event has been added to catch inconsistencies between the desired number of instances and those that are currently running. When the number of running instances is higher than 50%, but less than 100%, of the desired number of instances, the event is a warning. If it's 50% or lower, the event is an error. For example, this event triggers when there are repeated crashes of Garden containers preventing the Cloud Foundry Application reaching a healthy state.

Incidents view

A rebuild of the Incidents view now reflects the visual changes and concepts that were applied in other product areas. There are also some small changes and improvements to help you understand and quickly find events.

Filtering and grouping on the source entity in Analyze

A call has both source and destination applications; service and endpoint. Until now, tags like application.name or service.name in Analyze were applied to the destination of calls. This feature also allows filtering and grouping on the source.

Infrastructure entity tags such as agent.tag or host.name can also be applied to both the source and destination of a call. However, this option is not available for call tags such as call.http.path or call.tag, which are properties on the call itself and are independent of the source or destination.

Sample queries with this feature:

  • What are the endpoints called by shop service? Query: filter by service.name=shop on the source and group by endpoint.name on the destination.
  • What are the hosts that make database calls? Query: filter by call.type=DATABASE and group by host.name on the source.

Native AWS Lambda Tracing

As an alternative to the AWS X-Ray integration, Instana now offers native tracing for AWS Lambda functions. This new native tracing of AWS Lambda functions provides three big advantages over the previous X-Ray based tracing:

  • The tracing of Lambda functions now seamlessly correlates with tracing of other components monitored via the Instana agent.
  • Instana can now differentiate among traces coming from different versions of the same AWS Lambda function.
  • Reduced need of pulling costly X-Ray data from AWS.

This feature is currently only available for AWS Lambda functions based on the Node.js runtime.

Monitor AWS Lambda Versions Independently

Previously we aggregated metrics for all versions of the same AWS Lambda function. Starting with this release, you can monitor all versions independently and view metrics for each version. This enables you to easily compare the behaviour between different versions (for example, when publishing a new version to production).

Splunk to Instana

Configure your Splunk dashboards and navigate to Instana entities directly from your logs. For more information, see our Splunk docs.

Nomad TLS

Instana now supports monitoring Nomad instances with TLS enabled. For more information, see our Nomad docs.

Showing Inbound or All Calls within Application Perspectives

Previously certain dashboards within Application Perspectives displayed just the "Inbound" calls, and other dashboards showed "All" calls and related metrics. With release 166, it's possible to switch between these perspectives.

For more information, see our docs.

JavaScript Stack Trace Translation

JavaScript stack trace translation provides readable and more actionable stack traces within our website monitoring area. Instead of mangled and unreadable stack traces, we will show references to locally existing files whenever possible. For more information, see our docs.

Animation showing the difference between readable and minified stack trace.

PostgreSQL Replication Delay

Instana now supports monitoring replication delay presented in bytes and seconds. See more information, see our PostgreSQL docs.

CRI-O container runtime

Instana now supports monitoring CRI-O containers. For more information, see our CRI-O docs.

VMWare vSphere

Instana now supports monitoring vSphere clusters, ESXi hosts and virtual machines. For more information, see our vSphere docs.

Cloud Foundry: Service navigation

From any Cloud Foundry application dashboard, it is now possible to navigate to the services powered by it.

Application Perspectives: Custom events for Inbound and All Calls

Custom events for Application Perspective can now be created for either 'Inbound Calls' or 'All Calls' metrics. Built-in rules remain unchanged.

New built-in events for RabbitMQ

  • Disk free alarm: when free disk space drops below the configured limit, an event is fired.
  • Socket usage rate: when 90% and 95% of available sockets are used, new "Warning" and "Critical" events are fired respectively.

Cloud Foundry

Added health-check indicators for PCF applications.

Kafka

Added broker lag calculation support.

Nginx tracing preview 0.7.0

Added compatibility check enforcing the OpenTracing module from Instana. For more information, see https://github.com/instana/nginx-tracing.

LogDNA Logging integration

In addition to Humio and Splunk, we now also support integration into LogDNA from Instana. For more information, see our LogDNA docs.

Jump to Analytics from Application Dashboards

In Application, Service and Endpoint dashboards, we have added a new feature that will help you get started with Analyzing calls displayed in your dashboards. highlight contextmenu

Tibco EMS

Instana now supports monitoring Tibco EMS. For more information, see our Tibco EMS docs.

Improvements

  • Golang runtime: for searching your infrastructure entities, traces, and calls, the search and analysis tags go.app.name and go.version are exposed.
  • MongoDB: calls to a MongoDB cluster are mapped to a service named after the cluster replica set name.
  • Nginx: filter calls to Nginx by Nginx technology.
  • AWS RDS: enhanced metrics gathering for the CPU credit usage and CPU credit balance.
  • Kubernetes 1.15 support.
  • Kubernetes namespace dashboard now displays used requests and limits, even when no resource quota is set.
  • Calls to Consul nodes are now mapped to a service whose name is the Consul cluster name.
  • OpsGenie integration: alerts for incidents now have priority P1 instead of P2. The priority P2 is now only used by critical issues.
  • AWS ELB sensor: optimized fetching load balancers.
  • Kubernetes dashboards:dDisplay cluster icons for GKE and EKS. Also display an additional Rancher icon for clusters managed by Rancher.
  • Dynamic Focus: to enable searching for a Kubernetes cluster by distribution and management layer, we have introduced 2 new keywords entity.kubernetes.cluster.distribution and entity.kubernetes.cluster.managedBy. Supported values for entity.kubernetes.cluster.distribution are gke, eks, openshift, and kubernetes. Supported values for entity.kubernetes.cluster.managedBy are rancher and none.
  • Various runtimes: search keywords and analysis tags have been added for filtering, e.g. Crystal, Haskell, .Net Core, Python, and Ruby on both the application name or version. They follow the generic format of <runtime>.app.name and <runtime>.version, exposed for searching your infrastructure entities, traces, and calls.
  • OracleDB sensor: configurable poll rate is now available.
  • Inbound calls: instead of two filters on application.name (source and destination), go to Unbounded Analytics with a more straightforward inbound calls filter named call.inbound_of_application.
  • Inbound calls: configure applications with a default scope to display only the inbound calls or all calls. This also affects the default alerting on applications; those KPI's are selected corresponding to the chosen scope.
  • Unbounded Analytics: internal calls and synthetic calls are hidden by default in the Calls & Traces Analytics. To include them in the query, add the include_internal=true and include_synthetic=true tag filters. On the filter bar, a "Hidden Calls" filter is also available.
  • On the infrastructure tab of application perspective dashboards (application/service/endpoint), Lambda infrastructure items now have additional links to the Lambda function version, the Lambda function, and the region.
  • Custom events: more options have been added to the grace period values.
  • AWS Lambda sensor: by default, Instana monitors the five most recent versions of each Lambda function individually. In the case that the feature has been disabled explicitly via configuration or the required IAM permission is missing, Instana falls back to aggregating the metrics for all versions.
  • Support for tracing PHP 7.4.
  • PHP Tracer 1.5 traces Symfony and Twig.
  • PHP Tracer 1.5 displays total compile time.
  • PHP Tracer 1.5 displays memcached result codes and messages.
  • PHP Tracer 1.5 supports tracing Pipelining and Transaction in Predis.
  • PHP Tracer 1.5 traces exit codes in shell calls.
  • Link database calls to AWS RDS instances.
  • Custom service mapping: process.name can now be used.
  • Pipeline Feedback: Only one Release notification displays at a time.
  • Built-in disk space detector: improved algorithms to reduce false positives for short-term up to 1h in advance capacity warning.
  • Kafka sensor: added Broker topic metrics monitoring, metrics gathering improvements based on Kafka version, Cluster metrics. Broker dashboards improved. Cluster dashboard appearance and positioning improved.
  • RabbitMQ Sensor: added File system and Socket descriptor usage.
  • New tags available in Application Perspectives:

    • Kubernetes tags: kubernetes.cluster.managedBy and kubernetes.cluster.distribution.
    • Cri-o tags: crio.container.id, crio.container.name, crio.container.image.name, and crio.label.
    • Generic container tags: container.id, container.name, container.image.name, and container.label.
  • Application perspective creation: filters on tags service.name, endpoint.name and infrastructure tags such as agent.tag or host.name can now be applied to the source of the call.
  • Built-in service mapping rules: rules based on cluster tags now take precedence over rules based on single-entity tags. For example, {elasticsearch.cluster.name} over {docker.label.com.docker.swarm.service.name}.
  • New memory metrics available on a Linux host: swap free and total, memory in buffers cache, cached and available memory.
  • Jenkins: support for an instance running in a container.
  • Metric drop detection: sudden and complete drop detectors yield fewer false positives when the metric is very sparse.
  • Host search improvement in Splunk integration: when the hostname in Instana is a shorter version of the hostname in Splunk.
  • Container based agents can now be configured to report to multiple backends. For more information, see our docs.

Fixes

  • AWS RDS: fixed false positives for the CPU credit balance health event.
  • Couchbase: fixed service mapping using cluster name and fallback to host name. Added endpoint mapping rule using the bucket name.
  • Docker: fixed false positives for the memory usage health event.
  • Fixes issue that when the canConfigureApplications permission was granted, an application could only be selected for the scope of a custom event, alert or maintenance window.
  • Application Perspectives - Error Messages: fixed spike-chart to show correct numbers that are in line with the total count.
  • Releases API: The ID length for a release marker is not limited to 42 characters anymore.
  • Alert notifications: "Container Names" attribute is not generally added to e.g. Slack messages anymore as "not available" when empty.
  • The PagerDuty alerting channel is now using PagerDuty Event API v2, since v1 is deprecated.
  • Event details: for some events, the window-size of the time-window/rollup used by the Built-in Events or Custom Events was not included in the timeframe shown by the chart. The used timeframe is now consistently [start - windowSize, end]. The Analyze button of an event also uses the same timeframe.
  • Change and presence events do not have a duration anymore.
  • When tracing ElasticSearch, PHP Tracer 1.5 no longer changes result counts.
  • A race condition in PHP-FPM sensor caused snapshot information to be missing in dashboards.
  • Creating an Application Perspective with the aws.arn tag.
  • Improved the startup for the SAP Hana sensor.
  • Memcached Sensor: the correct value for used bytes is now displayed.
  • Fixed pagination of "Infrastructure" lists for Services in the Application Perspectives product area.
  • Nginx/Envoy tracing preview 0.7.0: Several fixes for more reliable, faster agent connection, compatibility, better debugging and logging. For more information, see https://github.com/instana/nginx-tracing.
  • Built-in event: unreachable cassandra nodes is now working as expected.
  • Instana OpenAPI specification document fixes related to GET and PUT endpoint of custom event specification.
  • Fixed configuration parsing in the Docker agent image. For more information, see Upgrading The Agent Container Image.

Deprecations

  • Another reminder that 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.
  • Nginx/Envoy tracing preview: libinstana_sensor < 0.7.0