Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upPublish exposition format as an IETF standard #1361
Comments
beorn7
added
the
enhancement
label
Feb 2, 2016
fabxc
added
kind/enhancement
and removed
enhancement
labels
Apr 28, 2016
This comment has been minimized.
This comment has been minimized.
|
We have a number of issues around the exposition format by now. How about moving them all into the docs repo, with a dedicated label? We should have clarity on the spec before starting any work, and the spec lives in the docs repo. So it might be the best point to track those issues. |
This comment has been minimized.
This comment has been minimized.
|
Sounds good to me; as soon as they are done, I can start pouring it all into the ID. Maybe the specs could even be replaced with a link to the RFC after it's been published. Just keep in mind that this sets the exposition format in stone for a certain time. |
This comment has been minimized.
This comment has been minimized.
|
Even more a reason to get clarity about changes we might want to get in. I'll go ahead and start creating issues about topics we discussed before. |
This comment has been minimized.
This comment has been minimized.
|
Moved to prometheus/docs#541 |
beorn7
closed this
Sep 9, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
SuperQ commentedFeb 1, 2016
It would be interesting/good to write up the exposition format as an IETF RFC standard. This would allow more adoption by "traditional" companies since they can reference a standard for both implementation and marketing "We support metrics via RFC XXXX".