Multiple Hosts?

[Its4Nik]

Is it possible to use more then one host as a monitoring endpoint?

Like with dozzle you can add more then one host to see logs. And I would like to ask if this is also possible with monocker.

This would be a dozzle configuration for example:

dozzle:
    restart: always
    image: amir20/dozzle:latest
    labels:
      autoheal-app: true
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    container_name: dozzle
    ports:
      - 8989:8080
    environment:
      DOZZLE_ENABLE_ACTIONS: true
      DOZZLE_HOSTNAME: Fin-1
      DOZZLE_REMOTE_HOST: tcp://10.0.0.3:2375|Fin-2,tcp://10.0.0.4:2375|Fin-3
    healthcheck:
      test: ["CMD", "/dozzle", "healthcheck"]
      interval: 3s
      timeout: 30s
      retries: 5
      start_period: 30s

As you can see there are multiple Hosts at the DOZZLE_REMOTE_HOST part.

[jeffreyswiggins]

I think I inquired about this a while back so I could be running a single instance on my “main” container machine and still be able to monitor my other running containers on a few other hosts I have. I just do not want to have to beverage the resources to another app to monitor them directly if I could do it remotely like I am doing the way Dozzle is allowing.

I realize most of these containers are very low overhead but 2 or my hosts are Pi 3B+ devices running Pihole plus NextAlertX (may soon be AdGuard Home) and while having this and several other small “support” apps like WatchTower do not tax the devices, they add up and by setting them up to remotely monitor when I access them instead it just uses less resources on them.

Jeffrey Wiggins @.***

On Jun 20, 2024 at 03:29 -0500, ItsNik @.***>, wrote:

Is it possible to use more then one host as a monitoring endpoint? Like with dozzle you can add more then one host to see logs. And I would like to ask if this is also possible with monocker. This would be a dozzle configuration for example: dozzle: restart: always image: amir20/dozzle:latest labels: autoheal-app: true volumes:

• /var/run/docker.sock:/var/run/docker.sock:ro container_name: dozzle ports:
• 8989:8080 environment: DOZZLE_ENABLE_ACTIONS: true DOZZLE_HOSTNAME: Fin-1 DOZZLE_REMOTE_HOST: tcp://10.0.0.3:2375|Fin-2,tcp://10.0.0.4:2375|Fin-3 healthcheck: test: ["CMD", "/dozzle", "healthcheck"] interval: 3s timeout: 30s retries: 5 start_period: 30s As you can see there are multiple Hosts at the DOZZLE_REMOTE_HOST part. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[Its4Nik]

So thats a no? That it is not possible for now?

[petersem]

@Its4Nik it only allows one home to be defined, however you could run a second instance with a different container name and docker ip:port.

Monocker uses very low resources, so it would be low impact. I will have a look at what's involved to make it multi-server capable, but for now just run a second instance.

[Its4Nik]

@Its4Nik it only allows one home to be defined, however you could run a second instance with a different container name and docker ip:port.

Monocker uses very low resources, so it would be low impact. I will have a look at what's involved to make it multi-server capable, but for now just run a second instance.

Okay i see, because i have several cloud servers it would be nice to just have one central monitoring stack without running 3 containers for the same thing.

I am not worried about ressources but it would just make it easier for the end user.