Ad Widget

Collapse

Custom Expression in Actions not working

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • RyanPrice
    Junior Member
    • Jan 2023
    • 4

    #1

    Custom Expression in Actions not working

    Hello,

    I have an action that alerts on a bunch of triggers for a specific group of servers. I want to exclude a specific trigger on 3 servers. The custom expression in the action is not operating properly. Screenshot below with the FQDNs of the hosts blacked out.

    This action is still firing for all triggers identified in A, B, and C.

    I have tried multiple iterations of 'Trigger does not equal' and 'Trigger name does not contain ...' (Trigger name does not contain Blacklisted, for example)

    I am on Zabbix 5.0.28


    Click image for larger version

Name:	image.png
Views:	609
Size:	42.7 KB
ID:	456999

    I have seen a few other similar issues posted without resolutions. Anyone have any thoughts?

    Thanks in advance.
    Ryan​
  • tomijs
    Junior Member
    • Jan 2023
    • 7

    #2
    Everything seems to check out, the solution might be that you need to clear any existing problems, and perform a configuration cache reload by entering `zabbix_server -R config_cache_reload`.

    Comment

    • RyanPrice
      Junior Member
      • Jan 2023
      • 4

      #3
      Thanks for the reply, I tried the cache reload and we are still seeing the same issue.

      Any other thoughts?

      Comment

      • Markku
        Senior Member
        Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
        • Sep 2018
        • 1781

        #4
        I have seen a few other similar issues posted without resolutions.
        Try to configure a minimal reproduceable setup and open an issue in https://support.zabbix.com, that's the usual way to get something fixed. I see 5.0 LTS is still in full support until May 31st.

        Markku

        Comment

        • Markku
          Senior Member
          Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
          • Sep 2018
          • 1781

          #5
          As a workaround, try adding some specific (same) tag to each of those three triggers and then use a "tag not x" condition. Maybe it works with only one negated condition. (Just an idea)

          Markku

          Comment

          • RyanPrice
            Junior Member
            • Jan 2023
            • 4

            #6
            Thanks for the ideas, unfortunately that workaround also sees the same issues. I have scheduled an update to 6.2 and will set up a lab to try and recreate this if that doesn't solve it.

            Comment

            Working...