hmdhk

Results 57 issues of hmdhk

Since we have started working on api version 3, planned to be used in agent version 6.0, we should identify if there are any other changes we want to make...

breaking change

Currently the user-interaction transaction names include the tag and (if exists) the `name` attribute of the element. However, in some use-cases these might not be enough to identify the element...

enhancement

* In the first phase we should make sure the agent works properly within a web worker by adding test for custom transactions. * We should investigate if we should...

enhancement

related: https://github.com/elastic/elasticsearch/issues/54110 TODO: - [ ] We should discuss limiting the configuration of session to only `session.id` (although setting timestamp and sequence is useful too) - [x] Add E2E -...

enhancement
breaking change

For users that use a CDN to load the rum agent it is more convenient to configure the agent with the same script tag as the one that loads the...

enhancement

As part of the issue to [propagate the sampling rate](https://github.com/elastic/apm-agent-rum-js/issues/845), we need to remove the context for unsampled transactions. However this needs to be considered a breaking change.

breaking change

* [Provide integration with external authentication systems for the RUM endpoint](https://github.com/elastic/apm-server/issues/1718) * Provide the ability to modify the http request that the agent sends to the APM server, for example...

We decided to [add a feature flag for propagating tracestate to avoid a breaking](https://github.com/elastic/apm-agent-rum-js/issues/845), however since the APM functionality depends on this header we need to propagate this by default....

breaking change
Cross Agents

In some case in our code we don't set all of the trace context information (`sampled`, `parentId`, `traceId`) on spans (e.g. on resource timings). Although we fix the payload we...

enhancement