Associate arbitrary comment text for triggers

[Spectator]

Hello,

First of all, I apologize for my bad English.

Our company plans to introduce Zabbix.
Our company has many operation groups, each with its own area of operation. Eg. linux operation group, windows operation group, database operation group, etc.
Our current monitoring application is viewed 7/24 by our heldpdesk team through many monitors.
In the current monitoring application, each alarm is accompanied by a short text outlining what the helpdesk team should do when the alarm occurs (which group to notify, reach it by email during business hours, or call the specialist immediately by phone).

How can we design this under Zabbix so that alerts and their comments (action plans) are also visible on the dashboard?

They may also vary within a host, who should be notified in the event of a particular alarm.
For example, a host has a linux operating system and runs a MySQL database.
If the free space on the disk is greatly reduced, the helpdesk should notify the linux operating group (based on the text of the defined action plan).
If the number of MySQL sessions increases significantly, the helpdesk should notify the database operations group (based on the text of the defined action plan).
For simplicity, therefore, the trigger should contain the text of what the helpdesk team should do in the event of an alarm.

Do you have any ideas on how we could do this with Zabix? It would be important to be able to enter different text for each alarm. If these action plan texts might come from a template, we may need to be able to overwrite them manually for a particular host.

[Spectator]

If you add text to "Description" field in trigger config, there will be small "?" icon beside problem name in problem list. Hovering over it you can see your text.
You can also use "Operational data" field.

Thank you for your response!

I tried this before, then these were gray, inactive fields.
Today I realized that this was because I was using the factory, "Template OS Linux by Zabbix agent" template on the host where I wanted to modify the descrition field of the triggers.

When I cloned the "Template OS Linux by Zabbix agent" template under a different name, I couldn't change the trigger description field on the host where I put the cloned template.

However, I built my own template from scratch, into which I linked the same templates that are included in the factory "Template OS Linux by Zabbix agent" template, I was able to modify the description field of the triggers on the host on which this was a new template.

I think there may be some protection against modification in the factory "Template OS Linux by Zabbix agent" template.
And since I tried to edit the description fields of the triggers on the host recorded with the factory "Template OS Linux by Zabbix agent" template, I failed, so I opened this topic, which can now be closed.

Thanks again

[Spectator]

There is no such protection methods for templates.
It might be disabled, if that trigger is created by discovery. To have something there, you need to fill it in prototype. but then it will be same everywhere...
Operational data field is also disabled, if trigger comes from template/discovery. Need to edit it in template

Thanks your answer. You are absolutely right.

Do you or anyone else have an idea how I could monitor these hosts? I want to add these host to Zabbix with a linux OS template (with autodiscovery filesystems), but I want to use the trigger of some mount points with different trigger comments:

linuxhost1:
Filesystems (Triggers and trigger's comments):
/ ("Disk space is critically low" trigger's comment: "Call linux operation group by phone immediately")
/boot ("Disk space is critically low" trigger's comment: "Call linux operation group by phone immediately")
/database ("Disk space is critically low" trigger's comment: "Call database operation group by phone immediately")

linuxhost2:
Filesystems (Triggers and trigger's comments):
/ ("Disk space is critically low" trigger's comment: "Call linux operation group by phone immediately")
/boot ("Disk space is critically low" trigger's comment: "Call linux operation group by phone immediately")
/office ("Disk space is critically low" trigger's comment: "Call windows operation group by phone immediately")

linuxhost3:
Filesystems (Triggers and trigger's comments):
/ ("Disk space is critically low" trigger's comment: "Call linux operation group by phone immediately")
/boot ("Disk space is critically low" trigger's comment: "Call linux operation group by phone immediately")
/accounting ("Disk space is critically low" trigger's comment: "Call accounting operation group by phone immediately")

[cyber]

I was about to say "overrides", but those will not allow you to add descriptions/comments.. only tags and severity...
One way would be to not use discovery. Your / and /boot are there anyway, no need to discover them, you can have items ready for them in one template that will be assigned for all. Then have separate templates for /db and /office and /accounting and have somekind of autoreg rule for template adding .. maybe based metadata or something...Or maybe you have somekind of naming convention in hostnames, that allows you to trigger different rules...
This is example of things where OOB things do not meet everyones needs.. Then you have to work around things to get things working as You need...