PipoCanaja

> Maybe should split the enum to `SensorClass` and `SensorUnit` Other question : Should we make the Unit "overridable" ? Like default value is the current one, but it becomes...

Hi @ciroiriarte rule and rule_id are 2 different variables, containing 2 different values : ``` [rule] => %macros.device_down = "1" [rule_id] => 1 [name] => Devices up/down ``` `rule` is...

> OHHHHH, rule is the legacy rule. For almost all recently created rules the rule definition is in the builder field, hence why the rule field is empty. > >...

Hi @ciroiriarte You can probably close this PR now. The rule is now properly filled both with legacy and modern rules. Bye

Hi @Bierchermuesli Coud you regenerate tests for other Infinera Groove variants ? Thx

Hi @sina-4 Could you by chance sort the license/CLA point out ? Thanx

Hi @sina-4 Seems that the Contributor License Agreement is not signed yet. According to the CLA test : **akabli** seems not to be a GitHub user. You need a GitHub...

Agreed, it's indeed hard to read, but I think the point is that YAML is better than PHP specific code OR Custom MIB. So if one wants to monitor these...

> you shouldn't use a colin like that as it is already used for other things I also thought of `str2num($index)` which would lead to `{{ str2num($index) }}` in the...

> That makes it look like you can run functions inside {{}}, which we don't want to indicate. > > `str_index_as_numeric` ? Why not. I prefered the look of the...