Confirmed users
574
edits
Telemetry/Alerts: Difference between revisions
Add notes on the Medusa/Cerberus server.
m (Normalize heading levels) |
(Add notes on the Medusa/Cerberus server.) |
||
| Line 86: | Line 86: | ||
...except making sure you never have to respond to an Alert for this probe again, that is. File a bug in that bug's component to update the Alert'ing probe to have a valid, monitored "alert_emails" field so that the next time it misbehaves ''they'' can be the ones to explain themselves without you having to spend all this time tracking them down. | ...except making sure you never have to respond to an Alert for this probe again, that is. File a bug in that bug's component to update the Alert'ing probe to have a valid, monitored "alert_emails" field so that the next time it misbehaves ''they'' can be the ones to explain themselves without you having to spend all this time tracking them down. | ||
== Server Anatomy == | |||
Medusa and Cerberus share a server. Both services run from within /home/ubuntu. | |||
* Cerberus is a Python project run daily by /etc/cron.d/cerberus. | |||
* Medusa is a Clojure project kept running by supervisord. See /etc/supervisor/conf.d/medusa.conf. | |||
=== Deploying New Medusa Code === | |||
# Make source code changes. | |||
# Update the version on the server (in /home/ubuntu/medusa), using git. | |||
# Still in /home/ubuntu/medusa, run <code>lein cljsbuild once release</code>. | |||
# Restart the JVM. I can vouch for the efficacy of manually killing the existing server processes and letting supervisord restart them, but <code>supervisorctl restart medusa</code> is worth a try next time, as it's a bit more polite. | |||