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.
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.
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.
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.
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.