SAP Solution Manager monitors the behavior of SAP Instances and sends notification email in case of misbehaviors. Integrating this solution with NetEye the benefit is the possibility to have the mails sent to a user on NetEye Server and thanks to a procmail script rows are inserted into the MessageConsole Application. The script could be like this:
#! /bin/sh
#
export PATH=/usr/local/bin:/usr/bin:/bin:$PATH
#
mailfile=~/tmp/mail$$.log
logfile=~/tmp/mailout$$.log
tmpfile=~/tmp/mailmsg$$.log
#
trap 'rm -f $mailfile $logfile $tmpfile; exit 1' 1 2 15
trap 'rm -f $mailfile $logfile $tmpfile' 0
#
cat >$mailfile
echo EOF >>$mailfile
#
if [ ! -e $mailfile ]
then
echo "Cannot write to $mailfile"
exit 1
fi
#
subject=`cat $mailfile | formail -xSubject | sed -e 's/^ *//g'`
if ! echo "$subject" | grep "SAP Alert"
then
exit 1
fi
#
state=$(grep -E "^[A-Z]* CCMS alert" $mailfile | tail -1 | awk '{ print $1 }')
if [ "$state" = "YELLOW" ]
then
severity=w
else
severity=c
fi
clienthost=SAP
#
to=`cat $mailfile | formail -X "From " | cut -d' ' -f2`
#
cat $mailfile | formail -I "" | (
line=""
read line
while [ "$line" = "" ]
do
read line
done
startblock=0
while [ "$line" != "EOF" ]
do
if echo "$line" | grep "^ALERT f"
then
cat /dev/null >$tmpfile
startblock=1
fi
if [ -z "$line" ]
then
startblock=0
fi
if [ $startblock -gt 0 ]
then
echo "$line" >>$tmpfile
fi
read line
done
)
#
if [ -s $tmpfile ]
then
msgfile="-f $tmpfile"
fi
#
nesendmsg -H localhost -s "$subject" -S "$severity" -l "$clienthost" $msgfile
exit 0
One of the advantage would be to monitor actively if the SAP instances are running, at the very least the one running the Solution Manager. This is done using the binary rfcping and the Nagios check command check_sap_rfcping using the following command syntax:
check_sap_rfcping -a $HOSTADDRESS$ -s-w 2000 -c 5000
Doing so it gives you a pretty good overview over your running SAP instances. 😉
I have over 20 years of experience in the IT branch. After first experiences in the field of software development for public transport companies, I finally decided to join the young and growing team of Würth Phoenix (now Würth IT Italy). Initially, I was responsible for the internal Linux/Unix infrastructure and the management of CVS software. Afterwards, my main challenge was to establish the meanwhile well-known IT System Management Solution WÜRTHPHOENIX NetEye. As a Product Manager I started building NetEye from scratch, analyzing existing open source models, extending and finally joining them into one single powerful solution. After that, my job turned into a passion: Constant developments, customer installations and support became a matter of personal. Today I use my knowledge as a NetEye Senior Consultant as well as NetEye Solution Architect at Würth Phoenix.
Author
Juergen Vigna
I have over 20 years of experience in the IT branch. After first experiences in the field of software development for public transport companies, I finally decided to join the young and growing team of Würth Phoenix (now Würth IT Italy). Initially, I was responsible for the internal Linux/Unix infrastructure and the management of CVS software. Afterwards, my main challenge was to establish the meanwhile well-known IT System Management Solution WÜRTHPHOENIX NetEye. As a Product Manager I started building NetEye from scratch, analyzing existing open source models, extending and finally joining them into one single powerful solution. After that, my job turned into a passion: Constant developments, customer installations and support became a matter of personal. Today I use my knowledge as a NetEye Senior Consultant as well as NetEye Solution Architect at Würth Phoenix.
Fixing Misplaced Plugin Output in Icinga Web Interface When plugin output contained HTML content (like links), it was incorrectly displayed near the service name instead of in the Plugin Output section. The plugin output section now correctly renders all content. Read More
Icinga Director Now Responsive During Configuration Deployments Previously, users were unable to interact with Icinga Director while configuration deployments were running. Any attempt to access the interface or API would be blocked until the deployment completed, causing unnecessary delays in Read More
Bug Fix We updated the version of GLPI in order to fix some relevant vulnerabilities. List of updated packages The following packages have been updated for NetEye 4.45: glpi, glpi-autosetup, glpi-configurator, glpi-neteye-config to version 10.0.22_neteye1.17.5-1.
Bug Fix in Tornado Module We solved an issue in Tornado's rule configuration where the action_name field in director actions was being cleared after saving and deploying. When users created a rule with a director action and filled in both Read More
Today we continue our journey into monitoring automation in NetEye. In my previous post we discussed the possibility of automating Business Processes. As you may remember, for those of us working on NetEye Cloud monitoring dozens of clients, it's important Read More