Telemetry alerting system
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
ansible Configure aws region. Nov 23, 2015
doc
resources
src Actually point to the right URL for instructions Jul 24, 2018
test/medusa Combine the 2 bounding-buildids tests, since `testing` makes both ass… Sep 21, 2017
.gitignore Add a smoke test for find-date-buildid. Sep 19, 2017
LICENSE Change over to MPLv2 Sep 20, 2017
README.md Add deployment instructions to README.md Sep 11, 2018
Vagrantfile
ansible.cfg
project.clj Add changeset link to alerts. Jul 6, 2015

README.md

Medusa

Medusa (also known as Telemetry Alerts) is a tracking, alerting, and visualization service for regressions in Telemetry. It aims to provide a unified frontend for managing regression alerts.

Medusa does not perform detection of regressions by itself; it exposes an API that detectors - services that detect regressions - can post to. For example, Cerberus is a detector for histogram regressions.

Some examples of Cerberus, an automatic histogram regression detector.

Medusa is written in Clojure/Clojurescript, and uses Ring with React/Om for the web interface.

Development and deployment

First, make sure you have Vagrant and Ansible.

To start hacking on your local machine:

vagrant up
vagrant ssh

To provision resources and deploy medusa on AWS, first edit ansible/provision.yml, replacing the vaue of key_name with your own key, then:

ansible-playbook ansible/provision.yml -i ansible/inventory

To run tests, run lein test.

To deploy changes on production:

git pull --ff-only ...
sudo lein cljsbuild once release
sudo supervisorctl
supervisor> restart medusa

Usage

To launch the server simply yield lein run. Note that you must have a recent version of leiningen installed (> 2); some distributions ship with earlier versions.