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

Add ability to delete historical reports #17926

Closed
elasticmachine opened this issue Feb 10, 2017 · 8 comments
Closed

Add ability to delete historical reports #17926

elasticmachine opened this issue Feb 10, 2017 · 8 comments
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Feature:Reporting:Framework Reporting issues pertaining to the overall framework needs-team Issues missing a team label release_note:enhancement

Comments

@elasticmachine
Copy link
Contributor

Original comment by @w33ble:

Need to add another control to allow users to remove their historical reports.

The functionality should be limited to the owner of a given report in the UI.

@elasticmachine
Copy link
Contributor Author

Original comment by @epixa:

I think we can ship this in 5.1, or at least it certainly isn't a blocker for 5.0. If we were to mark any part of that discussion as a blocker, it should be the messaging/filtering from LINK REDACTED

@elasticmachine
Copy link
Contributor Author

Original comment by @mellieA:

Is this still in the works? I don't see anyone assigned to this one, but we regularly get the question about "How to delete old reports"

@elasticmachine
Copy link
Contributor Author

Original comment by @louisong:

i have another customer LINK REDACTED asking for this as well.

@elasticmachine elasticmachine added :Sharing (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead release_note:enhancement labels Apr 24, 2018
@timroes timroes added Team:Visualizations Visualization editors, elastic-charts and infrastructure and removed :Sharing labels Sep 13, 2018
@timroes timroes added Team:Stack Services and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jul 18, 2019
@epixa
Copy link
Contributor

epixa commented Sep 19, 2019

A way to delete individual reports would still make sense, but it's worth pointing out that index lifecycle management is a great tool to support automatic pruning of reporting indices on the basis of age.

@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 Author

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

@YashMangla
Copy link

YashMangla commented Jan 8, 2020

In Kibana, reports are stored under the default index and the pattern is following by .reporting-<yyyy.mm.dd> format.
One can delete reports from kibana followed by below command
DELETE .reporting-<yyyy.mm.dd>
eg.
DELETE .reporting-2019.12.01

@tsullivan
Copy link
Member

Hi @YashMangla be careful not to delete reporting indices while Kibana is running.

When the index is deleted, it takes it mapping away with it, because there isn't an index template for the Reporting indices. That will cause problems if today's Reporting index is deleted, because ES will automatically create it with the default mappings if more reports come in.

The safest way to delete Reports from ES directly is:

POST /.reporting-<yyyy.mm.dd>/_delete_by_query
{ "query": { "match_all": {} } }

That deletes the documents, but not the index completely, making the mappings still correct for the index. That's the safe thing to do if you need to delete recent reports.

@tsullivan
Copy link
Member

Duplicate of #26725

@tsullivan tsullivan marked this as a duplicate of #26725 Mar 13, 2020
@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 Feature:Reporting:Framework Reporting issues pertaining to the overall framework needs-team Issues missing a team label release_note:enhancement
Projects
None yet
Development

No branches or pull requests

7 participants