- Mark C. Persiko, Network Engineer
- IT Division, Boulder Valley School District-----Original Message-----
From: Jakob Peterh�nsel [mailto:[EMAIL PROTECTED]
Sent: Friday, August 29, 2003 11:59 AM
To: Dartware Support
Cc: InterMapper Discussion
Subject: Vote for Map dependencies.Dear Dartware.. ;-)
You listened to customers, and added the Reference Point and Map Probe.
I would like to suggest an expansion of this feature: Map in-between dependencies.
Let me explain:
When the Reference point was introduced, someone suggested that the 'map probe' should be able to refer to a 'map' on the map itself, making it possible to 'expand' a 'device' - a map probe should be able to simply hold all the probes to a single device - indicating the state of the device in total (ping, SNMP, SMTP, POP3 etc..)
What I miss, is navigation, and a half-working shadow feature...
Now that we have Map Status and Reference Point, I would like to suggest the following:
[All this assume we are talking local - 127.0.0.1 - references]
Uplink Point:
If a map is referenced via a Map Probe, it should be able to specify an 'uplink point'.
This point should be the 'interconnection' reference to the Map Probe, allowing the reference point to 'drill-down' multiple maps!
This should be a one-to-one relation. If several maps have probes that reference the map, only one 'uplink' should be possible to each reference.
One benefit of this is, it would be possible to make 'uplink' navigation between the maps - natively or in the web interface.
Another benefit would allow the reference point to work multiple maps down, shadowing all devices on a link from the reference point to the actual map the device is on.
Map Probes as 'in-between-maps' links.
When using the Map Probe on local maps like suggested above, it should be possible to ignore the actual probe on the web reports.
Errors and Outages should not list the Map Probe status as it's only a link between maps.
Only reason to list the Map Probe in the reports, would be if the map the probe is actually monitoring is not responding/is unknown.
(Like it does today, but only as a comment in the PopUp!)
Hope this makes sense... otherwise feel free to ask for elaboration...
Yours,
____________________________________________
Jakob Peterh�nsel
Technical Engineer
Tel: +45 7022 1014
Fax: +45 7022 1013
Mob: +45 22 68 49 61
[EMAIL PROTECTED]
www.NetPoint.com
Title: Message
These sound like good ideas. Two comments:
1) Through InterMapper Web, the Uplink Point
can be done by clicking on the "Back" button. In the InterMapper Console interface, the Uplink Map
could be listed as an object on the child map.
2) I agree about Map Probes not being in Errors and
Outages, but maybe that depends on how one implements maps. It's possible
to have one InterMapper Server/Client that monitors a map of maps,
i.e., nothing but map probes. Such a map should produce Errors and
Outages in order to produce any output at all about what's
unreachable.
Thanks ,
Mark
- Vote for Map dependencies. Jakob Peterh�nsel
- Re: Vote for Map dependencies. Jeje
- Re: Vote for Map dependencies. Mark Persiko
- Re: Vote for Map dependencies. Jakob Peterh�nsel
