Troubleshooting
Problem
The release of the following .NET components (and higher) will modify the behaviour of the .NET rewriter...
- .NET Core Sensor 1.0.90
- CLR Sensor 1.1.148
- .NET / .NET Core Tracer 1.315.1
- .NET Framework Tracer 1.315.1
This will result in the restriction of instrumentation at the profiler/rewriter level to only work with compatible libraries that follow supported runtimes and supported versions as per our public release documentation
It is highly recommended to upgrade your runtimes or library versions as per our release notes.
- Monitoring .NET Framework-based applications - IBM Documentation
- Monitoring .NET and .NET Core based applications - IBM Documentation
If the version used by the application is not listed as supported, the rewriter will not attempt to instrument (rewrite) that library.
Cause
Some customers may currently be using library versions that are not officially supported, or they may be using patch versions that are not explicitly listed in our supported versions documentation. In previous versions this might still have worked, but with this update instrumentation may no longer occur.
Resolving The Problem
To avoid unexpected interruption to Instana monitoring, we recommend to check that you are running supported libraries / runtime versions. If not, please upgrade to a supported version
In the case where it is not possible to perform an immediate upgrade, the following workaround can be employed
Workaround Steps
(1) Please find the instrumentation.json file from instrumentation path such as the one below for .NET Framework.
C:\Program Files\Instana\instana-agent\data\repo\com\instana\clr-managed-libs\1.315.1\clr-managed-libs-1.315.1\instrumentation.json
(2) You can find the supported Runtimes and supported Versions for each library that we support within the JSON file, modify these for altering the restrictions.
C:\Program Files\Instana\instana-agent\data\repo\com\instana\clr-managed-libs\1.315.1\clr-managed-libs-1.315.1\instrumentation.json
(2) You can find the supported Runtimes and supported Versions for each library that we support within the JSON file, modify these for altering the restrictions.
- If you know the exact version or a range of versions that were successfully instrumented previously for a library, add them to the respective sections within the JSON file.
Note: If you don't know the exact version(s), you can set it as "all" for temporarily allowing all versions of runtimes or library versions. This should be changed to the supported versions as per our public documentation as soon as possible to prevent future instrumentation failures.
We have the following options in both Supported Runtimes and Supported Versions that allow the instrumentation of the library.
We have the following options in both Supported Runtimes and Supported Versions that allow the instrumentation of the library.
- Specifying the exact runtime/version : "5.0.0"
- Specifying a range of runtimes/versions : "5.0.0 - 7.8.0"
- Allowing all runtimes/versions (all keyword) : "all"
If this workaround does not restore instrumentation, please reach out to Instana Support via a case so we can review and assist.
If this workaround does not restore instrumentation, please reach out to Instana Support via a case so we can review and assist.
Related Information
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSE1JP5","label":"IBM Instana Observability"},"ARM Category":[{"code":"a8m3p000000UoUBAA0","label":"Sensors - Setup \u0026 Discovery"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0.281;1.0.282;1.0.283;1.0.284;1.0.285;1.0.286;1.0.287;1.0.288;1.0.289;1.0.290;1.0.291;1.0.292;1.0.293;1.0.294;1.0.295;1.0.296;1.0.297;1.0.298;1.0.299;1.0.300;1.0.301;1.0.302;1.0.303;1.0.304;1.0.305;1.0.306;1.0.307;1.0.308;1.0.309;1.0.310;1.0.311;1.0.312;1.0.313;1.0.314;1.0.315;1.0.316"}]
Was this topic helpful?
Document Information
Modified date:
13 March 2026
UID
ibm17263408