Related issues:
ApplicationInsights v3.x uses OpenTelemetry under the hood. OpenTelemetry instruments
Node.js core modules (http, https, etc.) by monkey-patching them at require() time.
| /** | |
| * Workaround for https://github.com/Azure/azure-sdk-for-js/issues/33975 | |
| * | |
| * Problem: | |
| * @azure/monitor-opentelemetry's internal Logger class unconditionally | |
| * takes over both the OpenTelemetry diagnostic logger (via diag.setLogger()) | |
| * and the Azure SDK logger (via AzureLogger.log = ...) when it initializes. | |
| * The Logger class is not exported, and initialization is non-deterministic | |
| * (lazy singleton on first internal use), making it hard to override. | |
| * |
Related issues:
ApplicationInsights v3.x uses OpenTelemetry under the hood. OpenTelemetry instruments
Node.js core modules (http, https, etc.) by monkey-patching them at require() time.
Workaround for microsoft/ApplicationInsights-node.js#1411.
Node.js v16.9+ supports Error.cause for chaining exceptions, but the Application Insights
Node.js SDK only captures the top-level error. The TelemetryExceptionData.exceptions array
always contains a single entry even though the schema supports chains via id/outerId.
| KeyError at /path/ | |
| 1445170200 | |
| Request Method: GET | |
| Request URL: http://localhost/path/?end=42.3881952%2C-72.5233084452446&format=json&start=42.3950825%2C-72.5269116&threshold=1 | |
| Django Version: 2.2.7 | |
| Python Executable: /usr/local/bin/python3 | |
| Python Version: 3.8.0 | |
| Python Path: ['/app', '/usr/local/lib/python38.zip', '/usr/local/lib/python3.8', '/usr/local/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/site-packages'] | |
| Server time: Sun, 8 Dec 2019 04:54:33 +0000 |