Just some background here (in case it's missed when we'll review this RFE) : actually the rpm signing is automated but when there are some massive tagging (like several dozens or hundreds of pkgs, like for a new openstack/rdo release), SIG don't know if signing is stuck somewhere or why pkgs aren't appearing on mirror network signed in the next minutes.

While they can see action through distRepo task for their tag (that means that signing happened and repository is being composed and then pushed out) it would be good to have simple way to know signing status (either irc bot, or mqtt topic, or else, to be discussed).
So nothing blocking for now but just small enhancement for better feedback

[backlog refinement]
It's still relevant, we don't just have capacity to work on it right now.

[backlog refinement]
It's still relevant, we don't just have capacity to work on it right now.

[backlog refinement]
We can use grafana to show the metrics publicly. This will allow us to share the metrics without allowing people to query everything.

status update : as I had to update that code recently, I'll just plumb some mqtt notifications in .stg. env to see if that works fine and then push it live (and document it on sig guide)

It was tested in .stg. env and working fine so merged that staging branch and applied on prod.
The simple way to follow signing queue/process is to just follow now documented step : https://sigs.centos.org/guide/delivery/#following-signingpush-process-status
Closing that (old) RFE ticket

PS: I'll also eventually add a grafana dashboard for this but this simple process is enough for people to know the current signing status and ticket can now be closed with implemented mqtt function