Issues

Grafana Panel Internal Server Error when lasteventid is Null for an Alarm when Using HELM

automation cleanUpRpStatusChanges that references removed action with same name remains in default vacuumd-configuration.xml configuration

Cleared alarms with closed ticket state not removed when using a hybrid approach

The behavior of the Ticketing API differs from older versions.

Issue clearning alarms since updgrade to 23.0.3

Situation Severity is not adjusted downward as related alarms clear

Harden Drools engine in alarmd

Alarmd Drools context logs constantly in DEBUG mode

Kafka Producer: Sync timing issues cause erroneous deletes

duplicate key exceptions in alarmd

Scheduled outages applies value "Null" when using type weekly

Move Alarm like attributes from event element to alarm-data

Optionally create new alarms when a problem reoccurs

Change in JMS NBI Date Format

Only increment the alarm count if the alarm type is not a resolving event.

Alarm Service Layer is needed for proper Alarm workflow

Add documentation for the Alarm Northbounders

The OpenNMS Web User Interface Has Experienced an Error

Normalize Alarm Data in Events Shipped with OpenNMS

deleting a BSM monitor while an alarm is active doesn't clear the alarm

Add capability to un-acknowledge an alarm on reduction

Invalid DB constraint on alarms table

PostgreSQL COALESCE function used in automation triggers is used inaccurately

Improve event processing rate in alarmd (for databases with high latency)

AMQP forwarders do not support AMQP 1.0.0

alarm-change-notifier feature fails to install due to missing dependencies

It should be possible to set different severities for nodeLostService depending on the service

DHCP monitoring issue

auto-acknowledge-alarm element does not work in notifd-configuration.xml

After OTRS Integration Cleared ticket was not delete

alarmd calls onEvent() multiple times events enriched by Drools

reloadDaemonConfig doesn't work fully for vacuumd

Northbounders implementation are not sending feedback events for reloadDaemonConfig

Programmable Northbounder Interfaces

AMQP features broken after Camel upgrade

reductionkey Should be Unique in Table memos

Acknowledging alarms with a huge Description causes error when the Alarm-change-notifier plugin is running

Alarms Page Enhancements - Sound and Flashing

Traps failing to be ingested by Elasticsearch

Elasticsearch integration avoid parm name conflicts for severity as integer

ES REST Forwarder: Allow configuration to be updated without restarting

JMS Northbounder ignores first-occurrance-only and sending as object message doesn't work

PSQL Exception When Acknowledging Alarms

es-rest: Allow a comma-separated list of Elasticsearch URIs

OpenNMS Loses Events if Elasticsearch is down

Use MappingJackson2MessageConverter for JMS Northbounder

Elasticsearch alarms integration improvements

es-rest: HTTP 201 is considered an error

Remove the opennms-elasticsearch-event-forwarder feature