[cgl_discussion] Request for review of App. Heartbeat Service

Zhuang, Louis louis.zhuang at intel.com
Thu Sep 26 23:05:59 PDT 2002

Dear all,
I noticed that the sentence in requirement doc "Application heartbeat time
shall be granular to at least 10 msec resolution
(at least 100 heartbeats/second).". According the scheduling time-slice in
Linux (1/100 second), it might be a mission impossible. :)

Louis Zhuang, SW Engineer, Intel Corporation.
My opinions are my own and NEVER the opinions of Intel Corporation.

-----Original Message-----
From: Brugger, Andrea L [mailto:andrea.l.brugger at intel.com]
Sent: 2002?9?14? 6:41
To: 'cgl_discussion at osdl.org'
Subject: [cgl_discussion] Request for review of App. Heartbeat Service

Project Review Request for Application Heartbeat Service

1. Quote the requirements from the requirements doc that your project is
expected to meet.

Requirement 3.3 Application Heartbeat Monitor --
" OSDL CGL shall provide an application heartbeat service that allows
to register to be monitored via standard APIs and allows a registered
to be monitored by the service. This mechanism shall use periodic
events (heartbeats) between an application and the monitor. If a registered
application fails to provide a heartbeat, the monitor shall report the event
via the
system event log.
Application heartbeat time shall be granular to at least 10 msec resolution
(at least
100 heartbeats/second).
The application heartbeat service shall be available to any process or
(thread) entity on the system. A process or thread may register for multiple
heartbeats. Each heartbeat request can have its own parameters to specify
heartbeat granularity.
This requirement does not specify a maximum number of concurrent heartbeat
registrants that the monitor can handle. However, if the monitor cannot
any additional registrants, the request will return a specific error so the
will know this.
The application heartbeat service requires a registrant to specify a unique
identifier upon registration. If the given identifier is not unique, an
error will be
returned. The registrant may use its PID or choose some other system-unique
value. The latter necessary if a single process wishes to register for

2. Explain how you think the project you have picked meets the above

The project implements all of the above requirements, in addition, it
provides persistence of registration information if, for some reason, the
service goes down.  During this time, if an application hangs or crashes,
when the service is restarted, it will detect the application failure.

3. Explain the design of your project or point to a document on the web
that explains the design.

The documentation is in the form of doxygen comments within the code and may
be extracted using "make docs" (you must have doxygen on your system).  You
can also go to http://sourceforge.net/projects/appheartbeatmon. 

4. Pointer to your code/patch.

The latest code (revision 12) is available from anonymous CVS access as
explained on the sourceforge website.  You can also obtain a copy of the
code from components/AppHeartbeatMonitor directory in CVS on

Andrea Brugger
Software Engineer
Intel Corporation -- Telecom Software Programs

This email message does not represent or express the opinions of Intel
cgl_discussion mailing list
cgl_discussion at lists.osdl.org

More information about the cgl_discussion mailing list