-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
Ability to delete chat history #2355
Comments
Could be that this feature is only available for server admins. |
you can delete rooms (again - check #2351) - look: |
Thanks sampaiodiego, that is nice to know. However, it would be very nice to have the ability, as an admin, to auto expire messages. Perhaps a system-wide setting to forget messages older than a given time period. Or, perhaps to forget messages once a user logs out. Or perhaps best of all, to never keep messages on the server at all. |
Agree with this. Setting up auto-expiring channel history(like, daily, weekly) could be interesting in some cases. We are doing some integration of Rocket.Chat with Zabbix, and the channel that receives the notifications could be cleared from time to time to avoid long history and keeping daily notifications clean. Meanwhile we can delete and recreate the channel from time to time, but we have to ask to all members to refresh their browsers since it keeps some of the old channel cache showing(and blocking new messages to be sent) |
I recently installed a fresh version of Rocket.Chat and played a bit. To not need to recreate a channel everytime, there IS some need to cleanup the thread. Is it possible to just clean previous messages from some message/time? (Especially automatization-chats would benefit from this) |
With a MongoDB Query you can delete all messages in the whole db "less than" a specific date.
It is not the best solution, but in our company we had to find a workaround until the developers add some cleanup features. |
Another vote for this feature. We have a channel that logs a certain kind of exceptions from our sytems and those tend to be rather large - so the channel becomes very slow to load in short order. Currently I'm deleting and recreating the channel on a regular basis, but that's not really a "solution" |
is this something that is close to being usable the ability to remove all chat without having to remove the channel would be amazing or at least a way to clean the database... |
+1 for this feature |
+1 from me as well. |
+1 The functionality I would like is slightly different, I'd like to clear DM's on logout I could help test if needed |
+1 |
Dear +1ers, you can just click on the first post and add your thumbs-up there. :) Regarding the feature, I think it would be extremely useful to be able to choose between 1) delete permanently, or 2) archive (perhaps to S3?) then delete. |
Yes but it wouldn't keep this thread alive nearly as well :) |
As this project is pull-request friendly, maybe someone can create a PR instead of just +1-ing? I'm currently not (yet) able to develop, but I'm preparing to. Maybe I will fast enough to develop this feature (but I doubt it, because I'm not used to develop meteor-driven apps) |
Added some thumbs up per suggestions :) |
After digging around a bit, this feature seems to already exist: As far as I understood, this only is a missing button, am I correct? EDIT: there is even some permission already: |
That seems to be only for channels, right? I believe this is for deleting other stuff, as well. |
@mddvul22 looking at the sourcecode, it only is for channels:
|
It does not work for private groups which you temporarily change to public channel for a minute, just to be able to use the api - so either this functionality needs to be duplicated for private groups, or it needs to be fixed so that the workaround works |
I use the solution that that KKvin came up with but expanded upon it to clear the uploaded files that were part of the 30 day threshold as well. Not elegant but it gets the job done. Can be seen here: |
Just to cross-link: If you want retention policy rather than manual deletion, There's An Issue For That: #795 |
Dang. lol. Thanks that is much easier.
…On Sun, Mar 12, 2017 at 11:04 AM, Tim McCormack ***@***.***> wrote:
Just to cross-link: If you want retention policy rather than manual
deletion, There's An Issue For That: #795
<#795>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2355 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALQ9fwhJ3pKqJXbuEpa2029rR3IJlQU7ks5rlAmFgaJpZM4HjuX_>
.
|
any progress on this? |
just a reply for the issue in general. If we can make something in the admin panel to delete old message history. |
Based on my experience, deleting messages via REST API causes the client side to update automatically, so their is no issue with cached messages. |
@MarcosSpessatto Right now we currently have Rocket.Chat/packages/rocketchat-api/server/v1/channels.js Lines 86 to 112 in a9aea36
|
We currently have the same issue in requiring a cleanup I ended up writing a python based script very similar in logic to the php script above however as we have to delete literally millions of messages and each of those requiring a seperate api call which took around a second to complete with the python request library this was impractical. and seemed to cause a massive load over an extended period of time. I am currently rewriting in hope of changing private groups to public and using the channels.cleanhistoryyes endpoint. however this is hacky I would much prefer a rooms.cleanhistory endpoint for bulk message deletion. |
In case anyone else also needs this here is a script which can delete both public and private rooms using the api. https://github.com/HackyPenguin/rocketchat_cleanup/tree/master |
Same requirement here ... |
To second this feature, we also have that requirement not for technical but legal reasons. Background: in Germany (and probably other countries) data protection law requires to define a maximum storage time for data. That means we need a reliable way to set an expiry date (e.g. "after 5 years") on all content in all channels. Ideally there's a global setting as well as by channel settings, to allow a faster purge for automation channels. |
@rsimai not only germany, with the upcoming GDPR (General Data Protection Regulation) the whole EU is having "new" data protection laws, making the whole history-thing a bit more painful than it might have to. |
@FibreFoX "upcoming"... as in... the 25th of May 2018! As far as I understand GDPR we will have to have the ability to automatically delete messages after a specified time or upon user request. |
Is there anything new to this, or information about when it will be implemented? Did anyone automated the channel history deleting process and can share it with us? |
@eszeus There is the REST API call |
@vynmera Any Automated process would be awesome! Specially with a GUI. I am not an expert with APIs and such, sadly... |
I'm making it happen! ---> #11236 |
@vynmera that's pure awesomeness! How can I deploy it? Has it been merged to master? Don't know much about git! |
@wdimd You can clone my fork Note that it's a WIP build, don't expect everything to work correctly (or at all). I highly advise you to not use it in production :) When I update anything, you can |
Thanks @vynmera, keep rocking!!! |
@vynmera also deployable via snap installation? :D |
@eszeus I'm afraid not, it's not done yet ~ but when it is, you can start using it once it is on Rocket.Chat's snap (probably next month, at 0.67.0)! |
@vynmera so nice! Thanks! Sounds great to me :D Thank you for this work. Awesome, and neccessary xD |
Closes #6749 Closes #8321 Closes #9374 Closes #2700 Closes #2639 Closes #2355 Closes #1861 Closes #8757 Closes #7228 Closes #10870 Closes #6193 Closes #11299 Closes #11468 Closes #9317 Closes #11300 (will incorporate a fix to this PR's issue) Closes #11046 (will incorporate a fix to this PR's issue) Contributes to #5944 Contributes to #11475 _...and possibly more!_ This PR makes deleting messages (automatically and manually) a lot easier on Rocket.Chat. - [X] Implement a bulk message deletion notification, to quickly push large message deletions to users without reload - [X] Use it in `rooms.cleanHistory` - [X] Use it in user deletions - [X] Completely remove cleanChannelHistory as required by v0.67 - [X] Remove server method `cleanChannelHistory` - [X] Remove REST API `channels.cleanHistory` - [x] Implement a sidebar option to clean history - [x] Basic implementation - [x] Allow excluding pinned messages - [x] Allow attachment-only mode - [x] Allow specifying user(s) to narrow down to - [x] Also update REST API - [x] Also update docs - [x] Break the deletion into multiple different requests, so the client can keep track of progress - [x] Clear animation / progress bar for deleting - [x] Retention policy - [X] Global, set by admin - [X] Global timer that runs every second and deletes messages over the set limit - [X] Can change its timer's resolution to prevent insane CPU overhead - [X] Admin can decide what room types to target (channels, groups and/or DMs) - [X] Allow excluding pinned messages - [X] Allow attachment-only mode - [x] Per-channel, set by those with a new permission - [x] Disabled when master switch off - [x] Set in channel info - [x] Can override global policy with a switch that requires `edit-privileged-setting` - [x] Allow excluding pinned messages - [x] Allow attachment-only mode - [x] Uses same global timer for cleanup - [X] Message at start of channel history / in channel info if there is a retention policy set - [x] Message in channel info if there is a retention policy set on that channel specifically - [X] Make cleaning history also delete files (completely!) - [X] Manual purging - [X] Automatic purging - [x] Make other deletions also delete files - [x] User deletion - [X] Own messages - [x] DMs with them's partner messages - [x] Room deletion - [x] Cleanup - [x] Finish related [docs](https://github.com/RocketChat/docs/pull/815) - [x] Link to the docs in the settings Please suggest any cool changes/additions! Any support is greatly appreciated. **Breaking change:** This PR removes REST API endpoint `channels.cleanHistory` and Meteor callable `cleanChannelHistory` as per the protocol specified for them. ![bzzzzzzzz](https://user-images.githubusercontent.com/39674991/41799087-56d1dea0-7670-11e8-94c0-bc534b1f832d.png)
Your Rocket.Chat version: 0.19.0
This is not an issue per se, but more of an enhancement request if possible.
The text was updated successfully, but these errors were encountered: