-
Notifications
You must be signed in to change notification settings - Fork 1.2k
types.db(5): Improve wording and document conventions. #3458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
src/types.db.pod
Outdated
|
||
I<min> and I<max> define the range of valid values this data source. Either or | ||
both may be unbounded, which is specified by providing C<U> instead of a | ||
number. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Optional] Should we add "The type of the min and max values corresponds to the value type (double for GAUGE, int64 for DERIVE and COUNTER)"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, for DERIVE
and COUNTER
, min and max refer to the rate, not the raw value. Added a note about this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks Igor! |
I just wanted to document that data source names must be unique within a data set (see prometheus/collectd_exporter#78) and ended up rewording most of the manpage.
ChangeLog: types.db(5): Documentation of metric definitions has been improved.