Pipeline Error Detection / Expose the keys in event object
N
Nick Wire
Have seen errors in pipeline where associated data added to an alarm configuration gets corrupted in the namespace and does not reach the pipeline.
The pipeline does not check the tag configuration of the the source tag and verify everything made it through to the event object.
You also need to know what keys yourself to be able to use them on the event object. If you print out the event object all you get are the basic keys no details about associated data at all. So if you created an associated data called "alarmGroup" on your alarm, you need to know that to reference it in the pipeline with event["alarmGroup"] because there's not way to get keys from event object in pipeline.
The pipeline also does not care if "alarmGroup" did not make it to the pipeline. If you referenced a key that doesn't exist in the event object, it will just return None with no error.
Log In
P
Paul Griffith
Any number of alarms, with any kind of configuration, can reach any arbitrary pipeline. The fundamental nature of the associated data functionality is that it's flexible, so you can never be absolutely guaranteed to have certain values.
Assuming I understand what you're asking for correctly, the best we could do is a "hint" in a given alarm pipeline about some of the possible values that were supplied in previous executions, but there's no mechanism to guarantee that they exist. We could add a new block that verifies certain keys are present, but that's nothing you can't currently do with a script block at the beginning of the pipeline.
Can you explain more about what you're looking for/the ultimate problem you're trying to solve?