Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. String length cut at 255 Characters

String length cut at 255 Characters

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 10.6k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H
    H
    hewa6254
    wrote on last edited by
    #1

    Hi Everyone,

    i wrote a simple curl Shell script that consumes a REST API from my Service i need to monitor.
    The ccript is stored on my netxms server and executed as an ExternalParameter from the local netxms agent.
    It returns JSON Data which i transform with nxsl to get the Information that i want. (This way i can reuse my CURL Script for diffrent APIs)

    My Problem occures when the API returns more than 255 Characters (which it does most of the time).
    The Datatype from the DCI is a String and apparently it can contain 255 Characters max. Everything longer gets cut off.

    Is there a better way to monitor my REST API or am i limited to those 255 Chars?
    I want to transform the Data with nxsl so i dont need a new shellscript for each diffrent API Parameter i want to monitor.
    I think this is a common Monitoring Task, so i think i am just doing this wrong 😄

    Best Regards
    Henry

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi,

      DCI value length is limited to 255 characters. In your case you can use external parameter provider instead of external parameter, do JSON parsing in agent side script and output all parameters you are interested in as name = value. Then you'll be able to collect them by name as any other agent's parameters.

      Best regards,
      Victor

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      Powered by NodeBB Contributors
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups