Maintenance

Config changes without restarting services

Making changes to the configuration during runtime is possible since they are mounted read-only from the host inside the container.

Prometheus

Sending SIGHUP to the running process will trigger a configuration reload,

docker kill -s HUP project_usage_global_prometheus_1

HAProxy

Again SIGHUP is your signal of choice

docker kill -s HUP project_usage_prometheus_proxy_1

Adding a new site

Adding a new site/location to the monitoring setup is as simple as adding three lines to your prometheus.yml specified by your PROMETHEUS_FILE_PATH set in your .portal.env.

    static_configs:
      # [...]
      - targets: ['<URL_OF_THE_SITE_PROXY>']
        labels:
          location: <UNIQUE_NAME_OF_SITE>
          location_id: <Id of the resource of the location/facility inside perun>

Afterwards trigger a reload of the config file as described above.