EMC OL-8950-01 manual Application Signatures, Monitoring Actions

Page 16

Introduction

Application Signatures

Conceptually, applications have characteristics or attributes that uniquely differentiate one application from another; together, these characteristics constitute a signature for a given application. Using the mechanism of Application signatures, we can then further qualify an application to reference particular instances of that application. Application Connectivity Monitor uses signatures to discover and classify software applications in the managed infrastructure. Application Connectivity Monitor includes many predefined signatures.

Application signatures are selected, configured, and enabled through the Application Signature Configuration Interface. Their configuration includes the name of the signature, port number, expected request and response, application class, and an application prefix. System matching criteria can be specified to limit discovery.

Once predefined signatures are configured and enabled, they are automatically registered with Application Connectivity Monitor. At the same time, the signatures are combined with a standard probe, which is set to “Autodetect,” that automatically discovers the specified applications. The discovery of the applications is initiated during the next discovery period, or when a new system is added to the Application Connectivity Monitor topology.

Monitoring Actions

Monitoring actions are scripts or programs that are associated with application signatures. The actions monitor the availability of applications.

Application Connectivity Monitor includes a Standard tcpAction monitoring action that, unless otherwise specified, is used by all application signatures. It automatically monitors application availability by attempting to establish TCP sessions with each managed application. Too, there is an option, with the request/response strings, to provide greater application availability checking.

See Specifying Monitoring Action Parameters on page 24 for additional information.

4	EMC Smarts Application Connectivity Monitor Configuration Guide

Image 16

Contents Configuration Guide Application Connectivity MonitorLast Update 7/29/05 Contents Groups and Settings Creating and Configuring Application SignaturesContents Wildcards Used By EMC Smarts Software Index Contents Preface PurposeIntended Audience PrerequisitesDocument Organization Documentation ConventionsPreface Document OrganizationApplication Connectivity Monitor Installation Directory YourDomainCommand Line Programs Additional ResourcesApplication Connectivity Monitor Products DocumentationTechnical Support EMC PowerlinkTe c h n i c a l S u p p o r t Xii Introduction About Application Connectivity MonitorDefine the Application Managing Applications with Application Connectivity MonitorIntroduction Discover the Software Infrastructure Application Signature Configuration InterfaceAutomated Root- Cause and Impact Analysis Application Signatures Monitoring ActionsDeploying Application Connectivity Monitor Planning the DeploymentInstalling the Software Privileges RequirementSupported Product Versions and Requirements Firewall Deployment ConsiderationsIntegrating Application Connectivity Monitor License ReminderC e n s e R e m i n d e r Availability Manager Adapter PlatformA m p l e o f D o m a i n T y p e E n t r i e s = INCHARGE-AMACM Domain Manager Global Manager A m p l e s o f D o m a i n T y p e E n t r i e sC o n f i g u r i n g t h e G l o b a l M a n a g e r INCHARGE-PMFault P a r a m e t e r s f o r S e r v i c e s Summary of EMC Smarts Service NamesStarting and Stopping the Components Manually Validating Your Integration Modifying Files With the smedit Utility# /opt/InCharge6/SAM/smarts/bin/smedit conf/ics/ics.conf Deploying Application Connectivity Monitor Creating and Configuring Application Signatures Using the Application Signature Configuration InterfaceCreating and Configuring Application Signatures Application Signature TabCreating Application Signatures Application Signature Fields Used By EMC Smarts Software on page 43 for Port Number 25 for Smtp Request No Value Response No Value Modifying Application Signatures Deleting Application SignaturesSpecifying Monitoring Action Parameters Monitoring Action DialogSpecifying System Name Patterns E c i f y i n g S y s t e m N a m e P a t t e r n sUse All Systems Matched by Pattern Customize System Match PatternsUse Only Selected Systems Standard Discovery ProbeE S t a n d a r d D i s c o v e r y P r o b e Standard tcpAction Page Scenarios for Removing Elements Groups and Settings Default Threshold Groups and SettingsThreshold Settings Threshold GroupsFault T h r e s h o l d G r o u p s a n d S e t t i n g s Parameters for Software Service ThresholdsPolling Settings Default Polling Groups and SettingsPolling Groups Opening the Polling and Thresholds Console Working With Groups and SettingsWo r k i n g Wi t h G r o u p s a n d S e t t i n g s Layout of the Polling and Thresholds Console Provides an example of a Polling and Thresholds ConsolePolling and Thresholds Console Toolbar Buttons Polling and Thresholds Console Toolbar ButtonsHow Managed Elements Are Assigned to Groups Modifying the Properties of a GroupMethod for Adding or Removing Settings Method for Modifying the Priority of GroupsMethod for Editing Matching Criteria D i n g o r R e m o v i n g a S e t t i n gMethod for Modifying the Parameters of a Setting D i n g o r R e m o v i n g M a t c h i n g C r i t e r i aCreating New Groups Groups and Settings P y i n g a n E x i s t i n g G r o u p E a t i n g a n E m p t y G r o u pWildcards Used By EMC Smarts Software Server-.smarts.com Compound Wildcard Patterns Example 1-100&*02468 matches even numbers between 1Wildcards Used By EMC Smarts Software Index Index Page Index