Ad Widget

Collapse

Using arguments in trappers to separate monitoring data

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Nishyda
    Junior Member
    • Apr 2023
    • 1

    #1

    Using arguments in trappers to separate monitoring data

    Hi!
    I've just finished creating a containerized application for the purpose of pinging domains that I own, and checking their SSL certificates. To do so, the data is sent using the sender format, and using it without any custom parameters works like a charm.

    The problem is, there's several hundreds of websites that will be monitored using this application; And there's no way creating 5 trappers per website would be efficient nor easy to work with. As such, I thought it would be possible to use custom parameters, for example: certStatus[website]
    However, this syntax doesn't seem to work, neither does certStatus[{$website}] nor certStatus[*]. Every time, the request is successfully received, but not processed. ( Verbose output: answer [{"response":"success","info":"processed: 0; failed: 1; total: 1; seconds spent: 0.000018"}] )

    Am I misunderstanding how arguments are supposed to work? If so, is there any way to separate the data from the sender per website, without creating many trappers?

    Thank you in advance for any help you could provide.
    Nishyda​
  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4806

    #2
    With trapper you are sending value to specific item, meaning it must exist. So yes, you need those 5 items per website, if you want to send data to all of them.
    If you have hundreds of websites, as you say, you should look for a way to create all those items based on discovery. Pulling a list from file or from a webpage or .. something. And create all the items from prototypes.

    Comment

    Working...