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.

Sign up for GitHub

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

Jump to bottom

Monitoring of Reporting #29281

Closed
tsullivan opened this issue Jan 24, 2019 · 4 comments
Closed

Monitoring of Reporting #29281

tsullivan opened this issue Jan 24, 2019 · 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:high Addressing this issue will have a high level of impact on the quality/strength of our product. needs-team Issues missing a team label performance

Comments

@tsullivan
Copy link
Member

tsullivan commented Jan 24, 2019 •
edited
Loading

Reporting needs a way to collect internal statistics over time as a way to expose performance insights. This has multiple goals:

  1. Enable date histogram charts with metrics, which will raise understanding of how Reporting works.
  2. Allow developers to tune performance of Reporting and measure the successes.
@tsullivan tsullivan added enhancement New value added to drive a business result (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead labels Jan 24, 2019
@tsullivan tsullivan mentioned this issue Sep 27, 2019
Closed
@tsullivan tsullivan mentioned this issue Oct 7, 2019
Closed
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@tsullivan tsullivan mentioned this issue May 11, 2021
Closed
@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 impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort and removed 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
@exalate-issue-sync exalate-issue-sync bot added loe:weeks and removed loe:medium Medium Level of Effort labels Aug 11, 2021
@exalate-issue-sync exalate-issue-sync bot changed the title [Reporting/Monitoring] Monitoring of Reporting (performance & capacity metrics) Monitoring of Reporting (performance & capacity metrics) Oct 27, 2021
@exalate-issue-sync exalate-issue-sync bot changed the title Monitoring of Reporting (performance & capacity metrics) Monitoring of Reporting Oct 27, 2021
@tsullivan tsullivan mentioned this issue Nov 30, 2021
Merged
1 task
@tsullivan tsullivan mentioned this issue Jan 4, 2022
Open
@lizozom
Copy link
Contributor

lizozom commented Apr 18, 2022

Will be done as part of https://github.com/elastic/dev/issues/1443
Once we have customer deployments reporting APM stats to the overview cluster, we should be able to create monitorting and alerts around them.

@tsullivan
Copy link
Member Author

Closing this, via internal documentation

@sophiec20 sophiec20 added Feature:Reporting:Framework Reporting issues pertaining to the overall framework and removed (Deprecated) Team:Reporting Services labels 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
Assignees
No one assigned
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:high Addressing this issue will have a high level of impact on the quality/strength of our product. needs-team Issues missing a team label performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@tsullivan @lizozom @sophiec20 @elasticmachine @liza-mae @petrklapka