T.R | Title | User | Personal Name | Date | Lines |
---|
3269.1 | Try using the Data Collector | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Tue Jun 30 1992 10:25 | 23 |
| Aharon,
The DATA COLLECTOR AM will work for the things you mentioned.
There are sample procedures for monitoring disks and printer queues. I
have tried the disk monitoring procedure.
You can use the Data Collector AM to monitor just about anything,
including processes, user information, disks, etc.
The Data Collector only works with DECnet Phase IV right now.
You will have to write your own command procedure or program to be
run on the system you wish to monitor. This procedure/program gathers
the information, then ships it to the DECmcc node via the MCC_EVC_SINK
object in the DECnet database. The EVent Collector Sink process
running on the DECmcc node receives the event and sends it to DECmcc
where the Alarms FM takes over to report to you.
The Data Collector is only a monitoring utility. If you want to
use DECmcc to set user features, you will have to write your own Access
Module.
-Dan
|
3269.2 | What about writing his own AM? | TAV02::WINDER | Aharon Winder | Wed Jul 01 1992 04:32 | 11 |
| Hello
The customer wants to put the ALL management activities in one place
including the control and the monitoring so of course he has to develop his
own AM (especially for his own entities).
In this situation what is the answer to the customer question as I asked in
.0 ?
Thanks,
Aharon Winder
|
3269.3 | If they're entities, they want an agent | BLUMON::SYLOR | Architect = Buzzword Generator | Sun Jul 05 1992 22:48 | 11 |
| And for a different answer...
In most cases if he wants to manage a real entity, and that entity is an
application or something that runs on VMS or Ultrix or OSF/1, then I'd
recommend he write a Common Agent MOM. That's what VMS and Ultrix are
doing for system management.
The cases where a developer should be writing an Access Module are
almost always limited to legacy devices speaking ancient protocols.
Mark
|