Skip to content
FreesbeFreesbe Docsfreesbe.net

Zabbix problems aren't posting

TroubleshootingFor adminsReviewed Guides: Zabbix

Zabbix shows problems, but the channel you picked stays quiet, or the cards don’t keep up.

Nothing posts

Section titled “Nothing posts”
  • Look at Zabbix’s action log. In Reports → Action log, find the problem and the Freesbe media. Its status and error say what happened.
    • Freesbe doesn’t know this URL: the connection was deleted or turned off. Turn it on, or connect again and paste the new URL in the user’s media.
    • Put the Freesbe URL … in the user media “Send to” field: Send to is empty or holds something else.
    • A timeout or “couldn’t connect”: the Zabbix server can’t reach the internet. Set the media type’s http_proxy parameter if it goes out through a proxy.
  • No entry at all? The action didn’t run. Check the action is enabled, its conditions match the problem, and it sends to the user with the Freesbe media. Check the user’s media is enabled and its When active and Use if severity settings include the problem.
  • Check the severity. Problems below the connection’s Problems to post are left out on purpose. Open Edit from the connection’s ⋯ menu to lower it.
  • Check the user can see the host. Zabbix only sends to users who can read the host.

Cards don’t turn green, or don’t show acknowledgements

Section titled “Cards don’t turn green, or don’t show acknowledgements”

The action needs Recovery operations (for green cards) and Update operations (for acknowledgements and comments) that send to the same user. Without them, Zabbix only tells Freesbe about new problems.

The Acknowledge or Close button fails

Section titled “The Acknowledge or Close button fails”

Freesbe tells the person who pressed it what Zabbix said.

  • Zabbix didn’t accept the API token: it expired or was deleted. Make a new one in Users → API tokens and paste it in Edit.
  • Couldn’t reach Zabbix: the frontend isn’t reachable from the internet, or the address is wrong. Use the address you open Zabbix at, starting with https://.
  • This trigger doesn’t allow manual close: turn on Allow manual close on the trigger, or let Zabbix close it once it’s fixed.
  • No permissions: the token’s user needs read-write access to the host.

No buttons at all? The connection has no API token; the list says No buttons (add an API token).