Is it possible to reset a baseline to be undefined once it has been set?
We were using the baseline here as a filter for the Evertz NATX protocol, and we'd set the Baseline for rows we wanted to monitor and not set it for rows we didn't want to monitor. However, once we've set a row we realized that we could not revert it to be empty again.
I know that filters and conditions are the preferred way to do this, but we were just wondering if this was something that is possible to do?
UPDATE:
For our use case we have several ports on a switch, some of which are expected to be "Up" and some "Down". Since there is no simple filter or condition we can use to divide them, we're using the Baseline to make it simple to filter which is which.
An issue has happened where we have some ports that are occasionally used and we don't need them to be monitored (Otherwise we are getting alarms every time they go up and down that are not useful and just create noise in the system). Previously we would just not set a baseline on these rows and they would be omitted from alarming. But now that the configuration has changed there are some rows we previously marked for alarming that we'd like to remove, but we can't simply delete the baseline.
Hi Nick,
I am Matthias from the client Cube team.
It's not possible to reset a baseline value which is of parameter type Discrete, because all possible valid values are stored within the dropdown.
I'm not the protocol expert, but hear me out, I have a proposal that should work out..
I would suggest to either create an addiitonal Discrete value OR an Exception value on the parameter such as "N/A" or "Disabled". Then you can put the baseline on that value.
Example in protocol for Exception value:
Then you can put it on that new value:
What do you think of the suggestion? Could this work out for you?
Looking forward to your positive response
Based on Matthias' answer (Thanks for taking the time to respond), it sounds like this is not a feature. So I've opened a feature request, for anyone else who is interested in this feature feel free to upvote it:
Add an option to delete or reset a baseline value from discrete alarm templates – DataMiner Dojo
This wouldn't work for us, I'll add more screenshots above to describe how we use it. But basically we set up alarms for both "Up" & "Down" states, then set the baseline value on each channel to either "Up" or "Down," or we omit a baseline to not alarm on that specific channel.
But I think if we can't remove a baseline then we'll just have to make many rows of filters, or duplicate the element and start from scratch.