{"id":2304,"date":"2019-11-18T10:06:17","date_gmt":"2019-11-18T09:06:17","guid":{"rendered":"https:\/\/www.aixpertsoft.de\/?post_type=product&p=2304"},"modified":"2023-09-27T16:41:38","modified_gmt":"2023-09-27T14:41:38","slug":"bsm-monitoring","status":"publish","type":"product","link":"https:\/\/www.aixpertsoft.de\/en\/product\/aixboms-specials\/bsm-monitoring\/","title":{"rendered":"Monitoring NSM"},"content":{"rendered":"
\n\t
\n\t\t
\n\t\t\t

The range of NSM systems in use at companies and authorities is diverse \u2013 from open source to major manufacturers, from isolated to fully integrated. With the AixBOMS-BSM application, we have already created a powerful environment for service modelling and structural analysis. By integrating NSM systems or scripts, the goal of a continuous and overarching BSM console can be achieved, namely a connection of service, configuration, and monitoring.<\/p>\n

 <\/p>\n

Following service planning and modelling (catalogue), the Configuration Items associated with the service must be integrated into system monitoring. Difficulties arise here due to system media breaks. The AixBOMS BSM.NSM module supports your technicians in configuring and creating monitoring elements, scenarios, and commands, and rolls these out to the NMS system (provisioning).<\/p>\n\n\t\t<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>

\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n\t
\n\t\t
\n\t\t\t

Service catalogue, NMS elements and condition chart<\/h3>\n

Service catalogues and elements or Configuration Items can be graphically mapped to NMS elements, thereby being embedded in the monitoring. The Condition Chart graphically evaluates incidents (alarms). Pre-configured atomic commands can be grouped into templates to form specific system groups or incident groups (e.g. \u201eWindows Server \u2013 Criticality Level 1\u201c). Rollout (activation) then takes place automatically.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>

\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n

<\/div><\/div>\n\t
\n\t\t\n\t\t
\n\t\t\t
\"\"<\/div>
Monitoring NSM: NSM Host and Related Physical Server<\/figcaption>\n\t\t<\/figure>\n\t<\/div>\n\n

<\/div><\/div><\/div><\/div><\/div><\/div>
<\/div>
\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n\t
\n\t\t
\n\t\t\t

Provisioning: Assignment of Monitoring Criteria<\/h3>\n

Incidents (alarms) that occur are pre-filtered according to specifications and can be displayed graphically and alphanumerically, or stored separately as a logbook entry (basic protection or emergency manual). A notification or escalation mechanism governs further distribution or dispatch (e.g. email, SMS).<\/p>\n\n\t\t<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>

\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n

<\/div><\/div>\n\t
\n\t\t\n\t\t
\n\t\t\t
\"\"<\/div>
Monitoring NSM: Dashboard<\/figcaption>\n\t\t<\/figure>\n\t<\/div>\n\n

<\/div><\/div><\/div><\/div><\/div><\/div>
<\/div>
\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n\t
\n\t\t
\n\t\t\t

Alarming and Impact Analysis<\/h3>\n

It is important when single alerts occur from monitoring consoles to be able to determine and recognise the impact on involved services and business services. Graphical analyses (Impact) help to show system-side effects and thus, in critical cases, to identify redundancies or bottlenecks, or to reconfigure affected and disrupted services.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>

\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n

<\/div><\/div>\n\t
\n\t\t\n\t\t
\n\t\t\t
\"\"<\/div>
NSM Monitoring: Hierarchy Editor with Status Information<\/figcaption>\n\t\t<\/figure>\n\t<\/div>\n\n

<\/div><\/div><\/div><\/div><\/div><\/div>
<\/div>
\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n\t
\n\t\t
\n\t\t\t

Highlights<\/h3>\n\n\t\t<\/div>\n\t<\/div>\n\n

<\/div><\/div>\n\t
\n\t\t
\n\t\t\t