Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated the digi-accordion macro with the following parameter(s): []
Panel
borderColor#72B0DE
bgColor#72B0DE#F0F0F0
Digi accordionexpand
titleSummitAI IT Operations Management

SummitAI IT Operations ManagementSUMMIT AI Availability Management_Alps

SUMMIT Platform Components

Monitoring Types

Digi accordionexpand
titleConcepts

Auto Upgrading of Proxy Agent

Hyper-V

IPSLA

Netflow

VMware

Event Management

Digi accordionexpand
titleDashboards

Viewing Operations Dashboard

Viewing Oracle Dashboard

Viewing SQL Server Dashboard

Viewing Exchange Server Dashboard

Digi accordionexpand
titleViews

Network View

Network Device View

Event View

Server View

Server Group View

Printer View

Common View

Digi accordionexpand
titleServer Management
Expand
titleAnalysts

Server Dashboard

IIS Dashboard

ASP.NET Dashboard

Cloud Dashboard

Storage Dashboard

Application Dashboard

Creating Server Views

Viewing Server Details

Defining Server Groups

Expand
titleAdministrators

Save Discovered Servers

Adding Servers

Configuring Application Log Templates

Configuring Event Log Templates

Defining Mailbox Relations

Adding Cloud VM for Monitoring

Digi accordionexpand
titleNetwork Management

Network Management

Expand
titleAnalysts

Creating Views from Drawing Board

Creating Views from Discovered Devices List

Network Dashboard

Viewing Network Link Details

Edit Network Link Details

Viewing Network Device Details

Viewing Network Interface Details

Editing Network Device Details

Expand
titleAdministrators

Adding Interfaces for Monitoring

Digi accordionexpand
titlePrinters

Adding Printers

Save Discovered Printer

Printer View

true
Digi accordionexpand
titleURLs

Adding or Modifying URLs

Digi accordion
expanded
digi-accordion
Expand
titleEvent Management

Event Management

Configuring Event Action Templates

Configuration and Mapping

Configuring Event CI Relations

Configuring Help

Configuring Problem Templates

Configuring Event Processing

Expand
titleRisks

Configuring Asset Value

Configuring Business Impact Risk

Configuring Correction Capability

Probability of Occurrence

Probable Timeline of Detection

Viewing Overall Risks

Digi accordionexpand
titleCloud Management

Adding Accounts

Adding Resources

Adding Virtual Machines

Adding Virtual Machine Templates

Digi accordionexpand
titleOther Administrative Actions

Configuring Master Settings

Configuring Custom Scheduler Script/SNMP

Configuring Script or SNMP Thresholds

Importing Data

Mapping Proxies

Configuring Alerts And Log Incidents for Proxy Servers

Configuring Jobs for Device Maintenance

Configuring Job Hung Notifications

Configuring Service Entitlements

Configuring Cost

Configuring Risk

Configuring Incident Templates

Configuring Action Templates

Configuring Application Server Threshold

Configuring Alerts And Log Incidents

Configuring Alert and Log Incidents for Hard disk and Service

Configuring Vital Business Functions

Configuring Standard Operating Procedure Mapping

Mapping Standard Operating Procedures

Default Configuration

Digi accordionexpand
titleReports

Viewing Reports

Scroll export button
scopecurrent
template-idc9a14909-8f27-452d-bca0-164bee1a9265
captionDownload this Page
add-onScroll PDF Exporter

An Event is any significant change in the state of a device, observed while monitoring. Event Management allows constant monitoring of devices, and categorizes events (as Critical, Warning, Alert and Information) to take relevant actions, whenever required.


Figure: Event Management Workflow

 

Monitoring of devices involves the following parameters:

  • Availability Parameters: Availability of the service being monitored.
  • Utilization Parameters: Utilization level of the resources, by a service, being monitored.

An Event occurs whenever any significant change in the above listed monitoring parameters occurs. The User is notified about the Event through SMS or E-mail. The criticality of the Event is categorized in the following order:

  1. Critical
  2. Warning
  3. Alert
  4. Information

Based on the criticality of the Event, an Incident can be created as an action to resolve the cause of the Event. Once the cause of the Event is resolved, the corresponding Incident can be closed.


Scroll ignore
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmltrue
truenoneRelease Noteshttp://summitconfluence.symphonysummit.com:8090/display/PD/SUMMIT+Release+NotestruenoneInstallation Guide http://summitconfluence.symphonysummit.com:8090/display/PD/Installation+GuidetruenoneOther Documents http://summitconfluence.symphonysummit.com:8090/display/PD/Other+Documents1

| |