IBM Security Resilient

Expand all | Collapse all

Resilient scripting log is empty

  • 1.  Resilient scripting log is empty

    Posted Tue January 28, 2020 05:02 AM
    Edited by Aitor Vivanco Sata Cruz Tue January 28, 2020 05:10 AM

    I suppose that scripting errors are written in the log file 
    • /var/log/resilient-scripting/resilient-scripting.log

    When I access into this logs file, my errors are not appearing, it looks like there is a writing error or something. For example, when I try the script on the Resilient console, it gaves me this message:'=============================================================================== Hi!')
    log.debug('=============================================================================== Hi!')
    log.warn('=============================================================================== Hi!')
    log.error('=============================================================================== Hi!')

    But as I said before, the error is not visible on the scripting log.

    Thank you.

    Aitor Vivanco Sata Cruz

  • 2.  RE: Resilient scripting log is empty

    Posted Tue January 28, 2020 05:30 AM
    Hi Aitor,

    Thanks for your query, hopefully I can clarify this for you.

    So the log messages added to a script using log.* statements are only visible in the console as you've seen, and are really used more for debugging scripts that are under development. These messages are not actually written to a file, they are displayed in the console when the script completes.

    The resilient-scripting.log file is the log for Resilient's scripting service and contains information related more to the mechanics of actually running of a script rather than what the script is doing line-by-line.

    There is a framework through which product feature requests/ideas can be submitted, here is one in the general area of script logging but you can also submit your own too for the community to vote on if you so wish:

    Hope this helps,

    Paul Curran