/prometheus-formula

Manage a Prometheus installation

Primary LanguageSaltStackOtherNOASSERTION

prometheus-formula

Formula to manage Prometheus on GNU/Linux and MacOS.

Travis CI Build Status Semantic Release

See the full SaltStack Formulas installation and usage instructions. If you are interested in writing or contributing to formulas, please pay attention to the Writing Formula Section. If you want to use this formula, please pay attention to the FORMULA file and/or git tag, which contains the currently released version. This formula is versioned according to Semantic Versioning. See Formula Versioning Section for more details.

None.

Commit message formatting is significant!!

Please see How to contribute for more details.

Meta-state (This is a state that includes other states).

This installs from prometheus solution.

This state will install prometheus components on MacOS and GNU/Linux from archive.

This state will install prometheus client libraries on MacOS and GNU/Linux from archive.

This state will install prometheus component packages from GNU/Linux.

This state will apply prometheus service configuration (files).

This state will start prometheus component services.

This state will apply prometheus exporters configuration.

This state will remove prometheus exporters configuration.

This state will stop prometheus component services.

This state will remove prometheus service configuration (files).

This state will uninstall prometheus component packages from GNU/Linux.

This state will uninstall prometheus client libraries.

This state will remove prometheus component archive (directories).

Linux testing is done with kitchen-salt.

Requirements

  • Ruby
  • Docker
$ gem install bundler
$ bundle install
$ bin/kitchen test [platform]

Where [platform] is the platform name defined in kitchen.yml, e.g. debian-9-2019-2-py3.

bin/kitchen converge

Creates the docker instance and runs the prometheus main state, ready for testing.

bin/kitchen verify

Runs the inspec tests on the actual instance.

bin/kitchen destroy

Removes the docker instance.

bin/kitchen test

Runs all of the stages above in one go: i.e. destroy + converge + verify + destroy.

bin/kitchen login

Gives you SSH access to the instance for manual testing.