SOC-3655 Zabbix API read options

[eric-eisenhart]

I'd like to explore some additional "intelligence" that reads from the Zabbix API before sending an update to Zabbix, to avoid duplicating anything...

• Skip "resolve" if Zabbix already shows problem as resolved/closed.
• Don't add "triggered" comment if that comment is already there.
• Generally don't add a comment if same comment already there?
• Don't acknowledge if already acknowledged
• Don't unack if not acked
• Don't change severity if severity already same

For any of those where we add a comment when making the change, the non-op (acking already acked, setting priority to what it is, etc) shouldn't add a comment. Or can make it configurable to add a comment...

This should help eliminate some "noise" in Zabbix, and may also help eliminate potential loops... I haven't hit any problematic loops, but they seem theoretically possible.

Sonic.com Internal reference: https://jira.noc.sonic.net/browse/SOC-3655