We are a long term eHealth/Spectrum customer and is now in the process of moving to CAPM. What I have noticed is that the info being forwarded from CAPM towards Spectrum for events/alarms is lacking some variables compared to the eHealth-Spectrum integration. In particular Element Alias.
We are currently forwarding alarms from both eHealth and CAPM towards Spectrum. For the example below we see an alarm on an interface to much errors.
From eHealth we see these variables in the alarm details in Spectrum
Element Name - Switch-FastEthernet0/9
Element Alias - Switch-This-Has-Been-Modified-for-human-readable-purposes
From CAPM we see only the ItemName variable in the alarm details in Spectrum that describes the item/element details.
We modify InterfaceNameAlias in CAPM PC in the same manner as we have done with eHealth. For the CAPM alarm in Spectrum the NOC has to do further digging into CAPM (follow the URL listed in Alarm Details in the alarm and log into CAPM) to get more information. As opposed to the eHealth alarm where the NOC has more "human readable information" available directly in the Alarm Details in Spectrum, and do not need to log into eHealth to decide further action. So CAPM adds an extra step for the NOC for all performance alarms.
CAPM has the following variables for describing an Item (interface in this case):
- Interface Name
- Interface Name Alias
For Devices (Routers/Switches/Servers etc) CAPM has these variables:
I would suggest to to enrich the CAPM-Spectrum integration with more information being passed from CAPM to Spectrum. The best would be to be able to have the opportunity in CAPM to choose which variables to pass to Spectrum. Or as a minimum add the variables mentioned above to the integration so that they are visible in Spectrum (at least InterfaceNameAlias and NameAlias fields).