Ad Widget

Collapse

Zabbix script item HTTP API, data gets truncated but does lld can read all of it?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • galvcom
    Junior Member
    • May 2024
    • 13

    #1

    Zabbix script item HTTP API, data gets truncated but does lld can read all of it?

    From here https://www.zabbix.com/documentation...xt-data-limits I understood the limits of the text that can be stored in the database, but my question is:

    - if the json is bigger than the database limit, do the lld rules read all the data or only the truncated data? Actually my minified json is 94 250 characters long, but some elements are not stored.

    I don't know if this matters, but just for debugging options I have set the history storage period to 1h. If anyone has any advice, I will appreciate it.
  • Brambo
    Senior Member
    • Jul 2023
    • 245

    #2
    Maybe a solution is to use pre-processing before sending the data to the next step (LLD)
    So item type script or http-agent whatever you need > in that item jsonpath pre-processing (if possible in your use case) > LLD rule > dependent item on your first one.
    Item prototypes > dependent item on your original item. Not sure if that will work but you know soon enough when you press the test button.

    edit:
    BTW you don't even need to store the data in this scenario, which could save you a lot of load when your polling interval is high.
    Last edited by Brambo; 13-08-2024, 07:54.

    Comment

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

      #3
      IIRC data limits are applied during saving. If you poll the data, save it to "master item" and then point your disco to it, then it probably gets truncated... But if your discovery pulls the data by itself, and then processes it, it should be full size, as it does not store that data ...

      Comment

      Working...