-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[APM] Critical path for a single trace #143735
Merged
Merged
Changes from 11 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
120c5e0
[APM] Critical path for a single trace
dgieselaar 22baeb1
Merge branch 'main' of github.com:elastic/kibana into critical-path-p…
dgieselaar 8c28f3c
Merge branch 'main' of github.com:elastic/kibana into critical-path-p…
dgieselaar 96ea7da
Add tech preview badge
dgieselaar 0b61ad1
Merge branch 'main' of github.com:elastic/kibana into critical-path-p…
dgieselaar aaae194
Update synthtrace tests
dgieselaar d01ede8
Merge branch 'main' of github.com:elastic/kibana into critical-path-p…
dgieselaar 1c91019
Add new setting to mapping
dgieselaar cded11e
Merge branch 'main' of github.com:elastic/kibana into critical-path-p…
dgieselaar 7fb95b8
Make sure timestamp.us is set for error events as well
dgieselaar 3d1787d
Merge branch 'main' into critical-path-preview
dgieselaar 0e6919e
Merge branch 'main' of github.com:elastic/kibana into critical-path-p…
dgieselaar 06dd608
Merge branch 'main' of github.com:elastic/kibana into critical-path-p…
dgieselaar cb4d9b5
Merge branch 'critical-path-preview' of github.com:dgieselaar/kibana …
dgieselaar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,17 +20,18 @@ export class Service extends Entity<ApmFields> { | |
} | ||
} | ||
|
||
export function service({ | ||
name, | ||
environment, | ||
agentName, | ||
}: { | ||
name: string; | ||
environment: string; | ||
agentName: string; | ||
}) { | ||
export function service(name: string, environment: string, agentName: string): Service; | ||
|
||
export function service(options: { name: string; environment: string; agentName: string }): Service; | ||
|
||
export function service( | ||
...args: [{ name: string; environment: string; agentName: string }] | [string, string, string] | ||
) { | ||
const [serviceName, environment, agentName] = | ||
args.length === 1 ? [args[0].name, args[0].environment, args[0].agentName] : args; | ||
Comment on lines
+23
to
+31
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Doesn't this overcomplicate this a bit? Is it really necessary? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See comment above. |
||
|
||
return new Service({ | ||
'service.name': name, | ||
'service.name': serviceName, | ||
'service.environment': environment, | ||
'agent.name': agentName, | ||
}); | ||
|
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks very weird, why is it needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's basically method overloading, but in one signature. I think span(spanName) is often good enough and more concise than span({ spanName: ... }). I previously discussed this with @sqren when he changed it, and IIRC(?) we decided I would add back the original method when I would have time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree it makes the signature simpler but I'd rather be without the extra complexity in synthtrace. But I don't feel strongly for it either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I'll take that back. I don't think the signature improved except for
transaction()
with a single arg.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the signature is more complicated but not less easy to use, which is my goal. Like you know, I disagree about span({...}) and transaction({...}) being the better interface. I do we think should add more defaults for span() though, IMHO span(spanName) is good enough too, we can default to custom/custom for span type and subtype.