Skip to content

Commit ce0d5d8

Browse files
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]>
1 parent 93dce4b commit ce0d5d8

File tree

1 file changed

+9
-0
lines changed
  • src/docs/product/issues/issue-details/performance-issues/endpoint-regressions

1 file changed

+9
-0
lines changed

src/docs/product/issues/issue-details/performance-issues/endpoint-regressions/index.mdx

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,15 @@ Endpoint Regression issues are a generic class of problems where the duration of
1212

1313
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.
1414

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+
1524
## Regression Evidence
1625

1726
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

Comments
 (0)