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. Feature Requests
  3. Handling of errors for ExternalParameter

Handling of errors for ExternalParameter

Scheduled Pinned Locked Moved Feature Requests
1 Posts 1 Posters 11.7k 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.
  • R
    R
    rz
    wrote on last edited by
    #1

    Hello,

    1. I'd be usefull to notify admin that monitoring by using ExternalParameter/ExternalParameterShellExec commands is not working correctly.

    If external command is failed, I expect that
     - event should be raised (e.g. SYS_DCI_UNSUPPORTED or any other new event) 
     - "Data collection error" of the ExternalParameter command should be set to <<ERROR>>, so it could be at least checked externally via thresholds.

    I've tested these error conditions: invalid command is launched, script having no execution permission is launched, syntax-error happens in shell/perl scripts, command returns non zero return code. I've tested it on linux/solaris servers (version 1.2.14) with following result: default value (i.e. 0 for int) or first value send to stdout is returned, no error is shown in the logfile, no event is raised. So it is impossible to identify incorrect commands. The same happens for ExternalParameter and ExternalParameterShellExec parameters.

    1. It could be probably better to raise event automatically if error happens, without explicit testing of "Data collection error" status via threshold for each external parameter.  The same behaviour could be applied for external commands with execution timeout exceeded (note: for timeouted external commands "Data collection error" status is set to <<ERROR>> and error could be seen in the logfile, but no event is raised).

    2. I'd appreciate if it is possible to see raw output (stdout/stderr) for these external commands from the console.

    Kind Regards,
    Roman

    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