Discovered Issues Header:
The buttons behave as a 'radio button' (single select)
The top issues should be filtered by the issues filters above as well as the global (env/service) filters
All: Show All Issues
Critical: Show only issues with criticality (over 0.6)
Active: Show all active issues (except fixed)
Regression: Show all issues with regression status
Fixed: Show all issues with fixed status
Show a list of issues with the indicated data. The list is ALWAYS sorted by criticality
Issues to include (no endpoint issues):
Span N+1
Excessive API Calls
Span bottleneck
Span scaling issue
Span query optimization suggested
It should also include the following endpoint issues:
high number of queries
Open session in view
There are two links in this widget, a link to the 'affected endpoint' and an 'open' link.
affected endpoint should open the issues tab of the endpoint asset.
open should open the issues tab of the asset (for example, the query causing the m+1)
See motivation in #886 Backend API issue: #https://github.com/digma-ai/digma-collector-backend/issues/2159 https://www.figma.com/design/LWTvpodwOga7qiRmGwPCcj/Digma-Website?node-id=1112-4293&t=u7HK5ExazIePwuXJ-4
Discovered Issues Header: The buttons behave as a 'radio button' (single select)
The top issues should be filtered by the issues filters above as well as the global (env/service) filters All: Show All Issues Critical: Show only issues with criticality (over 0.6) Active: Show all active issues (except fixed) Regression: Show all issues with regression status Fixed: Show all issues with fixed status
Show a list of issues with the indicated data. The list is ALWAYS sorted by criticality
Issues to include (no endpoint issues): Span N+1 Excessive API Calls Span bottleneck Span scaling issue Span query optimization suggested
It should also include the following endpoint issues: high number of queries Open session in view
There are two links in this widget, a link to the 'affected endpoint' and an 'open' link.
affected endpointshould open the issues tab of the endpoint asset.openshould open the issues tab of the asset (for example, the query causing the m+1)The list should include pagination