Menu
▾
▴
#9 Template exceptions sorted misleadingly
According to the TEMPLATES documentation, the "exceptions" are applied in a specific order: ignore, only, alarm, noalarm. But many of the templates list alarm before ignore, which implies a different specific order or random processing. If one has read the documentation ("So if you have a primary alias that matches both an 'ignore' and an 'alarm' exception, no alarm will be generated (in fact, the row wont even be displayed in the repeater table)."), it can be somewhat jarring.
The templates' exceptions files should be revised to be in the documented order, as reminder/reinforcement for the documentation. Some of the cisco serial exceptions (e.g. 2801, 2900, 2950, 2970, 6506) seem to be in the correct order, but they're arguably more like Easter Eggs than correct. Additionally, the USING and using.html documents should be revised to conform to the documented order instead of only/ignore/alarm on/no alarm. Additionally, perhaps the paragraph that follows the exception types in USING and using.html should be appended with a
Alternatively, if the TEMPLATES documentation is wrong, the documentation should be corrected.
I can create patches if that would help.
I probably won't look at fixing this myself for 0.3.1, which I would like to release soon, but if you supply a patch I can take a look.