Skip to content
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

RUM-7643 Correctly handle TTNS when resource was stopped with error #2444

Conversation

mariusc83
Copy link
Member

What does this PR do?

Currently if a resource was stopped with an error we are computing the TTNS metric no matter if the error event was persisted or not. To align with the the approach we took for the normal resource stop we will have to make sure that the TTNS metric will only be computed when the error event was persisted.

Motivation

What inspired you to submit this pull request?

Additional Notes

Anything else we should know when reviewing?

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Make sure you discussed the feature or bugfix with the maintaining team in an Issue
  • Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

@mariusc83 mariusc83 self-assigned this Dec 10, 2024
@mariusc83 mariusc83 force-pushed the mconstantin/rum-7643/fix-ttns-computation-when-resource-stopped-with-error branch from b3b77fb to 7efc6d9 Compare December 10, 2024 09:27
@mariusc83 mariusc83 marked this pull request as ready for review December 10, 2024 09:42
@mariusc83 mariusc83 requested review from a team as code owners December 10, 2024 09:42
@mariusc83 mariusc83 merged commit 2103445 into feature/view-loading-times Dec 10, 2024
25 checks passed
@mariusc83 mariusc83 deleted the mconstantin/rum-7643/fix-ttns-computation-when-resource-stopped-with-error branch December 10, 2024 10:33
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