You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(stats-detectors): List transaction ops for endpoint regression (#8598)
* feat(stats-detectors): List transaction ops for endpoint regression
Since not all transactions qualify for the endpoint regression feature,
explicitly list all the transaction ops that qualify.
* Update src/docs/product/issues/issue-details/performance-issues/endpoint-regressions/index.mdx
Co-authored-by: vivianyentran <[email protected]>
---------
Co-authored-by: vivianyentran <[email protected]>
Copy file name to clipboardExpand all lines: src/docs/product/issues/issue-details/performance-issues/endpoint-regressions/index.mdx
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,15 @@ Endpoint Regression issues are a generic class of problems where the duration of
12
12
13
13
The detector for performance issues periodically checks the 95th percentile transaction duration of the most common endpoints in your project. When a significant increase in the p95 value is detected and has been sustained for some time, a regression issue is created.
14
14
15
+
To be categorized as an endpoint, the transaction operation must be one of the following:
16
+
17
+
-`function.aws`
18
+
-`function.aws.lambda`
19
+
-`http.server`
20
+
-`serverless.function`
21
+
-`asgi.server`
22
+
-`rails.request`
23
+
15
24
## Regression Evidence
16
25
17
26
To find additional info, go to the Issues page and click on the Endpoint Regression issue you're interested in. In the top section of the "Details" tab, you'll find the following:
0 commit comments