pilchita

Hi, thanks for the reply. Here my supervisor configuration: ``` [unix_http_server] file=/var/run/supervisor.sock chmod=0700 [supervisord] logfile=/var/log/supervisor/supervisord.log pidfile=/var/run/supervisord.pid childlogdir=/var/log/supervisor [supervisorctl] serverurl=unix:///var/run/supervisor.sock [include] files = /etc/supervisor/conf.d/*.conf /etc/supervisor/conf.d sqlp01.conf [program:sql01] directory=/opt/sql01 command=python -u sql_service.py...

@tiagocoutinho thanks for the reply. From the instance where I installed the web servers I still do not see the supervisor of the client instances. ``` [unix_http_server] file=/var/run/supervisor.sock chmod=0700 [supervisord]...

The connection to port 9002 of the instance where the rpc interface is installed from the webserver can be done correctly nc -v 10.54.130.34 9002 Connection to 10.54.130.34 9002 port...

Hello, any helps?

> Had same issue, turned out to get fixed by deleting alertmanager pod and all the values were added automatic to alertmanager.config Can you share your configuration? I deleted the...

Thanks for the clarification, I thought that the groups parametro was used on the side of alertmanager and not on prometheus, I apologize for asking something so silly.

I’m back here again. What is the correct way to update the alertmanager.yaml file? I try this: ``` alertmanagerFiles: alertmanager.yml: alertmanager: config: global: route: group_wait: 30s group_interval: 5m repeat_interval: 12h...

This is very difficult my God, I can’t find the problem. I see this: `ts=2023-05-22T00:16:24.928Z caller=coordinator.go:118 level=error component=configuration msg="Loading configuration file failed" file=/etc/alertmanager/alertmanager.yml err="yaml: unmarshal errors:\n line 3: field sigv4...