template maintenance – file system monitoring variants€¦ · template maintenance – file...

Template Maintenance – File SystemMonitoring Variants

Applicable Releases:

SAP Solution Manager 7.1 SP1 and higher

SAP Solution Manager Scenarios:Technical Monitoring

David Heffernan

Pavan Rao TK

Version 1.1

February 2013

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The information containedherein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPoint areregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,i5/OS, POWER, POWER5, OpenPower and PowerPC aretrademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Readerare either trademarks or registered trademarks of AdobeSystems Incorporated in the United States and/or othercountries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registeredtrademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,Inc., used under license for technology invented andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAPNetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world.All other product and service names mentioned are thetrademarks of their respective companies. Data containedin this document serves informational purposes only.National product specifications may vary.

These materials are subject to change without notice.These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAPGroup shall not be liable for errors or omissions withrespect to the materials. The only warranties for SAPGroup products and services are those that are set forth inthe express warranty statements accompanying suchproducts and services, if any. Nothing herein should beconstrued as constituting an additional warranty.

These materials are provided “as is” without a warranty ofany kind, either express or implied, including but notlimited to, the implied warranties of merchantability,fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind includingwithout limitation direct, special, indirect, or consequentialdamages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links or other items containedwithin these materials. SAP has no control over theinformation that you may access through the use of hotlinks contained in these materials and does not endorseyour use of third party web pages nor provide any warrantywhatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplifythe product implementation. While specific productfeatures and procedures typically are explained in apractical business context, it is not implied that thosefeatures and procedures are the only approach in solving aspecific business problem using SAP NetWeaver. Shouldyou wish to receive additional information, clarification orsupport, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)included in this documentation are only examples and arenot intended to be used in a productive systemenvironment. The Code is only intended better explain andvisualize the syntax and phrasing rules of certain coding.SAP does not warrant the correctness and completeness ofthe Code given herein, and SAP shall not be liable forerrors or damages caused by the usage of the Code, exceptif such damages were caused by SAP intentionally orgrossly negligent.

Disclaimer

Some components of this product are based on Java™. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is onlyto be used by SAP’s Support Services and may not bemodified or altered in any way.

Document HistoryDocument Version Description

1.0 First official release of this guide

1.1 Additional examples for Windows file systems

Table of Contents

1 Overview ..........................................................................................................................1

1. Adding the file system variants ......................................................................................11.1 Simple Regular Expression .......................................................................................1

1.1.1 Unix Technical System .................................................................................11.1.2 Windows Technical System ..........................................................................3

1.2 Negative Regular Expression ....................................................................................71.2.1 Unix Example ...............................................................................................71.2.2 Windows Example ........................................................................................8

2. Changing the individual thresholds ............................................................................. 10

Template Maintenance – File System Monitoring Variants

February 2013 1

1 Overview

The goal of this document is to show how to customize a template to monitor only specific file systems andalso how change the monitoring threshold for each variant.

1. Adding the file system variantsThe file system monitoring configuration uses regular expression to filter the monitoring result set of the SAPHost Agent. The filtering is done by SMD Agent. The example below uses a simple example by defining ametric group for each file system you intend to monitor. You could create one metric grouping and use acomplex regular expression however the advantage of the simple approach is that you can have differentconfigurations such as different thresholds for each monitored file system.You can either create a new host template for your OS by extending a SAP template or modify an existingtemplate.

1.1Simple Regular Expression

1.1.1 Unix Technical System

In the first simple example you we will add a variant to monitor one particular file system using the regularexpression:

/oracle(.*)*Once you have selected your OS template you follow the instructions below:

1. You go you to edit mode and then select the expert mode.

2. Select the metric tab

3. Select the metric “File System Free (%)”

You then select on the Data Collection tab for this metric and add a variant. If you want to monitor thefile system for oracle on Unix or Linux you would use the regular expression (valid for Linux or Unix):

/oracle(.*)*


February 2013 2

4. This can be done for every file system intended to be monitored. For example, here we monitorOracle, SAP and Aris:

5. It is important to deactivate the default metric variant “.*” from the list of metric groups associated forthis metric otherwise you will still see the all file systems monitored by the SAP Host Agent. You cansee this in the screenshot shown above.

6. After this the Technical Monitoring setup needs to be done for the system selecting the option “AssignTemplate” and selecting the template you have just modified or created:


February 2013 3

7. It is possible to have any template that is created as the default template. One could use this templateas a default assignment for the OS if this OS is prelevant within the landscape. This is can be done inStep 4 Template Maintenance.

8. Once the set up is complete it could take 5 to 10 minutes before it is possible to see the newmonitoring take effect:

1.1.2 Windows Technical SystemIn the first simple example you we will add a variant to monitor one particular file system using the regularexpression:

Ex: [C].*.To monitor drives from C to F, the example is asfollows [C-F].*

Once you have selected your OS template you follow the instructions below:1. You go you to edit mode and then select the expert mode.

2. Select the metric tab

3. Select the metric “File System Free (%)”

You then select on the Data Collection tab for this metric and add a variant. If you want to monitor thefile system for C drive you would use the regular expression (valid only for Windows): [C].*


February 2013 4

4. This can be done for every file system intended to be monitored. For example, here we monitor D drive,E and F drive simultaneously.


February 2013 5

5. After this the Technical Monitoring setup needs to be done for the system selecting the option “AssignTemplate” and selecting the template you have just modified or created:


February 2013 6

6. It is possible to have any template that is created as the default template. One could use this templateas a default assignment for the OS if this OS is prelevant within the landscape. This is can be done in Step4 Template Maintenance.

7. Once the set up is complete it could take 5 to 10 minutes before it is possible to see the new monitoringtake effect:


February 2013 7

1.2Negative Regular Expression

1.2.1 Unix ExampleIn this example one can create a variant to exclude certain file systems. A regular expression such as:

(?:(?!/oracle(/.*)*)(?!/aris(/.*)*).*)

The example above will show everything the SAP Host Agent monitors with the exception of the file systemsoracle and aris. Below is an example of the configuration:

And this will result in a complete file system monitoring with exception of the above folders which can be seenin the example below:


February 2013 8

1.2.2 Windows ExampleIn this example one can create a variant to exclude certain file systems. A regular expression would be likethis [^<Drive>].*

Example: [^D].*

The example above will show everything the SAP Host Agent monitors with the exception of the D drive filesystem. Below is an example of the configuration:

And this will result in a complete file system monitoring with exception of the above folders which can be seenin the example below:


February 2013 9


February 2013 10

2. Changing the individual thresholds

It is possible to change the threshold of each individual file system being monitored i.e. each variant. In orderto do this you should select the metric (as explained previously) and then the variant for your file system belowthe metric in the table:

In the example above I have selected the oracle file system and in the defaul threshold setting s it is possibleto change the thresholds. It is also possible to define different threshold for the different work modes that mightcome into effect for your Technical System such down time or peak times.

template maintenance – file system monitoring variants€¦ · template maintenance – file...

Documents