-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Comments
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 |
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" |
Original comment by @louisong: i have another customer LINK REDACTED asking for this as well. |
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. |
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
In Kibana, reports are stored under the default index and the pattern is following by .reporting-<yyyy.mm.dd> format. |
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:
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. |
Duplicate of #26725 |
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.
The text was updated successfully, but these errors were encountered: