[Reporting] more data on reports generated in Kibana to help identify bottlenecks and failures #24306
Labels
(Deprecated) Feature:Reporting
Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead
enhancement
New value added to drive a business result
Feature:Reporting:Framework
Reporting issues pertaining to the overall framework
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:small
Small Level of Effort
needs-team
Issues missing a team label
Requested by a customer who uses reporting extensively,
Currently, they have a difficult time to understand how long the report processing tooka and how many reports failed.
In addition in a per report aspect, they will like to be able to tell who is the user who submitted the job, which Kibana instance generated the job, and/or IP address/hostname (for report generation requested through Watcher). This information will help admins pin-point where requests for reporting are coming from.
we had a lot of trouble understanding from the limited log messages, what was happening with reporting. It would be better if we didn't need to dig into the logs and could simply view success/failure counts and processing latency to understand if there are any issues/bottlenecks with reporting.
The text was updated successfully, but these errors were encountered: