[ZBXNEXT-4919] Edit description and Tags in Discovered Items/Triggers Created: 2018 Dec 17 Updated: 2023 Sep 12 |
|
| Status: | Confirmed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F), Server (S), Templates (T) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Trivial |
| Reporter: | Michael P | Assignee: | Zabbix Development Team |
| Resolution: | Unresolved | Votes: | 8 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
I'd like to update Descriptions and Tags for my discovered Triggers.
Real live Example: Trigger: Windows service discovery: Service "MSExchangeNotificationsBroker" (Microsoft Exchange Notifications Broker) is {ITEM.LASTVALUE3} (startup type {ITEM.LASTVALUE1}) But this service is really just running for about 30 seconds, and then not running ever agin (according to our exchange admins) So we decided to disable this trigger. But for documentation purpose I'd like to add a Node/Description to the Item/Trigger in order to keep track of our decicion why we disabled this. And in addition to this, may be add (or remove?) Tags to a Trigger for changing action behavior.
PS: The same goes for VMware discovered hosts and adding them into additional host groups. |
| Comments |
| Comment by Markus Hornyik [ 2020 Feb 19 ] |
|
Would be essential for VMWARE monitoring... |
| Comment by Nikolay P [ 2021 Jan 16 ] |
|
Another use case would be if a host has many network interfaces. The LLD graph prototype will create the graphs named (an example):
Traffic on eth0 Traffic on eth1 Traffic on eth2 etc.
It would be extremely useful to be able to configure the discovered items and add a description or a custom macros to make better description for the graphs:
Traffic on eth0 (sales) Traffic on eth1 (management) Traffic on eth2 (support) etc.
|
| Comment by Matt Alvis [ 2023 Jan 13 ] |
|
We are going through an initiative to tag Triggers appropriately for routing and correlation in other systems. Using a single Trigger Prototype to capture processes that may be unrelated (think Systemd Services) is difficult because a single Tag cannot be applied to all discovered triggers, as they impact different systems/services in the network. |