Two actions to fix:

The nginx configuration doesn't seem the same for the Docker container and the development site:

Checking the RabbitMQ Monitoring with Prometheus guide:

• we're OK for cluster name
• to get sensible values for rate() in Grafana, we need to configure Prometheus to scrape RabbitMQ every 15s ; according Prometheus configuration, the value scrape_interval can be set at job level

Grafana dashboard was full N/A.

It's now available on bash by default, but still missing for zsh.

The port now depends of ImageMagick 7. ImageMagick provides compatibility commands:

Next step: nginx configuration inside the container

DNS change

Some context about this staging repository:

[Moved to T1620]

This is still needed for acme.sh if we want to provision different *.nasqueron.org certificates on different servers.

The problem is somewhat fixed by two things:

That's an issue for Chrome to report upstream.

Are we going to keep the rSTAGING repository?

Prometheus is available, regardless of the initial goal to offer a service mesh on Kubernetes.

Dashboard: https://grafana.nasqueron.org/d/Kn5xm-gZk/rabbitmq-overview?orgId=1&refresh=15s

RabbitMQ exporters have been added to NetBox under the tag observability -> https://netbox.nasqueron.org/ipam/services/?tag=observability 🔒

Pending container redeployment with D3374, we can reach metrics set in D3373 with socat:

Independently of the 2020 plan for a service mesh, we're going to deploy Prometheus right now to gain observability on currently deployed services.

T169 / D3168 seems to work

Subtask removed to simplify the graph. It's the task where db-B-001 has been created and so solved this one.

Alkane will now PULL files from Jenkins, instead of Jenkins pushing to the relevant server.

Resolved by db-B-001 deployment: MySQL server doesn't have a public IP anymore

In T1627#23666, @dereckson wrote:

Perhaps replace references here too: https://code.nasqueron.org/?q=equatower&i=nope&literal=nope&files=&excludeFiles=&repos=