Pierre Mdawar

@raymondbutcher Thank you for reviewing this proposal, well it's your call, it was just an idea to improve the syntax. About the reserved keywords, I think that they won't be...

Hi, Thank you for your suggestion, how do think these job start/end times should be exposed? The only thing that I can think of right now is exposing the job...

Actually I thought that we can calculate the duration from the start and end times of the job. As per the Prometheus documentation on [histograms and summaries](https://prometheus.io/docs/practices/histograms/#count-and-sum-of-observations): > Histograms and...

I could be wrong but I still don't think we can record this data using a histogram/summary metric accurately, also as you said this operation could get very expensive. About...

Hi, Thank you for this pull request. About your decisions, I really can't comment on these decisions as I have very little experience in this metrics/Prometheus field and this was...

I had this issue as well, here's the debug output from the exporter: ``` [DBG] ignoring server http://nats:8222: parse "http://nats:8222healthz": invalid port ":8222healthz" after host ``` A forward slash is...

@xlr-8 I'm personally no longer using the exporter, just maintaining it and I have no plans to add this feature unless we have a fully working PR with tests and...

It's also worth noting that the [`nats`](https://github.com/nats-io/natscli) CLI current `main` branch also shows the error: ``` nats: error: nats: jetstream not enabled ``` I can only get the error: ```...

> It is because the trailing “..” is an invalid subject and it causes the API subjects being used to also be invalid. > > We should probably fail for...

It seems that you don't have any workers running and there are no jobs enqueued, this is the initial state when there are no metrics to display. Take a look...