Skip to content

fix(angular): Use ui category for span operations #4222

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

Merged
merged 2 commits into from
Dec 3, 2021

Conversation

AbhiPrasad
Copy link
Member

As per the new spec in https://develop.sentry.dev/sdk/performance/span-operations/#js-frameworks, we now want to prefix our angular spans operations with ui.

This in conjugation with the changes in getsentry/sentry#30363 will allow these ui spans to be categorized as part of operations breakdown.

@@ -224,7 +225,7 @@ export function TraceMethodDecorator(): MethodDecorator {
activeTransaction.startChild({
description: `<${target.constructor.name}>`,
endTimestamp: now,
op: `angular.${String(propertyKey)}`,
op: `${ANGULAR_OP}.${String(propertyKey)}`,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same thing as React comments, especially since we recommend low cardinality ops, we should probably only use the same exported const ops and consume them here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, but not sure how to best start considering: 1) we have 0 tests for angular (lol) and 2) this matches existing behaviour.

The propertyKey should be a set of strings though, not uuids or unique names, so I think we still fit the low cardinality aspect.

@AbhiPrasad AbhiPrasad merged commit d17f049 into master Dec 3, 2021
@AbhiPrasad AbhiPrasad deleted the abhi-ui-ops-angular branch December 3, 2021 14:07
onurtemizkan pushed a commit that referenced this pull request Dec 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants