Forum Discussion

Mike_Moniz's avatar
Mike_Moniz
Icon for Professor rankProfessor
5 years ago

Monitoring Linux systems using SSH

On 4/18/2020 at 2:55 PM, raul.rtr said:

So with current SSH based Linux datasources we miss important required capabilities:

- Linux text log monitoring: Basically, we need to be able to monitor specific log files in a target server for the appearance of specific error patterns on them, and raise an alert in case any of this error occurs. The rule to trigger the alarm must manage the triggering of the alarm depending on the recurrence of the errors and probably other rules. The datasource should be able to manage checkpoints in order to be aware what was the last log line read ensuring that always read only new content in monitored files.

- OS process monitoring: we need to be able to monitor the presence of OS processes and if the number of processes instances required are in execution and probably other rules.

 

 

 

I suggest you start a new thread/topic. You can also try taking one of the existing linux ssh DataSources and customizing the Groovy code to do the work you need.

1 Reply

Sort By
  • Anonymous's avatar
    Anonymous
    5 years ago

    This thread was split from here. @raul.rtr, tagging you for visibility. You said:

    Quote

    Hi,

    Currently starting the implementation of Logicmonitor in our organization, replacing an old agent based monitoring tool. Probably one of the main reasons to select LM has been the agent-less monitoring capabilities.

    SNMP based linux monitoring is not an option for us, neither installing LM collectors in each monitored server.

    So with current SSH based Linux datasources we miss important required capabilities:

    - Linux text log monitoring: Basically, we need to be able to monitor specific log files in a target server for the appearance of specific error patterns on them, and raise an alert in case any of this error occurs. The rule to trigger the alarm must manage the triggering of the alarm depending on the recurrence of the errors and probably other rules. The datasource should be able to manage checkpoints in order to be aware what was the last log line read ensuring that always read only new content in monitored files.

    - OS process monitoring: we need to be able to monitor the presence of OS processes and if the number of processes instances required are in execution and probably other rules.

    Thanks.

    Raúl

     

    Quote

    Linux text log monitoring: Basically, we need to be able to monitor specific log files in a target server for the appearance of specific error patterns on them, and raise an alert in case any of this error occurs. The rule to trigger the alarm must manage the triggering of the alarm depending on the recurrence of the errors and probably other rules. The datasource should be able to manage checkpoints in order to be aware what was the last log line read ensuring that always read only new content in monitored files.

    You would accomplish this via a custom EventSource.

    Quote

    - OS process monitoring: we need to be able to monitor the presence of OS processes and if the number of processes instances required are in execution and probably other rules.

    You can do this with a custom Groovy based Datasource making use of the Expect library built into the collector.