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

Automated Alerting #8246

Closed
Pete987 opened this issue Jul 20, 2020 · 1 comment
Closed

Automated Alerting #8246

Pete987 opened this issue Jul 20, 2020 · 1 comment

Comments

@Pete987
Copy link

Pete987 commented Jul 20, 2020

Hi all, I would like to just get community confirmation of the following

  1. There is no way to get an Automated Report emailed to me weekly of any Unaccepted Assets? It seems that someone has to manually generate this report. If so, is this true for ALL reports in the Reports link? We ask specifically for the Overdue Audits Report and the Unaccepted Assets Report.

  2. Can someone explain to the the process of Automating backups of SnipeIT? I can see how to run backups manually, how can I run an automated backup?
    Many thanks everyone

@snipe
Copy link
Owner

snipe commented Jul 20, 2020

You have to set up the alerts using cron or scheduled tasks. This is in the documentation.

https://snipe-it.readme.io/docs/configuring-alerts-backups
https://snipe-it.readme.io/docs/email-alerts

Snipe-IT Documentation
Starting from Snipe-IT v3.0, all automated tasks are handled via the scheduler. To set a cron job to run every minute to ping the scheduler:The scheduler already knows how often it should trigger the individual tasks, because of this code in the Console Kernel:So basically, the scheduler will figure...
Snipe-IT Documentation
Snipe-IT comes with several email alert options which can be run manually via command line, or more typically on a cron job (Linux) or scheduled task (IIS). Most of these settings are managed in Settings > Notifications, however self-hosted users will need to set up a cron job to trigger the aler...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants