Alex Nordlund

Note, if you've setup with the current version of the helm chart you're going to have to adjust the `username` to match your current one (postgres iirc)

major-wise it should be on the same level as after #18941, but all of this is coming because I missed changing one thing in `values.yaml` back then. I don't think...

Did anyone create any dashboards? I'm looking at adding the exporter to the helm chart

This is my mapping config so far: ```yaml mappings: - match: "Mastodon.*.sidekiq.queues.*.*" name: "Mastodon_sidekiq_queues_${3}" labels: environment: "$1" queue: "$2" - match: "Mastodon\\.(\\w+)\\.(.*)" match_type: regex name: "Mastodon_${2}" labels: environment: "$1" ```...

For scaling that's an awesome idea, but I still want the metrics :-) and I want to give fancy scaling a go, like scaling up sidekiq if all the queues...

If you want to validate my changes so far here's a branch with my latest changes: https://github.com/deepy/mastodon/tree/statsd-prom-exporter I'm going to force-push updates to it as I go though

From having tried to piece together the statsd metrics into sensible prometheus ones I'm fully with you there. Especially in the area around the controllers which gets very messy very...

@winsmith I think the best way to test this is by merging https://github.com/mastodon/mastodon/pull/19678 into your local checkout since the current state of postgres is... well, not quite broken not quite...

That sounds about right to me. If I refreshed often enough the full and correct page would eventually load but you'd get a notice about streaming hitting a 502 most...

Because of these changes the upgrade may fail with the following error: ```Error: UPGRADE FAILED: cannot patch "mastodon-sidekiq"``` If you want an easy upgrade and you're comfortable with some downtime...