LogicMonitor healthcheck, Logicmonitor portal, LogicMonitor Professional Services, Monitoring

ReportMagic’s Free LogicMonitor HealthCheck is live

Panoramic Data are pleased to announce the General Availability of our free LogicMonitor HealthCheck!

6 months in the making, and with 150+ individual checks using 100,000+ automated actions, this comprehensive report presents a series of recommendations against best practices.  See statistics, issues, errors and compliance information, and prioritized recommendations for change.

Our HealthCheck report:

  • Reviews your LogicMonitor portal settings, focusing on security, reliability and best practice compliance
  • Includes information about Device and Collector health, as well as entity grouping standards
  • Assesses your usage of LogicMonitor functionality
  • Provides you with wide-ranging feedback identifying issues and suggested remedies
  • Benefits you by giving you a more successful and stress-free experience of the LogicMonitor product
  • Includes a comprehensive, interactive Device and Alert Analytics spreadsheet
  • Uses “Heatmaps” to draw the eye into each actionable recommendation, allowing the reader to skip over purely informational items

See here for more details and to request a report.

Logicmonitor DataSources, Windows updates

Windows update monitoring using a LogicMonitor DataSource

There is an simple method to help keep your PC safer and running smoothly – I mean by using Windows Update of course. All you have to do is turn it on, and you will get the latest security and other important updates from Microsoft automatically.

However, running it on a mission critical server is the last thing you want. You do not get a chance to evaluate updates before installing them, nor are you protected when Windows Update decides it’s time to reboot. What if it reboots in the middle of your latest backup, for example? Most people set updates and backups in the same early hours of the morning to avoid disruption. So in the majority of cases, administrators often disable automatic updating all together. We all make plans to check updates on a regular basis and install them within a reasonable time frame, but the best-laid plans of mice and men….

And before you know it there are potentially hundreds of critical updates waiting to be installed. Mainly security updates – meaning your servers are susceptible.

So we created a LogicModule, CriticalUpdateCheckPS, which checks your servers using Powershell for any available updates, and alerts you by email, text or voice using LogicMonitor.

In our first design, the time taken to establish a Microsoft Update Session and then interrogate it for updates was too long; scripts were tying up threads and using collector resources more rapidly than required. So back to the drawing board, and we wrote a script that runs locally on the servers, uses Task Scheduler to run once a day and which quizzes the update site for the number of critical updates and writes the number to a file stored on the server.  Then we created the CriticalUpdateCheckPS DataSource with a much simpler script that simply logs onto the server being monitored for updates and reads the contents of the file written by the scheduled script. This allowed us to collect the data in seconds.

You can set your thresholds however you want  we suggest > 5 10 20, so you get an warning alert on 5 or more, an error alert on 10 or more, a critical alert on 20 or more. But this is, of course, your choice.

An example alert is shown here:

  • ID: LMD12345
  • This server, APP013XYZ, has 17 outstanding critical updates to be installed. 

By alerting you to the fact and reminding you, (a.k.a. nagging) you are more likely to deal with it.

The DataSource applies to any device that has a system category of “CheckUpdates”.

Using the CriticalUpdateCheckPS DataSource

Here’s how you’d use it in LogicMonitor:

  1. Navigate to the Devices tab.
  2. Navigate to the level that you want to set the property – the root level for your device tree, a group, or a device
  3. Click the Manage button for that group or device.
  4. From the Manage dialog box, you can change the value for a system category by clicking on the value field and adding CheckUpdates. It there are already values in there, remember to separate them with a comma.
  5. You will also need two new properties PS.USER and PS.PASS (credentials which allow you to run remote scripts in Powershell).
  6. Additionally you will need to deploy the local script, a folder (C:/LMCriticalUpdates) which contains the local script, and set it to run once per day.
    Note: Your servers must be set for remote Powershell scripts as per LogicMonitor’s help page.
Logicmonitor DataSources, Monitoring

SSL errors and alerting using a LogicMonitor DataSource

SSL/TLS is a deceptively simple technology. It is simple to deploy, and it just works. Except the truth is – it does not really work, and it is not easy to deploy correctly! To ensure that SSL provides the necessary security, you have to put effort into properly configuring your servers.

For example, consider the  POODLE attack (Padding Oracle On Downgraded Legacy Encryption), a man-in-the-middle exploit taking advantage of Internet and security software clients’ fallback to SSL V3. An attacker could successfully exploit this vulnerability by making no more than 256 SSL 3.0 requests to reveal one byte of encrypted messages. But the time taken to check all sites under your control can quickly mount up and become a task that you leave for another day, which, in IT, means someday….

So we created a LogicModule, SSL Test, which checks your sites for certain vulnerabilities, and alerts you by email, text or voice using LogicMonitor. At the time of publication, it checks for Beast, Logjam, Freak, Heartbleed,  Luckyminus20, Debian Flaw, OpenSslCcs, drown, Known DH primes and poodle Attacks vulnerabilities. It also checks the SSL certificate matches the address.

An example alert is shown here:-

  • ID: LMD12345
  • This server, www.yourwebsite.co.uk, is vulnerable to the POODLE attack. If possible, disable SSL 3 to mitigate.

By alerting you to the fact and letting you know how to deal with it, you are saving time having to trawl through RSS feeds and security updates. You need to manually add each website you want to check as an instance in LogicMonitor.

Using SSLTest

To do this :

  1. Select a host in LogicMonitor, (it doesn’t matter which one as it is just a placeholder for the DataSource; the actual check is done from the Collector).
  2. Click the down arrow shown here:
    one
  3. Select Add monitored instance then fill out the various required values:
    two

And that is it!