APM Server version 7.9

edit

APM Server version 7.9

edit

View commits

Known Issue: APM Server introduced support for cloud metadata in v7.9 (3729). Unfortunately, the JSON Schema was too strict, and does not account for null values. As a result, sending null values for cloud metadata causes the payload to be rejected. This issue was resolved in v7.10.0 (4142). To avoid problems, we recommend updating to version ≥7.10.0.

APM Server version 7.9.3

edit

View commits

Bug fixes

edit

Ensure custom index names are lowercased 4295, 4322

APM Server version 7.9.2

edit

View commits

Bug fixes

edit

De-dot metadata labels set from process and resource tags to prevent indexing errors 4193

APM Server version 7.9.1

edit

View commits

Bug fixes

edit

Honour output.elasticsearch.headers configuration in API Key auth and source mapping 4090

APM Server version 7.9.0

edit

View commits

Bug fixes

edit

Ensure unique names in dynamic templates for fields 3832
Process user_agent and client.ip for RUM Intake v3 requests 3943

Added

edit

Support configurable response headers for the RUM endpoints 3820
Support custom ILM index suffix 3826, 3905
Jaeger traceIds/spanIds are formatted without leading zeros 3849
Index Page URL and referer as ECS fields 3857
Map the Jaeger attribute message_bus.destination to the Elastic APM type messaging 3884
Added user_agent.name to grouping key for page-load transaction metrics 3886
Map the Jaeger attribute peer.service to span.destination.service.name 3897
Add timeseries.instance to transaction.duration.histogram docs 3904
Uses instrumentation config and APM tracer from libbeat, deprecating apm-server.instrumentation 3836
Scale Jaeger transaction counts by inverse sampling rate in histogram metrics 3722
Use peer.hostname for destination.address if peer.address is not given on Jaeger span 3969
Upgrade Go to 1.14.4 3961
Use peer.address for destinationService.Resource if peer.address is not given on Jaeger span 3975

« APM Server version 7.10 APM Server version 7.8 »