Error Analysis: expose serviceName in list responses
Author: feelformCreated Aug 26, 2026Updated Aug 26, 2026
The exceptiontrace storage stores serviceName per row and every Error Analysis query filters by it, but the response views (ExceptionDetailView) do not expose the field. Rows returned by /api/errors/errorList therefore cannot say which service they belong to, and the error detail view falls back to the screen's service when opening a row (#14187).
Expose serviceName in the response views so consumers pass the row's own service through, the same way errorKey does for call tree rows.
Tasks:
- Add
serviceNametoExceptionDetailViewand the mapper's selected columns - Add
serviceNameto the frontendErrorAnalysisErrorList.ErrorDatatype and pass it to the detail query - Make
ErrorAnalysisTransactionInfo.Parameters.serviceNamerequired (missing values default to DEFAULT) and drop the screen-service fallback in the detail fetcher
Starting points:
exceptiontrace/exceptiontrace-web/.../view/ExceptionDetailView.javaexceptiontrace/exceptiontrace-web/src/main/resources/exceptiontrace/mapper/ExceptionMetadataMapper.xml— selected columnsweb-frontend/.../constants/types/ErrorAnalysisErrorList.ts,ErrorAnalysisErrorDetailFetcher.tsx— the screen-service fallback this removes in practice
Source: pinpoint-apm/pinpoint