Ad Widget

Collapse

Event details: Operational data {ITEM.VALUE} cut short

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • phand
    Junior Member
    • Jun 2022
    • 3

    #1

    Event details: Operational data {ITEM.VALUE} cut short

    Greetings

    Has anyone experienced Operational data in event details get cut short?

    I want the file path, date and time to show in the event details if a problem occurs ({ITEM.VALUE}, type of information is Text)

    Click image for larger version

Name:	item_value.png
Views:	448
Size:	8.0 KB
ID:	446887

    But it ends up looking like this:
    Click image for larger version

Name:	event_detailsl.png
Views:	351
Size:	5.0 KB
ID:	446888

    But the media type, teams and email have no problem showing the whole path.

    Zabbix version 5.4.6
  • koflert
    Junior Member
    • Aug 2024
    • 5

    #2
    Having the same issue. Nobody experienced that either? Or is nobody using that view?

    Comment

    • cyber
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Dec 2006
      • 4806

      #3

      Might be something to do with the case, when you have a trigger containing multiple items, then you get also multiple entries there and hovering your mouse gives you anyway a popup with a link to history...
      Maybe we are just using event details for different purpose... I just look there in case of somekind of analysis or investigation, I don't have an issue doing ctrl-click on "history" and opening it in other window...

      You can always use "operational data" field in trigger config and fill it with your required text/data (extract that needed path from item value), it may behave differently... I am too lazy right now to test it..

      Comment

      • Brambo
        Senior Member
        • Jul 2023
        • 245

        #4
        I got the same with operational data cut short but I'm not really using the operational data there. Even with mouse over the data is cut short. When I want to view it I just click history but all important triggers are usually formatted in something numeric so that always fit

        Comment

        Working...