Skip to content
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

Representing State in Values #147

Open
hwinkel opened this issue Feb 22, 2016 · 1 comment
Open

Representing State in Values #147

hwinkel opened this issue Feb 22, 2016 · 1 comment

Comments

@hwinkel
Copy link

hwinkel commented Feb 22, 2016

Whats the best way to representing a given state of a managed object? In example in SNMP you have
Integers representing a given state on an interface:

ifOperStatus
INTEGER
Value   Label/Meaning
1   up
2   down
3   testing
4   unknown
5   dormant
6   notPresent
7   lowerLayerDown

http://www.net-snmp.org/docs/mibs/interfaces.html

should we use an exometer_function or (ab)use a gauge for that?

further, can a exometer_function represent any datatype or only numerical values?

@uwiger
Copy link
Member

uwiger commented Feb 24, 2016

Have you looked at exometer_report_snmp?

Regarding metric values, exometer is a bit ambivalent. Basically, metric values can be of any type, but some metric types, e.g. histograms, require inputs to be numeric, but will simply discard update values that are non-numeric. The thinking behind that is that metric update operations should never crash the caller, but also, a single 'bad' update should not be allowed to crash the histogram.

The exometer_function module makes no assumptions about the return value, but function metrics can be very useful for transforming the values of other metrics ...

... or at least it could be. I tried to make a simple example, but found a number of things I'd like to fix. Thus the delay in responding. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants