feat: support cross-linking synthetics & apm#595
Open
vigneshshanmugam wants to merge 4 commits into
Open
Conversation
💔 Build Failed
Expand to view the summary
Build stats
Steps errors
Expand to view the steps failures
|
sorenlouv
reviewed
Jan 10, 2023
4 tasks
|
+1 |
Contributor
|
@vigneshshanmugam is there a plan to revisit this? |
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix [Proposal] Crosslinking Synthetics with APM #265
Relies on the properties being injected from the Heartbeat side to make it work seamless.
Adds support for crosslinking the Synthetics Waterfall information with the APM data to be able to understand the performance monitoring data across Elastic observability solutions. The key fields that are added to make the transition easier are
synthetics.monitor.id- monitor id of the synthetics monitorsyntheitcs.monitor.type- type of the synthetics monitor, can bebrowser or httpsynthetics.trace.id- checkgroup/exec id that denotes execution of a journey at any pointsynthetics.monitor.location- location id where the monitor was run fromtracestate: es=s:1- Sampling decision is propagated via tracestate header which is understood by APM agentsAdds the relevant headers only for the routes/urls that are configured via the
apm.traceUrls. Sampling decision can also be propagated viaapm.sampleRate. These options can be modified via CLI or Synthetics config file.