Suggestion: Add documentation on Collectors about prometheus-net

[sandersaares]

I have added an example of on-demand collection to the readme file that should satisfy the scenario you describe.

[sandersaares]

Absolutely, a pull request to showcase the more advanced scenarios in the readme would be quite welcome if you are still interested!

[NikokoFR]

Hello !
Do you have any update on this topic, i'm VERY interested 👍

Thanks

[sandersaares]

Do you have specific topics you would like to see more documented? Details about your needs can be very helpful.

[NikokoFR]

In Prometheus documentation we can read

"Metrics should only be pulled from the application when Prometheus scrapes them, exporters should not perform scrapes based on their own timers. That is, all scrapes should be synchronous.
Accordingly, you should not set timestamps on the metrics you expose, let Prometheus take care of that. If you think you need timestamps, then you probably need the Pushgateway instead.
If a metric is particularly expensive to retrieve, i.e. takes more than a minute, it is acceptable to cache it. This should be noted in the HELP string.
The default scrape timeout for Prometheus is 10 seconds. If your exporter can be expected to exceed this, you should explicitly call this out in your user documentation"

According to this, I'd like to avoid refreshing my metrics every n seconds. Instead, i'd like to make collection append only when Prometheus comes to retreive them. (with a http event or something similar)

Is there a sample/documentation explaining how to use the Metric Server in that way?

[NikokoFR]

Thank you!!

Now working perfectly 👍

[sandersaares]

A fair bit of documentation has been added with v2.0. I will close this issue as there do not appear to be obvious things remaining to document. If anyone has thoughts about what to document, feel free to open a pull request or issue or just comment here.