About eHealth® Live Health By Sohit Agarwal (Lecturer CS/IT)

Getting Started
This topic introduces the Live Health™ applications and
their system requirements.

Live Health Overview
Live Health consists of the following applications:
• Live Exceptions
• Live Status®
• Live Trend

About Live Exceptions
Live Exceptions provides real-time reporting of alarm
conditions to network operations center (NOC) and systems,
application, and network management personnel. It identifies
problems that include delay, errors, failures, security, or
configuration changes. It can display information about alarms
in its Browser, as well as send traps (alarms) to network
management systems (NMSs) and other trap destinations. For
integrated NMSs, users can view a condition, identify the
system component that generated it, and then run eHealth
historical reports to analyze the problem further. Live
Exceptions provides consistency and reduces alarm duplication
by using eHealth historical data to ensure that the alarms are
meaningful. If your account has the appropriate permissions,
you can also acknowledge or annotate an alarm.
Live Exceptions includes default profiles for all technologies.
The profiles organize variables by delay, availability, unusual
workload, and latency. Users with Live Health administrator
permissions define conditions by specifying variables to
examine, thresholds to detect, and intervals over which to
examine the data.


Fault Manager
eHealth Live Health — Fault Manager is an enhancement to
Live Exceptions and the Live Health suite of tools. It allows
eHealth to receive Simple Network Management Protocol
(SNMP) trap messages from other systems and devices and to
take actions based on Live Exceptions alarm rules. Fault
Manager can receive traps from any device or other NMS (such
as HP® OpenView). By default, Fault Manager can recognize a
variety of trap types (that is, it has certified trap types);
however, administrators may define additional trap sources for
use with Fault Manager. You can also request that Concord
certify additional trap types.
Unlike other trap-collecting applications that create logs of trap
messages, Fault Manager interprets and processes trap
information. It reduces the noise of duplicate and repeated
messages and alerts you to the problems and conditions that
interest you. When the eHealth system receives a trap, it
processes the trap based on Live Exceptions rules and profiles
that the Live Health administrator configures. Thus, you can
configure Fault Manager to raise an alarm for the associated
element or to ignore various trap messages.

Fault Manager takes advantage of the eHealth poller
configuration to associate the IP address in the trap message
with an element. You see the more informative element
name—not just the IP address. Thus, when traps raise alarms,
you can drill down to additional reports to obtain more detailed
information about the element and the problem.
If Fault Manager receives a trap for an IP address that eHealth is
not monitoring, it can still report the problem and raise an
alarm for the unknown element.
When Fault Manager receives traps from other sources, it
processes this data as it does data collected by eHealth: it
compares the performance statistics to rules defined in profiles
and generates intelligent alarms when thresholds are exceeded.
You can view these alarms in the Live Exceptions Browser,
which provides access to element-specific drill-down
information when available.
eHealth SystemEDGE and eHealth application insight modules
(AIMs) provide a source for out-of-the-box traps to Fault
Manager. You can use the SystemEDGE agent to monitor
thresholds, processes, log files, Windows® NT events, and
process groups so that you can respond to problems
immediately. A

About Distributed Live Health
Distributed Live Health combines the real-time performance
and availability management offered by Live Health with the
scalability of Distributed eHealth. Distributed eHealth allows
you to monitor up to one million of your critical resources
using several eHealth systems that are connected in a
configuration referred to as a cluster. Distributed Live Health
allows you to monitor and manage the alarms raised by
Live Exceptions across the same one million elements.

From the Live Exceptions Browser running on a Distributed
eHealth Console, you can monitor alarms from systems across
the cluster. You can also drill down on an alarm to view
historical and real-time reports from the eHealth system that
generated that alarm. This allows you to manage the
performance and availability of systems around the world from
a single point.





About Live Status
Live Status provides a high-level view of the current status of
your critical resources as determined by Live Exceptions. Live
Status displays a diagram of the elements in a group list. Icons
that represent the elements are color-coded to reflect their
alarm and monitoring status. You can look at the display and
quickly assess the status of your resources based on color
changes in a logically grouped graph.
You can identify the trouble spots at a glance and quickly drill
down for details to understand the nature of the problem.


About Live Trend
Statistics elements are members
of an eHealth element type that
includes various LAN and WAN
interfaces; Frame Relay circuits;
Asynchronous Transfer Mode
(ATM) paths, ports, and
channels; various components of
routers and systems, as well as the
router and systems themselves;
various remote access resources;
and applications, such as
Microsoft® Exchange and
Oracle™.

Live Trend is an application that you can use to create charts
that monitor statistics elements that you are polling using
eHealth. You can create a single chart or multiple charts in
various styles to represent both element trends (a single
element with multiple variables) and variable trends (a single
variable for multiple elements). Live Trend updates the charts
each time eHealth polls the elements.
You can display the following types of data:
• As polled
• Fast sampled
• Up to 48 hours of history data



System Requirements
A system or workstation that has
an installed version of the Live
Health software is called a Live
Health client.

If you plan to download and install the Live Health applications
on your local workstation, your workstation must meet the
following requirements. Unless stated otherwise, these
requirements apply to all supported language versions of
eHealth.