Closed
Description
openedon Aug 28, 2024
When we use our internal monitoring architecture to measure the overall report task success rates, we see low metrics of success. The failed report tasks that come up can be categorized as failing for the following reasons:
| Reason | Example error |
|---|---|
| User authentication changes or expires before task begins | Saving execution error for csv_searchsource job aa12a744-1494-4c61-98fb-9c9b5d60ea2b: ResponseError: security_exception Root causes: security_exception: unable to authenticate with provided credentials and anonymous access is not allowed for this request |
| Data view object is deleted before task begins | Saving execution error for csv_searchsource job 95cdfa5f-c8eb-44ed-a7e9-b8c8bbccf46b: Error: Saved object [index-pattern/5193f870-d861-11e9-a311-0fa548c5f953] not found |
| Report job document is deleted before task begins | Error in finding the report from the scheduled task info! [id: df438627-34ce-4dc8-b418-563e86252c90] [index: .ds-.kibana-reporting-2024.08.19-000001] |
These reasons are caused by the rapid setup and teardown of report data during automated testing, from functional tests and API integration tests. In a test covering a CSV report, the data view, test user, or report job document may removed before the report job task is flushed.
This issue is to "clean up" the tests for reporting to avoid report task failures. This can be done by making sure we always wait for a report job to finish before removing those artifacts in a test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
