Skip to main content

A distributed, scalable, and fault-tolerant alerting and monitoring system

Project description

LegionD

The monitoring service daemon for Legion - a distributed, scalable, and fault-tolerant alerting and monitoring system

Setup & Usage

Installation

TODO

Configuration

TODO

Usage

The key reference for using legiond is:

legiond --help

Development

Standards

  • Be excellent to each other
  • Code coverage must be at 100% for all new code, or a good reason must be provided for why a given bit of code is not covered.
    • Example of an acceptable reason: "There is a bug in the code coverage tool and it says its missing this, but its not".
    • Example of unacceptable reason: "This is just exception handling, its too annoying to cover it".
  • The code must pass the following analytics tools. Similar exceptions are allowable as in rule 2.
    • pylint --disable=C0111,W1203,R0903 --max-line-length=100 ...
    • flake8 --max-line-length=100 ...
    • mypy --ignore-missing-imports --follow-imports=skip --strict-optional ...
  • All incoming information from users, clients, and configurations should be validated.
  • All internal arguments passing should be typechecked whenever possible with typeguard.typechecked

Development Setup

Using poetry install from inside the repo directory:

poetry install

This will set up a virtualenv which you can always activate with either poetry shell or run specific commands with poetry run. All instructions below that are meant to be run in the virtualenv will be prefaced with (legiond)$

IDE Setup

Sublime Text 3

curl -sSL https://gitlab.com/-/snippets/2066312/raw/master/poetry.sublime-project.py | poetry run python

Development

Testing

All testing should be done with pytest which is installed with the dev requirements.

To run all the unit tests, execute the following from the repo directory:

(legiond)$  pytest

This should produce a coverage report in /path/to/dewey-api/htmlcov/

While developing, you can use watchexec to monitor the file system for changes and re-run the tests:

(legiond)$ watchexec -r -e py,yaml pytest

To run a specific test file:

(legiond)$ pytest tests/unit/test_cli.py

To run a specific test:

(legiond)$ pytest tests/unit/test_cli.py::test_cli_basics

For more information on testing, see the pytest.ini file as well as the documentation.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

legiond-0.1.5.tar.gz (19.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

legiond-0.1.5-py3-none-any.whl (19.9 kB view details)

Uploaded Python 3

File details

Details for the file legiond-0.1.5.tar.gz.

File metadata

  • Download URL: legiond-0.1.5.tar.gz
  • Upload date:
  • Size: 19.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.1.6 CPython/3.8.10 Linux/5.4.0-77-generic

File hashes

Hashes for legiond-0.1.5.tar.gz
Algorithm Hash digest
SHA256 6e31222a16f3b5a454792cb231ec84ae7b232ed22440f4e72229b0d8b48b6bf5
MD5 a36f8df98bc2cf67e9fff66727e7c4a8
BLAKE2b-256 a5ea80f26b87d23c8670f60cb55685e38b47142a727506f4a9e60d4374cee156

See more details on using hashes here.

File details

Details for the file legiond-0.1.5-py3-none-any.whl.

File metadata

  • Download URL: legiond-0.1.5-py3-none-any.whl
  • Upload date:
  • Size: 19.9 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.1.6 CPython/3.8.10 Linux/5.4.0-77-generic

File hashes

Hashes for legiond-0.1.5-py3-none-any.whl
Algorithm Hash digest
SHA256 0736f8418d3a2a05e3bd1f6a90e51c41d1f8009c720ea54ace6eec899be38b8c
MD5 16ef6ad081fd2f0a4dfacef6ebfaa0a6
BLAKE2b-256 ec851619891ff674ff9f89e9a4638d2a8ee4cc07092601b862e637e6fab1359b

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page