Get support for soyuka/pm2-notify
If you're new to LTH, please see our FAQ for more information on what it is we do.
Support Options
Unfortunately, there are currently no active helpers for this repository on the platform. Until they become available, we reccomend the following actions:
View Open IssuesTake a look to see if anyone else has experienced the same issue as you and if they managed to solve it.
Open an IssueMake sure to read any relevant guidelines for opening issues on this repo before posting a new issue.
Sponsor directlyCheck out the page and see if there are any options to sponsor this project or it's developers directly.
soyuka/pm2-notify
How does it work?
We're listening on pm2 bus automatic events (manual exits won't be mailed). When an exit event happend we're keeping the pm2 process environnement in a queue. Those elements are then emailed through SMTP by using the famous nodemailer.
Templates can be customized, if you want to use another mailing protocol feel free to dig into the code! This is meant to be used out of the box with minimal configuration but it can't fit everyone needs.
If you need better email interactions have a look at Keymetrics!
Configuration
mail:
from: "me@example.com"
to: "you@example.com"
# see https://github.com/andris9/nodemailer-smtp-transport#usage
smtp:
host: "smtp.gmail.com"
port: 25
# Events list:
# - restart
# - delete
# - stop
# - restart overlimit
# - exit
# - start
# - online
events:
- exit
template: './template.md'
# this is the process subject if there is only one event to be mailed
subject: '<%= process.name %> errored (<%= process.NODE_ENV %>)'
# if multiple events are going to be mailed, use a global subject:
multiple_subject: 'Error on <%= hostname %>'
#wait for 5 seconds after the last event before sending an email - avoid spam when a lot of events happened
polling: 5000
#if events are sent continuously, an email will be sent after 5 minutes anyway
max_polling_time: 300000
#attach your process logs to the email
attach_logs: true
Templating
This is how a standard pm2 object looks like:
{ event: 'exit',
manually: false,
process:
{ name: 'throw',
vizion: true,
autorestart: true,
exec_mode: 'fork_mode',
exec_interpreter: 'node',
pm_exec_path: '/usr/share/nginx/www/pm2-notify/throw.js',
pm_cwd: '/usr/share/nginx/www/pm2-notify',
instances: 1,
node_args: [],
pm_out_log_path: '/home/abluchet/.pm2/logs/throw-out-0.log',
pm_err_log_path: '/home/abluchet/.pm2/logs/throw-error-0.log',
pm_pid_path: '/home/abluchet/.pm2/pids/throw-0.pid',
NODE_APP_INSTANCE: 0,
NODE_ENV: 'production',
... //your env variables here
status: 'stopped',
pm_uptime: 1434096604224,
axm_actions: [],
axm_monitor: {},
axm_options: {},
axm_dynamic: {},
vizion_running: false,
created_at: 1434096545628,
pm_id: 0,
restart_time: 19,
unstable_restarts: 0,
started_inside: false,
command:
{ locked: false,
metadata: {},
started_at: null,
finished_at: null,
error: null },
versioning: null,
exit_code: 1 },
at: 1434096607294 }
You can use all those variables in the template. We're adding the hostname
and we format at
in a date
variable by using date = new Date(at).toString()
.
Templating is done through lodash and the email should be markdown-formatted.
Testing
Mail testing is hard to automate. There is a sample throwing process in the test
directory. To test manually just launch pm2 start test/throw.js
with node index.js
.
If you have an idea to unit test this feel free to open an issue.
Our Mission
We want to make open source more sustainable. The entire platform was born from this and everything we do is in aid of this.
From the Blog
Interesting Articles
-
Generating income from open source
Jun 23 • 8 min read
-
2023 State of OSS
Apr 23 • 45 min read ★
-
A funding experiment...
Aug 19 • 10 min read
-
But You Said I could
Aug 19 • 2 min read
Thank you for checking out LiveTechHelper |
2025 © lth-dev incorporated
p-e622a1a2