Build 142

September 18, 2018

Application Dependency Map

After the introduction of Application Perspectives we are continuing to release new features like the application dependency map. It is now accessible through the application dashboards “Dependencies” tab. Here is an overview of how it can help you:

  • Provides an overview of the service dependencies within your application.
  • Particles show a visual representation of calls between services to understand communication paths and throughput
  • Leverage different layouts to quickly gain an understanding of the application’s architecture.
  • Enables quick access to relevant detailed information for each service (dashboards, flows, calls and issues).

Check out the full description.

More Application Perspectives Features

  • Custom Endpoint Mapping: Define how endpoints are extracted for HTTP services. Check out the full description.

SAML authentication

  • Support authentication via SAML compliant identity providers. Check out the full description.

Other Features

  • Node.js: Add MSSQL (Microsoft SQL Server) instrumentation (supports mssql, version >= 4 via tedious driver).
  • Node.js: Report uncaught exceptions as incidents and via span/trace (disabled by default).

Improvements

  • Application Perspectives: The Analyze view now has a progress indication for long running queries.
  • Application Perspectives: PHP services defined based on HTTP host header (when available).
  • MySQL Sensor reports if performance_schema is not accessible.
  • JVM sensor: Number of collected Dropwizard metrics is limited and configurable. No longer collect Dropwizard metrics for Cassandra and Elasticsearch as they are already monitored
  • AWS Lambda Sensor Dashboard will display attached triggers in sidebar.

Fixes

  • Services are sometimes not correctly linked to infrastructure entities.
  • Node.js: Tracing context sometimes getting lost after a MySQL call.
  • AWS sensors: AWS entities are sometimes not removed in ui when deleted (e.g. Kinesis stream)