Share This:



Every quarter we release new functionality in our TrueSight Operations monitoring repository. In each release we add key technologies to support your diverse, heterogeneous environment. All good monitoring solutions come with broad, deep and simple to use OOTB coverage and ours is no exception. However, there are times when you need a little more control and/or horsepower in your monitoring. The December 2016 release is big news for everyone with UNIX/Linux systems. PATROL for Scripting has arrived – and it’s going to put you in the drivers seat.


So what is PATROL for Scripting?


This solution executes scripts and sets values and parameters based on the returned output. At first blush, this doesn't sound like much, but it is very powerful in practice. It will also take care of distributing scripts to the appropriate systems AND maintain synchronicity with its configuration in TrueSight (which also happens to be file-based and attached to device discovery). In short, you can programmatically configure through file manipulation and have TrueSight distribute the configurations.


The solution comes with a library of sample scripts as well as configuration examples. But the real beauty of the solution is its flexibility. If you can dream it, you can do it. Command line gurus rejoice!


What can you do with it?


Here are a few example scenarios to get your creative juices flowing:


  • Execute any script or application from the command line to a standard output stream.

    This could be a simple one-line command which prints directory size:
    # du -sh /opt/bmc/TrueSight/TSIM/pw/pronto/logs|awk -F " " '{print $1}'

    Or a path to a script residing on the remote filesystem or perhaps a Java application which you launch from the command line.
  • Bring custom data into TrueSight for dynamic baselining in cases where the Data Integration KM is more complex to use.
  • Skip writing your own cumbersome custom KMs or replace existing ones for easier upkeep and simpler migration.
  • Bring in data from your environment that TrueSight doesn’t have OOTB monitoring for.
  • Perform 3rd party host monitoring.  Ex. PATROL is on host A and you want to monitor the connection between hosts B and C.
  • Execute monitoring based on OS level scheduling - where the script controls execution logic.
  • Add configuration management to monitoring policies so you always know which machine has the right patches installed.


Let’s not stop here. Reply to this post with your ideas. Maybe they’ll be the next great addition to the library.




Dennis Newberry
Lead Product Manager