This is meant as a discussion to follow up on #411. For those interested in getting more involved with goss, I am interested in the following:

1. Now that there is a CONTRIBUTING.md, issue/pr templates,

Hello!,

Just started working with this package and have to say is great!.

Was playing with the Supervisor class and would love to have an option specify the path where supervisorctl resides as well to be able to define where the configuration may reside.

There are some scenarios where the

Hi,
I've an installation with more than 500 hosts, and when 500 hosts is exceeded the Network Parents section explode with this error

Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/adagios/views.py", line 43, in wrapper
result = view_func(request, *args, **kwargs)
File "/usr/lib/python2.6/site-packages/adagios/status/views.py", line 109, in network_parents

Affected Version: 3.4.1
OS: Ubuntu 18.04 LTS
Python: 3.8
pip: 20.0.2

As i am trying to setup and build the project locally for #637 but i am not sure how to properly contribute.

sudo apt install python3.8-venv
python -m venv venv
source venv/bin/activate
# Fix outdated pip version in venv
# curl https://bootstrap.pypa.io/get-pip.py | python3
python setup.py insta

Reading some issue like searchlight/searchlight#235 i can guess that it's possible to deploy it in a way the checks could be running on the cluster and submit checks to a remote icinga2 host. But then :

• is this assumption true ?
• does any documentation exists about that (i didn't find any) ?
• if yes could we avoid to deploy a local icinga2 instance and postgress dat

Currently the warning and critical threshold trigger when the number of nodes is above the number set in the threshold. They should trigger when the number of nodes goes below the threshold.

# ./check_rabbitmq_cluster -w 2,2 -c 1,1
RABBITMQ_CLUSTER CRITICAL - nb_running_node CRITICAL (3) nb_running_disc_node CRITICAL (3), nb_running_ram_node OK (0)
# ./check_rabbitmq_cluster -w 4,4 -c 

🗣️ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

👻 Brief Description

Chef have released updated cookstyle rules, we should therefore run the auto fix against the cookbook

1. Ensure you are on the latest stable chef-workstation
2. Run cookstyle -a

Issu

API calls should be sorted alphabetically for easier searches.

See example:

• Application.setSleepTime(seconds)
• Application.getRegion()
• Application.getRegionForWindow(windowNumber)
• Application.getName()

Issue Summary
When I run https://github.com/alerta/alerta-contrib/tree/master/integrations/mailer#deployment I see the following logs. Unfortunately, I have no idea at which point the authentication is failing: amqp, api, smtp? As for the 403 error, I have manually validated that my key works by running Client(...) in the Python REPL.

I have no files in alerta.rules.d.

alerta@44029

Tried to install from Bintray following the docs in http://docs.alignak.net/en/latest/02_installation/01_system.html, I met this error :

-----
Alignak post-install
User account: alignak
Installation prefix: /usr/local
-----
Detecting OS platform
-> system is: Linux
-> found linux
Checking / creating 'alignak' user and users group
User alignak still exists
Detecting Python version

It would be easyier if you can copy the Service Templates

here

and if you can input changes in the following site (/servicetemplates/edit/id of new service)

As discussed in #32 and merged in #33, we need to explain / amplify the documentation surrounding --element_regex_global and the new functionality of --element. cc @Project0

The top level README.md on the infrastructure repository is somewhat out of date with respect to our backup setups and policy for the infrastructure systems (jenkins, api, blog, monitoring etc.)

We should get the documentation up to date, while ensuring that all appropriate backups are definitely in place and running.

Hi

Just a suggestion.
For beginner, "okconfig addtemplate" is confusing.

According to folloiwng, it's action is to apply a existing template onto a host.

okconfig addtemplate <host_name> --template oracle

addtemplate should reserved for adding a new template not existed in /usr/share/okconfig/templates dir.

Existing "okconfig addtemplate" should be "okconfig applytemplate