TABLE OF CONTENTS
- Cumulative Features from Release #171, #172, #173
- Instana Smart Alerts
- Instana AutoProfile™ for JVM (open Beta)
- Cloud Foundry
- Nvidia GPU Monitoring
- Humio logging integration
- Cloud Foundry
- ELK Logging Integration
- Custom Service Rule
- Landing Page
- Context Guide
- Website Monitoring: Custom Events
- Website Monitoring: User-Timing Collection
- Website Monitoring: User Impact Based on Session Information
- IBM DB2
With this release we introduce a new repository for our instana-console binary. The advantage of the new repository is that its versioned:
Every instana-console binary version is tight to a specific container build, instana-console is tagged in the following way
You can find details e.g. how to change your existing configuration in the docs.
Build 173 is the first build that does not support the migration from the package-based installation.
With the new versioned repository, it's still safely possible to get the migration done with a few steps.
- Install the latest instana-console version 170
- Check that you have safely migrated (log-in, check for data)
- Install the latest instana-console version 173
With this release we catched up on our SaaS releases. We plan to release further releases with uneven release numbers on-premises one week after the SaaS release and skip even releases. Resulting in a monthly update cadence.
Depending on the changes we are making with our backend, we might skip-releases or change the cadence slightly. But we will work hard to keep you uptodate.
Instana AutoProfile™ is a new continuous production profiling capability that allows you to capture profiles from your running JVM automatically. The collected profiles can be used to identify hot spot methods, problems with locked threads. For detailed information, see our Instana AutoProfile™ docs.
- Added Instana service to PCF Application mapping.
- Added a health event which triggers if the required number of PCF Application instances changes more then three times in the past five minutes.
- Instana now supports monitoring of Kafka clients (consumers/producers) which are part of Java applications. For detailed information, see our Kafka docs.
- Added aggregated values for topic metrics on the cluster level.
Instana now supports monitoring of various Nvidia Tesla, Quadro, and GeForce graphics cards. For detailed information, see our Host docs.
Configure your Humio dashboards and navigate to Instana entities directly from your logs. See more information, see our Humio docs.
- Support for Pivotal Isolation Segments.
- The instance identifier is now available for Cloud Foundry application instances. The instance identifier is displayed on the Cloud Foundry application dashboard, the Garden container dashboard sidebar, and the container infrastructure view.
Configure your ELK Instance and see a direct link to your logs from views in Instana. For configuration details, see our ELK docs.
A list of Red Hat/CentOS packages installed on host can now be extracted once a day. For more information, see our Host docs.
A custom service rule could be used only to override the default service rules. Now with the introduction of the
service.default_name tag, a custom service rule can also be used to extend service default rules with additional tags.
For example, to separate your production and test services based on the host zone, create the custom service rule using the
Instana now comes with a new landing page, which helps the user focus on key entities in various areas. The new landing page comes with four five tiles which can be reordered depending on which areas are more important.
- Applications: Shows the top 5 applications ordered by calls
- Websites: Shows the top 5 websites ordered by page views.
- Infrastructure: Based on the selected type, the infrastructure tile will show the top 5 hosts, containers or processes, ordered by CPU usage.
- Platforms: This list collects entities from various platforms like Kubernetes clusters, Cloud Foundry applications and vSphere data centers.
- Events: Shows incidents and issues that occurred in the configured time.
Our custom event system for website monitoring is now generally available after being in beta for several releases. Custom events enable reporting about non-standard activities, important interactions and custom timings to Instana. This can be especially helpful when analyzing uncaught errors (breadcrumbs), reporting information about WebSocket connections, and tracking additional performance metrics.
Complementary to our custom event system, we now automatically collect markers and measures made via the user timing API. Markers and measures are automatically translated into custom events. This means that the user timing API can be used as a vendor-neutral way to report custom events to Instana.
To determine user impact, we now use the user ID provided via the user API (preferred) or the session ID provided by opting into our session tracking. This opens up user impact insights for a much wider audience, e.g. websites that work without sign-ins and without server-side sessions.
Instana now integrates with DB2, so you can monitor performance of your DB2 instances alongside related applications, and the infrastructure that runs it all. This includes a built-in dashboard that displays key metrics about your instances’ availability, connections, query rates, and more. For more information, see the DB2 docs.
- Kubernetes 1.16 support.
- Fixed uncaught errors in the Kubernetes service dashboard on the infrastructure map.
- Fixed back button interaction in several paginated views.
- Fixed parsing traces with unexpected parent-child relations and showing a warning in the trace detail view when this appears.
- Fixed CRI-O container naming by including the namespace and pod name when running in container-orchestration system.
- Now referring to erroneous calls as "Erroneous Calls" rather than "Errors".
- Added "Erroneous Calls" metric to show the number of erroneous calls. Previously, erroneous calls were shown as "Erroneous Call Rate".
- Added vSphere tags for Datacenter, Host, VM name, and VM state.
- Added tags for GPU model and the number of GPUs running in the Host.
- Trace Sensor 1.1.18: fixed JSON detection when also using ext/memcached.
- Trace Sensor 1.1.19: fixed bug that prevented connections to Apache.
- Tracer 1.6: more fine-grained error detection on ext/memcached spans.
- Tracer 1.6: instrument delete and flush operations in ext/memcached.
- Tracer 1.6: capture connection details from .ini in ext/mysqli.
- Tracer 1.6: support getting a connection from Predis Cluster.
- UI: PHP spans now renders script names and arguments.
- Fixed overly aggressive time skew adjustments.
- Added the ability to filter for time skews.
- Added health information to the websites overview.
- Fixed cases in which the page load visualization showed overlapping events.
- Fixed that previous baseline/threshold has been still shown for a short period when setting up an alert.
- Fixed that the UI offered options to create, delete, or edit an alert even though the user lacked the respective permission.
- Aligned the behavior of the JS errors count alerting to the related chart. Now it counts every error and not the number of erroneous page-loads.
- Fixed missing root call in traces started from XHR requests.