KHO THƯ VIỆN 🔎

Ebook Event management guide: Part 2

➤  Gửi thông báo lỗi    ⚠️ Báo cáo tài liệu vi phạm

Loại tài liệu:     PDF
Số trang:         106 Trang
Tài liệu:           ✅  ĐÃ ĐƯỢC PHÊ DUYỆT
 













Nội dung chi tiết: Ebook Event management guide: Part 2

Ebook Event management guide: Part 2

Chapter 12. Configuring event enrichmentYou can configure the way an event is processed as it passes through the Event Gateway.Configuring extra event

Ebook Event management guide: Part 2 t enrichmentYou can configure the Event Gateway to perform extra event enrichment. The following examples illustrate the kinds of information that can

be added to an event using event enrichment.You can configure the Event Gateway to populate any field in the Objectserver alerts.status table. You ca Ebook Event management guide: Part 2

n populate an existing field or a customized field.Note: The Event Gateway does not alter the alerts.status table. If you want to create a new field i

Ebook Event management guide: Part 2

n the alerts.status table and have the Event Gateway populate this new field, you must first alter the alerts.status table in the Objectserver to add

Chapter 12. Configuring event enrichmentYou can configure the way an event is processed as it passes through the Event Gateway.Configuring extra event

Ebook Event management guide: Part 2 configuring extra event enrichment then you might need to configure the Objectserver to add new fields to the alerts.stalus table.The following examp

les describe typical custom event enrichment. Each example specifies whether any alerts.status table configuration is required prior to configuring th Ebook Event management guide: Part 2

e custom event enrichment.Enriching a default event field that is not currently enrichedAn example of this is where you want to enrich the I’hysicall’

Ebook Event management guide: Part 2

ort alerts.stalus field. This is a field that exists by default in the alerts-stalus table, and therefore there is no need to modify the Objectserver.

Chapter 12. Configuring event enrichmentYou can configure the way an event is processed as it passes through the Event Gateway.Configuring extra event

Ebook Event management guide: Part 2 by one or more probes, and you want it populated for all events. In this example, some events that arrive via the monitor probe, from the poller, mig

ht have a populated EXTRAINFO_sysLocation field in the NCIM cache data. You have already added an NmosLocation field to the ObjectServer, and this fie Ebook Event management guide: Part 2

ld is populated from the monitor probe where possible. It can now be populated for all events. In this case there is no need to modify the Objectserve

Ebook Event management guide: Part 2

r.Performing any topology enrichment from the NCIM topology databaseIn this case you want to enrich the event with any of the data from NCIM. You must

Chapter 12. Configuring event enrichmentYou can configure the way an event is processed as it passes through the Event Gateway.Configuring extra event

Ebook Event management guide: Part 2 with main node device locationYou can configure event enrichment so that the location of the main node device associated with an event is added to a

field in the event.Consider which field in the Objectserver to populate. There already is a default Location field in the alerts.status table. This ex Ebook Event management guide: Part 2

ample assumes that you want to populate this field, unless it is already populated. If you have a reason to create a separate customized field to stor

Ebook Event management guide: Part 2

e the enriched location value, then you can add a field to the alerts.status table to store the main node device location; for example, NmosLocation.

Chapter 12. Configuring event enrichmentYou can configure the way an event is processed as it passes through the Event Gateway.Configuring extra event

Ebook Event management guide: Part 2 n node device associated with an event is available in the NC1.M topology database chassis table. This field can be accessed using NCIM cache, and is

held in the ncimCache.entityData table.For more information on the structure of NC1.M cache tables and fields, see the IBM Tivoli Network Manager IP E Ebook Event management guide: Part 2

dition Topology Database Reference.The following steps explain how to configure this extra event enrichment.1.Edit the Event Gateway schema file, $NCH

Ebook Event management guide: Part 2

OME/etc/preciSíon/ EventGatewaySchema.cfg, to allow the Event Gateway to update the new field. To do this, add the text in bold to the outgoing event

Chapter 12. Configuring event enrichmentYou can configure the way an event is processed as it passes through the Event Gateway.Configuring extra event

Ebook Event management guide: Part 2 config.ncp2nco(FieldFilter) ,values(["MnosCauseĩype*,"MnosDomainName*."NtnosEntityld”."MnosManagedStatus*."NmosObJInsf,"NmosSertal","Location"

Chapter 12. Configuring event enrichmentYou can configure the way an event is processed as it passes through the Event Gateway.Configuring extra event

Gọi ngay
Chat zalo
Facebook