tree: 1b66b9c12c479e27d5ff60c209bf8888eccf0fbd [path history] [tgz]
  1. files/
  2. meta/
  3. tasks/
  4. templates/
  5. README.md
skolo/ansible/switchboard/roles/install_managed_prometheus/README.md

Role Name

install_managed_prometheus

Description

Builds and deploys the managed_prometheus_ansible executable. This prometheus instance will collect metrics, fire alerts, and also upload the results to Managed Prometheus so they can be queried from the skia-monitoring project.

The server uses the Google Default Application Credentials for the chrome-bot user.

Requirements

The default service account key installed for ‘chrome-bot’ must have the ability to write logs to skia-public and access the machine server Firebase database.

Arguments

managed_prometheus_ansible_version - Optional argument to select the version of managed_prometheus_ansible to install. If not set then the version recorded in the k8s-config repo will be used.

Example Playbook

- hosts: jumphosts

  roles:
    - install_managed_prometheus

Pushing a test/debug binary:

To deploy a test/debug binary to a machine first upload the CIPD package via the //skolo Makefile:

$ cd skolo
$ make build_and_upload_managed_prometheus_ansible

The logs from the build_and_upload command will contain the CIPD version for that build. Pass that version to the ansible-playbook via --extra-vars. You probably also want to only push your new configuration to a single jumphost at first, using the limit.

You will run a command like this from //skolo/ansible, as per usual with ansible playbooks.:

$ ansible-playbook ./switchboard/jumphosts.yml --limit rack2 \
  --extra-vars managed_prometheus_ansible_version_override=2021-09-19T15:36:31Z-jcgregorio-ba7510fdcda7d3979cc2c0df21fee100e3ba4075-dirty