Roadmap to 1.0

Background

There was mention in the handoff discussion about the NodeJS library 'missing' things that make Prometheus, Prometheus. For the prometheus folks I'd like to have that discussion now.

On the radar for 1.0 is an improvement to metrics() #791 which is likely to amortize some of the string interpolation work over the ingest side of the data collection. That might result in a 15% decrease in collection cost. So if there are for instance discrepancies between how client_js generates the metrics output and everyone else does, that would be a convenient time to increase the complexity of the output code.

The only one I know of is OpenMetrics v 2.0. Are there other things that should go on the list, @mcolina @krajorama, @zbjornson?

Ideas for 1.0

• Progress toward OpenMetrics 2
• Content negotiation
• Reduce cost of metrics()
• Fix (dumb down?) summaries

Start by reading the metrics() improvement discussion in issue #791 and the listed ideas for OpenMetrics 2, content negotiation, collection cost, and summaries. The issue does not identify files, tests, a selected design, or concrete completion criteria, so the 1.0 roadmap needs to be scoped before implementation can begin.