-
Incident report
-
Resolution: Unresolved
-
Trivial
-
None
-
2.4.2
-
None
I'm unable to re-import/update a template where triggers for different severities have the same name but chaged status
For example this was imported as a new template and passed
<triggers>
<trigger>
<expression>{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].max(#3)}=0 |{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].nodata(3600)}=1</expression>
<name>Port 8080 is not listening or no data</name>
<url>https://wiki.allegrogroup.com/display/ITO/Port+%7B%24TCP_LISTENING_PORT_1%7D+is+not+listening</url>
<status>1</status>
<priority>5</priority>
<description>{"name": "net.tcp.listen.disaster", "description": "call onduty"}</description>
<type>0</type>
<dependencies/>
</trigger>
<trigger>
<expression>{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].max(#3)}=0 |{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].nodata(3600)}=1</expression>
<name>Port 8080 is not listening or no data</name>
<url>https://wiki.allegrogroup.com/display/ITO/Port+%7B%24TCP_LISTENING_PORT_1%7D+is+not+listening</url>
<status>1</status>
<priority>4</priority>
<description>{"name": "net.tcp.listen.high", "description": null}</description>
<type>0</type>
<dependencies/>
</trigger>
<trigger>
<expression>{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].max(#3)}=0 |{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].nodata(3600)}=1</expression>
<name>Port 8080 is not listening or no data</name>
<url>https://wiki.allegrogroup.com/display/ITO/Port+%7B%24TCP_LISTENING_PORT_1%7D+is+not+listening</url>
<status>1</status>
<priority>3</priority>
<description>{"name": "net.tcp.listen.average", "description": null}</description>
<type>0</type>
<dependencies/>
</trigger>
<trigger>
<expression>{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].max(#3)}=0 |{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].nodata(3600)}=1</expression>
<name>Port 8080 is not listening or no data</name>
<url>https://wiki.allegrogroup.com/display/ITO/Port+%7B%24TCP_LISTENING_PORT_1%7D+is+not+listening</url>
<status>1</status>
<priority>2</priority>
<description>{"name": "net.tcp.listen.warning", "description": null}</description>
<type>0</type>
<dependencies/>
</trigger>
<trigger>
<expression>{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].max(#3)}=0 |{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].nodata(3600)}=1</expression>
<name>Port 8080 is not listening or no data</name>
<url>https://wiki.allegrogroup.com/display/ITO/Port+%7B%24TCP_LISTENING_PORT_1%7D+is+not+listening</url>
<status>0</status>
<priority>1</priority>
<description>{"name": "net.tcp.listen.information", "description": null}</description>
<type>0</type>
<dependencies/>
</trigger>
</triggers>
then we changed the status in the last trigger
<triggers>
<trigger>
<expression>{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].max(#3)}=0 |{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].nodata(3600)}=1</expression>
<name>Port 8080 is not listening or no data</name>
<url>https://wiki.allegrogroup.com/display/ITO/Port+%7B%24TCP_LISTENING_PORT_1%7D+is+not+listening</url>
<status>1</status>
<priority>5</priority>
<description>{"name": "net.tcp.listen.disaster", "description": "call onduty"}</description>
<type>0</type>
<dependencies/>
</trigger>
<trigger>
<expression>{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].max(#3)}=0 |{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].nodata(3600)}=1</expression>
<name>Port 8080 is not listening or no data</name>
<url>https://wiki.allegrogroup.com/display/ITO/Port+%7B%24TCP_LISTENING_PORT_1%7D+is+not+listening</url>
<status>1</status>
<priority>4</priority>
<description>{"name": "net.tcp.listen.high", "description": null}</description>
<type>0</type>
<dependencies/>
</trigger>
<trigger>
<expression>{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].max(#3)}=0 |{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].nodata(3600)}=1</expression>
<name>Port 8080 is not listening or no data</name>
<url>https://wiki.allegrogroup.com/display/ITO/Port+%7B%24TCP_LISTENING_PORT_1%7D+is+not+listening</url>
<status>1</status>
<priority>3</priority>
<description>{"name": "net.tcp.listen.average", "description": null}</description>
<type>0</type>
<dependencies/>
</trigger>
<trigger>
<expression>{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].max(#3)}=0 |{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].nodata(3600)}=1</expression>
<name>Port 8080 is not listening or no data</name>
<url>https://wiki.allegrogroup.com/display/ITO/Port+%7B%24TCP_LISTENING_PORT_1%7D+is+not+listening</url>
<status>1</status>
<priority>2</priority>
<description>{"name": "net.tcp.listen.warning", "description": null}</description>
<type>0</type>
<dependencies/>
</trigger>
<trigger>
<expression>{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].max(#3)}=0 |{OS.Linux.Listening.port__759__1668:net.tcp.listen[8080].nodata(3600)}=1</expression>
<name>Port 8080 is not listening or no data</name>
<url>https://wiki.allegrogroup.com/display/ITO/Port+%7B%24TCP_LISTENING_PORT_1%7D+is+not+listening</url>
<status>1</status>
<priority>1</priority>
<description>{"name": "net.tcp.listen.information", "description": null}</description>
<type>0</type>
<dependencies/>
</trigger>
</triggers>
Zabbix reports:
Updated: Item "TCP listening on 8080" on "OS.Linux.Listening.port_759_1668".
Trigger "Port 8080 is not listening or no data" already exists on "OS.Linux.Listening.port_759_1668".
Of course creating a trigger manually with the same name works.
Tested on 2.2.4 and 2.4.2 both via UI and API
- duplicates
-
ZBX-16134 Duplicate triggers can be imported from XML
-
- Closed
-