Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Reporting] more data on reports generated in Kibana to help identify bottlenecks and failures #24306

Closed
AlonaNadler opened this issue Oct 19, 2018 · 4 comments
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

Comments

@AlonaNadler
Copy link

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.

@AlonaNadler AlonaNadler added the (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead label Oct 19, 2018
@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@bmcconaghy bmcconaghy added Team:Reporting Services and removed Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Dec 20, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@tsullivan
Copy link
Member

Hi, I hope the customer feels that these pain points are being noticeably improved on :)

We have done a lot of troubleshooting ourselves and found a few categories of common problems, which led us to putting in a lot of logging improvements, and self-checks at startup to warn or self-correct for any known issues. I can link to specific examples if you like.

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.

This request isn't something we've considered yet. I think what will get us there is having report jobs handled in Kibana as its own type of saved object, and have all saved objects in Kibana get these capabilities. Related: #21689

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@tsullivan
Copy link
Member

Duplicate of #79793 - the first step towards providing monitoring of Reporting.

@exalate-issue-sync exalate-issue-sync bot added 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 labels May 13, 2021
@sophiec20 sophiec20 added the Feature:Reporting:Framework Reporting issues pertaining to the overall framework label Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

7 participants