From f58bbe61289b26c6dcd6b1067a9cb6f059bffc45 Mon Sep 17 00:00:00 2001 From: Marshall Massengill Date: Fri, 13 Mar 2026 15:08:13 -0400 Subject: [PATCH] Adding a tip for UEI matching --- .../operation/pages/deep-dive/events/event-translator.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/modules/operation/pages/deep-dive/events/event-translator.adoc b/docs/modules/operation/pages/deep-dive/events/event-translator.adoc index 32b54d00ab61..f3f12cae89d1 100644 --- a/docs/modules/operation/pages/deep-dive/events/event-translator.adoc +++ b/docs/modules/operation/pages/deep-dive/events/event-translator.adoc @@ -11,6 +11,8 @@ If you would like to generate multiple events from a single source event, you ca The `$\{OPENNMS_HOME}/etc/translator-configuration.xml` file contains elements and attributes that create and/or change the fields or parameters of one event and publish a new event with these changes. +TIP: If the configured UEI in the event-translation-spec ends with a `/`, it acts as a prefix wildcard. Any event whose UEI starts with that prefix will match. IE, configuring `uei.opennms.org/nodes/` would match `uei.opennms.org/nodes/nodeDown`, `uei.opennms.org/nodes/nodeUp`, etc. + == Examples === Example 1: Associate traps with a node other than the SNMP manager