Ad Widget

Collapse

How does fired trigger comes to problems table

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • salad
    Junior Member
    • Sep 2022
    • 2

    #1

    How does fired trigger comes to problems table

    After failure, had to restore zabbix server v. 4.0.34 configuration (on mysql db).

    SCHEMAONLY was restored for these tables:
    acknowledges
    alerts
    auditlog
    auditlog_details
    history
    history_log
    history_str
    history_str_sync
    history_sync
    history_text
    history_uint
    history_uint_sync
    item_rtdata
    problem
    problem_tag
    task
    task_acknowledge
    task_check_now
    task_close_problem
    task_remote_command
    task_remote_command_result
    trends
    trends_uint​

    Other tables restored completely.

    I faced the issue that pre-fail Problems are missing in problems table and web interface.
    There are many Triggers in PROBLEM state, but those don't show up/come to Problems table.
    Enabling/disabling Trigger, Host does not solve the issue.
    Found workaround: clone(recreate) triggers or whole hosts, but for about 300 hosts with 11K items and 5K triggers it does not look as a good alternative.

    Is there a way to force Triggers to be (mass) reprocessed and Problems recreated?
    Or maybe there is some kind of mark in zabbix table(s) that the Trigger is already "mentioned" in Problems? (Then such a mention might be deleted in my case).
Working...