Feature Request: Expose build error details via /api/v2/builds endpoint
Summary: dsonam has expressed concerns regarding the Sisense API endpoint /api/v2/builds, which they are using to monitor ElastiCube build outcomes. While the endpoint effectively tracks basic build task status, it lacks detailed information on failures; it only provides a status of 'Failed' without any error message or reason. Critical error details are available only via the Sisense UI and not through the API. Therefore, dsonam requests that error messages or categories be included in the API response for meaningful monitoring and alerting.
We're using the /api/v2/builds endpoint to track ElastiCube build outcomes (successes, failures, retries). The endpoint works well for tracking basic build task status, but we are running into severe limitations regarding failure visibility.
Currently, when the build fails, the API response only returns a status of [Failed] with no accompanying error message or failure reason. The actual error detail is visible in the Sisense UI under the cube's build history, but there is no way to retrieve it through the REST API.
Request:Â Expose the build error message or error category as fields in the GET /api/v2/builds and GET /api/v2/builds{buildId} response objects. Even a brief top-level error summary would be sufficient to make monitoring and alerting useful. This would benefit any team building operational dashboards and alerting scripts around Sisense build reliability, making automated monitoring truly actionable.
Â
Edward James
·4 months agoStrongly support this request. Having Access to build error details through the api would make automated monitoring and alerting for more effective, eliminating the need to manually check the ui whenever a builds fails.