Labels

The following is the list of labels we use the descriptions. The basic structure is taken from the Prometheus project: https://github.com/prometheus/prometheus/wiki/Label-Names-and-Descriptions but some labels are added/deleted.

LABEL NAME	Meaning
COMPONENT LABELS
component/api.	Related to the provided API
component/write	Related to writing data.
component/read	Related to reading data.
KIND LABELS
kind/bug	A confirmed bug in Prometheus.
kind/cleanup	For refactorings, removing old config/flag, etc.
kind/testing	Testing changes
kind/documentation	For missing/old docs.
kind/enhancement	For feature requests.
kind/more-info-needed	When we require info from author, for reproducing the bug, etc.
kind/question	For questions related to usage/best practices. Best asked in mailing-list.
PRIORITY LABELS
priority/Sev0	Critical, will trigger a new patch release
priority/Sev1	Crash, next patch release
priority/Sev2	Broken, next minor release
priority/Sev3	Nice to have but no timeline
Misc. Labels
help-wanted	We really want this feature but don't have the time to do it. Will accept/mentor contributions.
wont-fix	Issues/Feature requests that are anti-patterns or out of scope..