Progress status about swarmprom HOT 18 CLOSED

It's almost ready, please take it for a spin and let me know if everything works.

Thanks

from swarmprom.

Sure will test.
Can you share what you mean by almost :-p

from swarmprom.

Let's use a tag here:

  cadvisor:
    image: google/cadvisor:v0.27.1

from swarmprom.

I want to use Docker configs more and reduce the number of custom images I have to build, publish and maintain.

from swarmprom.

If I use a fix version for cAdvisor I have to update this repo very often and I don't have time for that. This is just a starter kit, it's up to the user to fork it and have fix versions on everything.

from swarmprom.

Make sense!

from swarmprom.

At the moment my challenge is that caddy is messing with my traefik container (reverse-proxy).
Port 80, 433 seems to be published from caddy. I don't understand why.

The effect of this makes traefik goes does.

from swarmprom.

If you inspect Caddy do you see the port 80 mapping?

from swarmprom.

Continuing to play with swarmprom along traefik service...

What I did is to add those ports to the caddy service. It's not elegant but at least it's not messing with traefik.

  caddy:
    image: stefanprodan/caddy
    ports:
      - "3000:3000"
      - "9090:9090"
      - "9093:9093"
      - "9094:9094"
      - "9080:80"
      - "9443:443"

Gist here.

Now the issue is that it messed with the basic auth. The password I set is not working. But if I use admin as a password, it is working. I'm confused :-/

from swarmprom.

As expected, it's not showing up

If you inspect Caddy do you see the port 80 mapping?

root@CODA05:~/deploy-setup# docker inspect mon_caddy | grep 80
root@CODA05:~/deploy-setup# docker inspect mon_caddy | grep 9094
                        "TargetPort": 9094,
                        "PublishedPort": 9094,
                        "TargetPort": 9094,
                        "PublishedPort": 9094,
                    "TargetPort": 9094,
                    "PublishedPort": 9094,
root@CODA05:~/deploy-setup#

If you are curious, this is the stack I'm running for Traefik.

from swarmprom.

Wondering if I launching swarmprom before traefik could solve this. I'll let you know.

from swarmprom.

Are you running the Prom stack and the Traefik one on the same overlay network? If you want to scrape your services you can only add the Prometheus service to your app networks.

from swarmprom.

I’ve removed the ports 80/443 from the Caddy dockerfile. Can you please try the new image

from swarmprom.

Are you running the Prom stack and the Traefik one on the same overlay network?

Yes, and now that you mention it, it's not a good idea. Thanks for the input!

from swarmprom.

So far it's solid!

I would re-introduce the host dashboard, even if it contains many info from the swarm node dashboard.

I'll do a PR regarding the cpu and memory limits.

from swarmprom.

All services have memory reservations and limits. As for CPU I don't want to add those as it depends on what hardware are you running and how big is your setup.

from swarmprom.

LGTM

from swarmprom.

Thanks

from swarmprom.