XtremIO EMC Storage Monitoring with NetEye

Posted by on Nov 7, 2017 in NetEye | 0 comments

NetEye_XtremeIO
If you need to monitor a Dell EMC Storage XtremIO unit, then I have the right solution for you. Not long ago, I wrote an XtremIO storage tracking plug-in that can execute the following activities:

  • XTREMIO_CTRL_Status: monitors the controllers and the hardware status
  • XTREMIO_DPG_Status: controls the DPG groups from the storage array
  • XTREMIO_Storage_Efficiency: verifies and displays the actual XtremeIO “deduplication and compression” efficiency
  • XTREMIO_Storage_Space: checks the available storage space

But how does it work?

Read More

Sending Cisco Syslogs to Elasticsearch: A simple guide

Posted by on Oct 31, 2017 in Log Auditing, NetEye, Syslog | 0 comments

Elasticsearch
Do you use Cisco’s network infrastructure? Would you like to view its logs through the syslog protocol in an Elasticsearch database? Find out below about the filters and templates needed for the Logstash setup.

As you probably already know, you need a Logstash instance in order to get indexed data into the Elasticsearch database. Cisco is a well-known network device provider, so it is crucial to have a workable solution to index the logs that can be retrieved from these devices.

Read More

Using Active Direcory for defining new NetEye Users

Posted by on Jul 31, 2017 in NetEye | 0 comments

Users
Every so often I get asked whether it is possible to integrate Active Directory Users and Groups with NetEye. Until now my answer has always been that it is possible to use AD via its LDAP functionality as an authentication backend, and that you may manually add each AD user one-by-one to NetEye.

I was never very satisfied with this answer and so I tried to find a solution.  Here’s what needs to be done:

Read More

How to send monitoring notifications to Telegram or Microsoft Teams

Posted by on Feb 14, 2017 in NetEye | 5 comments

The conventional thing in a monitoring environment is to notify problems to your staff over E-Mail. Other than E-Mails also SMS are a very common notification type. But is this all we can offer to notify people about problems in our IT?

Obviously, there is more than that. Two very handy examples are:

  • Notifications over the Telegram App (CLI)
  • Notifications over the Office 365 Web API (Microsoft Teams)

Telegram

As you are most probably aware, the WhatsApp-similar application “Telegram”, allows you to send messages to your contacts, groups and also channels. Other then WhatsApp, Telegram has an installable command line interface (CLI) through which you may script the sending of messages from a computer. You have to download and install the Telegram binaries on your monitoring server. After that, you define the notification command in the monitoring in this way:

Host Notification: telegram-cli -W -e "msg $CONTACTEMAIL$ Host '$HOSTNAME$' is $HOSTSTATE$ - Info: $HOSTOUTPUT$ - Time: $SHORTDATETIME$"

Service Notification: telegram-cli -W -e "msg $CONTACTEMAI$ NetEye - $NOTIFICATIONTYPE$ - $SERVICEDESC$ - $HOSTNAME$ - $HOSTADDRESS$ - $SERVICESTATE$ - $SHORTDATETIME$ - $SERVICEOUTPUT$"

Obviously before being able to do this, you have to register your monitoring host as a Telegram sender (the same as you would do it on your smartphone). For this you can use the same phone number you use for sending the SMS’s.

NetEye Telegram Notifications

Read More

Some Words about Logstash Filters and Dates

Posted by on Nov 25, 2016 in Log Auditing, NetEye | 0 comments

date

Some time ago I published an article about how to store the NetEye SMS Protocol log into an ELK environment. Now, after using it some times, I discovered that it was not completely correct as the time/date functions for the Logstash filters are a bit more complicated. In particular, it was that the date was written in the SMS protocol file in this way:

June 29th 2016, 10:30:22 CEST 2016

And we used this Logstash date filter to convert it:

date {
          locale = "en"
          match  = [ "sms_timestamp_text", "EEE MMM dd HH:mm:ss" ]
      }

Now it seemed that it would work, but after some time (some days until the start of the next month) we discovered that the date in the first days of the month would look like:

Read More