Improvements to the Grafana LGTM dashboards - part 2

[alesj]

These 3 items from this issue: #43599

• Increase the scraper frequency

• In devmode, increase default output rate so data shows quicker on the dashboards

• Only activate the scraper if the Prometheus registry is present.

[github-actions]

🎊 PR Preview 392dbf0 has been successfully built and deployed to https://quarkus-pr-main-45747-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[brunobat]

@alesj, when I only have the opentelemetry extension, I continue to see the scraper calling /q/metrics.
That call must only be active it the micrometer prometheus registry is a dependency of the project,

[brunobat]

I think the machine is so resource constrained that the scraper hasn't started to work by the end of the test.
The only way to make sure is to get logs from the scraper.

[brunobat]

I think you deleted my test tweaks when you push forced, @alesj

[alesj]

Ah … true … sorry … can you put them back?

…

On Fri, 31 Jan 2025 at 11:25, Bruno Baptista ***@***.***> wrote: I think you deleted my test tweaks when you push forced, @alesj <https://github.com/alesj> — Reply to this email directly, view it on GitHub <#45747 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACRA6GBHX7BVJ7IBVKO7K32NNFRRAVCNFSM6AAAAABVSNG2Y2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRWHA3DCNRTGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[alesj]

I think the machine is so resource constrained that the scraper hasn't started to work by the end of the test. The only way to make sure is to get logs from the scraper.

How can it be so resource constrained?
Or how come the scraper doesn't start if the Prometheus says it started ... Prometheus is up and running

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit dd2b104.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit dd2b104.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[brunobat]

The test is disabled. @alesj will create an issue to fix it on the CI.
It works on local machines and we really need this asap.
Do not backport.
CC @gsmet