Releases: NovatecConsulting/boomerang-opentelemetry-plugin
0.48.0-5
0.48.0-4
Change default config of trace exporter:
exporter: {
maxQueueSize: 200,
maxExportBatchSize: 100,
scheduledDelayMillis: 5000,
exportTimeoutMillis: 30000
}
0.48.0-3
Re-include prototype patch for OTLPExporterBrowserBase
Additionally, there is a new property version
, to check the current plugin version.
You can use it like this: BOOMR.plugins.OpenTelemetry.version
0.48.0-2
Add new OpenTelemetry-plugin (browser-detector), which includes browser attributes into spans.
0.48.0-1
Updates all dependencies
--> BREAKING CHANGES:
Instead of the @opentelemetry/exporter-collector, the plugin now uses the @opentelemetry/exporter-trace-otlp-http. This exporter uses another format for the exported proto data. Thus, your previous APIs, which received the proto data, may not work properly after this update.
If you are using the inspectIT EUM-Server, because of this change, you need to use at least the version 2.6.0
--> MORE INFORMATION:
The prototype patch of version 0.25.0-3 was temporarily removed and was re-included at version 0.48.0-3
0.25.0-9
Add new global instrumentation configuration
Add new request parameter instrumentation
Fix serviceName bug from last release
- The global_instrumentation property can be used to add new instrumentations to the existing OpenTelemetry-plugins in the future
- The requestParameter property adds existing request parameter to the particular spans and beacons
- The excludeKeysFromBeacons property contains a list with parameter keys, which should not be added to beacons, for example due to cardinality concerns. However, request parameter will always be added to spans.
0.25.0-8
Add new DocumentLoadInstrumentation with new properties recordTransaction and exporterDelay.
Add new function startNewTransaction()
- With recordTransaction enabled, the DocumentLoadInstrumentation will create and hold the DocumentLoad span open until the transaction ends or startNewTransaction() will be called. Additionally, the instrumentation will try to read a trace context in the W3C-format from the Server-Timing-Response-Header. If a trace context was found, it will be used to create the DocumentLoadSpan.
- To guarantee, that the OpenTelemetry-Exporter exports the transaction span, a exporterDelay has to be specified. The delay is specified in milliseconds
- The startNewTransaction(spanName: string)-function ends the current transaction span und starts a new one. It receives a string as parameter, which will be used as the name for the new transaction span.
0.25.0-7
Add new addVarToSpans()-function to include tags in each span during and after the function call
0.25.0-6
- Add option to set all configurations for the integrated OpenTelemetry plugins.
Version 0.25.0-5
- Option for defining the context propagation header format