feat: anubis metrics #127
Reference in New Issue
Block a user
Delete Branch "anubis-metrics"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
abra.sh👯
@@ -0,0 +6,4 @@ANUBIS_METRICS_ENABLED: "true"secrets:- "basic_auth"deploy:I think this might overwrite the other
anubislables?aren't they concatenated? that's my experience so far with labels!
@@ -223,2 +223,4 @@#ANUBIS_SERVE_ROBOTS_TXT=true#ANUBIS_SLOG_LEVEL=INFO#COMPOSE_FILE="$COMPOSE_FILE:compose.anubis-metrics.yml"#SECRET_BASIC_AUTH_VERSION=v1I think we now have two basic with secrets in traefik now. Is there a reason you did not reuse the existing one?
if you're refering to basic auth, that secret contains the whole usersfile:
https://git.coopcloud.tech/coop-cloud/traefik/src/branch/master/compose.basicauth.yml
OK so they are specified in a differnt way. But I would still prefer if we habe only one way to set the basicnauth for metrics. Maybe we should deprecate the old usersfile? Or if we keep both secrets the new secret should be named more specific
not sure, you can have more than one user on the usersfile. should i rename it to metrics_basic_auth?
what was the resolution @decentral1se ?
I think you can. Is there a way to also use a users file with you method of basic auth?
metrics_basic_auth sounds good and then we can make a breaking change to also use that for the traefik metrics
Btw. the traefik Middleware supports both users and usersFile https://doc.traefik.io/traefik/reference/routing-configuration/http/middlewares/basicauth/
they're different things, one is the basic auth database that traefik protects routes with, and this new secret is for protecting anubis itself.
https://anubis.techaro.lol/docs/admin/policies#http-basic-authentication
since the metrics endpoint is only available locally, not exposed by traefik (thus not protected by basicauth middleware) and authentication is optional, i could remove it altogether to simplify things.
OK, my confusion is slowly clearing up 😀
I think I have a slight preference to remove the basic auth for now. We can always add it later and prevent confusion for now
@p4u1 done, but i can't re-request review, the page reloads and the status doesn't change
Can you add a small section about the metric to the readme?
done!
@@ -0,0 +11,4 @@- "prometheus.io/scrape=true"- "prometheus.io/port=9090"- "prometheus.io/path=/metrics"- "prometheus.io/auth=basic"Is this missing the actual basic auch middleware?
no need to, this works for the alloy branch from monitoring-ng and it doesn't go through traefik
and the basic auth is set up on anubis itself
Ah right
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.