Erin Schnabel

Right.. I was going to ask why this is being specified directly (rather than relying on the dependency through the quarkus micrometer prometheus extension? This is incorrect: ``` io.quarkus quarkus-micrometer...

There are quarkus integration tests that rely on the prometheus metrics endpoint being present. I'm not sure what the setup difference is between those and this.

> in case of direct `io.micrometer:micrometer-registry-prometheus` usage in the app. Was that the issue?

https://github.com/utmapp/UTM/pull/7117 ?

You did great. This is clear. =)

So this one is tricky. I did fix it so that if the link fails to resolve, it just puts the display text in (which is what always should have...

Yep.. I don't have support for that data type yet...

A draft PR with your script (or just add it here), would be useful.

Attach here or as a draft PR ;) It will give me a better idea of what you mean and how you approached it.

> [@mfp22](https://github.com/mfp22) Just post it here. Don't hide it! > > Btw: people who want full control can simply just use reveal.js without this plugin. But it would be nice...