[1474] in Coldmud discussion meeting

root meeting help first previous next next in chain last in chain last

system monitoring

daemon@ATHENA.MIT.EDU (Tue Nov 16 21:05:18 1999 )

From: "Charles Lance Woodson" <AE-Wauric@aephirsden.com>
To: <coldstuff@cold.org>
Date: Tue, 16 Nov 1999 13:09:47 -0800
Reply-To: coldstuff@cold.org

This is a multi-part message in MIME format.

------=_NextPart_000_0125_01BF3033.DBA5BA40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Lately I've been adding and removing a lot of monitoring messaging to =
coldcore systems (CML compiler, setting system) at Aeternity so that I =
could easily see how they work.  The thought occured to me that a =
monitoring system might be helpful to others coming behind me that would =
likely wind up doing the same thing.  Before I go any further, let me =
ask if there is currently any monitoring system in place that I simply =
haven't discovered?

If the answer to that is no, does anyone have suggestions as to what the =
best concept for a monitoring system would be?  I was thinking of using =
@set to allow users to hook themselves into an event for the specific =
system.  The system itself would then need to be modified to send the =
appropriate messaging to users hooked to the event.  Would such a =
monitoring system be a major performance impactor?  If this isn't =
acceptable, what about simply sending .announce() calls from different =
systems to a monitoring $place?

Lance

------=_NextPart_000_0125_01BF3033.DBA5BA40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Lately I've been adding and removing&nbsp;a lot=20
of&nbsp;monitoring messaging to&nbsp;coldcore systems&nbsp;(CML =
compiler,=20
setting system) at Aeternity so that I could easily see how they =
work.&nbsp; The=20
thought occured to me that a monitoring system might be helpful&nbsp;to =
others=20
coming behind me that would likely wind up doing the same=20
thing.&nbsp;&nbsp;Before I go any further, let me ask if there =
is&nbsp;currently=20
any monitoring system in place that I simply haven't =
discovered?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>If the answer to that is no,&nbsp;does anyone have =
suggestions=20
as to what the best concept for a monitoring system would be?&nbsp; I =
was=20
thinking of using @set to allow users to hook themselves into an event =
for the=20
specific system.&nbsp;&nbsp;The system itself would then need to be =
modified to=20
send the appropriate messaging to users hooked to the event.&nbsp; Would =
such a=20
monitoring system be a major performance impactor?&nbsp; If this isn't=20
acceptable,&nbsp;what about simply sending .announce() calls from =
different=20
systems to a monitoring $place?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>Lance</FONT></DIV></BODY></HTML>

------=_NextPart_000_0125_01BF3033.DBA5BA40--