Skip to Content

NAGIOS for SAP HANA Infrastructure Monitoring (part I)

Nagios is a server monitoring infrastructure available to help Infrastructure and datacenter team monitoring day to day tasks. In the olds days we used to have to run horribly cryptics commands like sar, ps, du, df, and others, then parse the output with awk and sed and then figure out how to do something with the data. These commands were never standardized so scripts running under Solaris may not work as expected under SunOS! Things gradually evolved and Nagios came on the scene almost 20 years ago. Nagios is now used to monitor sites with hundreds of thousands of services and you can configure tiered monitoring if you need maximum scalability. Nagios is incredibly flexible, but its greatest strength is also its weakness. Its power comes from the fact that it is based on scripting, allowing you to monitor literally anything. It’s notification system is also based on scripts, so you can do whatever you like with the information, even restart services, clean old logs, or whatever. You can even download pre-written scripts to extend Nagios in all sorts of ways. Check the Nagios website for a repository.

>>> Prerequisites – Very basic requirement your company should be using RedHat or CentOS or SuSE, I recommend you purchase Nagios XI version.

SAP CCMS (our old school monitoring) is integrated part of SAP, which provide the low and intensive level monitoring of SAP servers including their hardware and software. It monitor almost all the the things in SAP. As Nagios is an open source tool working as an Enterprise monitoring server for data center and lots of Enterprises are using it. It give the good interface to administrators and have very good alerting options through mail or sms according to the escalation matrix. We can take predefine remedies action on affected service.

It can send alert through SAP as well. But I do this through nagios because I wants to do the
centralized monitoring and making the Nagios as an complete Enterprise Monitoring solution for
complete Data center.

I will cover end to end runbook to setup Nagios integration with –

SAP in NAGIOS for SAP HANA and SAP Netweaver Monitoring (part II) blog

 

>Upcoming contents in part 2 –


Table of contents
1. Nagios installation
1.1 Prerequisites
1.2 Installation of nagios and nagios plugins
2. Installation of SAP Plugins
3. Configuration of SAP MON
3.1 Configuration of login.cfg
3.2 Configuration of Agent.cfg
4. Configure the SAP server for monitoring
5. Configure nagios of SAP monitoring
5.1 Checking the sap monitoring through commands
5.2 Make changes in nagios configuration

 

To be continue……

 

 

Any comments, feedback are appreciated.

Thank you.

Amit Lal

 

 

Disclaimer – These are my personal opinions and thoughts. This does not represent any formal opinions, POVs, inputs, product road-maps etc. from my current or past employers or partners or/and any Clients.
/
10 Comments
You must be Logged on to comment or reply to a post.
  • When is part 2 coming, it has been over 6 months… Basic HANA monitoring integrated with Nagios would be great, especially considering how painful it is to configure alerting for multiple tenants using the HANA Cockpit.

     

  • Hi Martin, All

    Really sorry about it, I am really busy working on tightly scheduled projects related to SAP Cloud, will definitely love to write on this topic. Let me know if you need any help with it.

     

    Regards,

    Amit

  • Hi Amit,

    We did configuration of SAP HANA Nagios monitoring but we are facing with the issue. If we starting the scripts locally everything is working fine. However if we are trying to do that remotely from NAGIOS server with nagios user we are getting :

     

    GetAlertTree FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen -> The sap-system-nr is incorrect.

    FAIL: HTTP error, HTTP/1.1 401 Unauthorized -> You use a new sap-kernel binarie (greater then 7.21)
    In this new version the sapstartsrv service have security features enabled.
    Set the paramter service/protectedwebmethods=NONE in the sap-instance profile
    NONE->sapstartsrv-security-features disabled
    For more information have a look at SAP-Note 927637.
    Other solution, you can create a monitoring user in sap-profile!

     

    Of course, we tried to change the value for service/protectwebmethods but did not help.

    Do yo have any hints for this ?

    Thank you in advance,

    Regards,

    Martin