Richard Hartmann

Numeric ordering for devices names

4

https://github.com/ytti/oxidized/issues/34 The webinterface's ordering seems wrong: ``` sw1.foo sw10.bar sw11.quux sw2.quuux ``` Wheras it should be ordered like so: ``` sw1.foo sw2.quuux sw10.bar sw11.quux ```

Expose log file via web UI

6

This could be as simple as offering a page that loads the log file in full and displays it via www. If the web UI is the preferred way to...

Tested with commit a4486c236a3bf15192d0500b3a1892f7465826c7 I had the following in my config: ` { key = "meta-�"; id = "change_window"; data = "30"; },` as hex: ```` 000049c0: 2232 3922 3b20...

Support `auth` alongside target & module as distinct property

4

auth is orthogonal from the target, the data model and from what data to receive. As such, it will be split out into its own section. For backwards compatibility, inline...

Should we allow multiple modules per target?

5

This is an ongoing discussion between @SuperQ and I; input very much appreciated. Pro: * Less config bloat * Allows for modular configs, which might be nice for modular chassis...

Support `config.d`

10

We should allow a directory from which we build the configuration. Open questions / debate: * Allow it by default? Gut is no. Require `--config.directory = 'foo'`. * Allow more...

Implement out-of-bounds verification & error handling when accessing OIDs not retrieved before

15

I had this in my config ``` walk: - 1.3.6.1.4.1.9.9.13.1.3.1_.3_ metrics: - name: ciscoEnvMonTemperatureStatusValue oid: 1.3.6.1.4.1.9.9.13.1.3.1.3 indexes: - labelname: measuring_point type: Integer32 lookups: - labels: [measuring_point] labelname: measuring_point oid: 1.3.6.1.4.1.9.9.13.1.3.1.2...

[Discussion] Transmitting wrong data vs failing/filtering within the exporter, and how to make this bearable for the user

5

We are having recurring issues with devices sending garbage data which violates SNMP specs. Also, we should offer users a way to work around issues as it's often not realistic...