Skip to content

NMS-19449: Daemon configuration docs - #8992

Closed
joseanesONMS wants to merge 8 commits into
developfrom
jira/NMS-19449-daemon-config-docs-smoke
Closed

joseanesONMS wants to merge 8 commits into
developfrom
jira/NMS-19449-daemon-config-docs-smoke

Conversation

@joseanesONMS

@joseanesONMS joseanesONMS commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Documents the daemon configuration and reloads, split out of #8984; content checked against the code on develop, one commit per ticket.

Ticket Topic Page(s) added/changed Source of truth
NMS-20473 Correct CORE_SERVICE_*_ENABLED names reference/…/daemons/introduction.adoc service-configuration.xml.tmpl, service-configuration.xml
NMS-16398 Reloads after package filter changes operation/…/daemon-config-files.adoc and links PollerEventProcessor.java, Collectd.java, SnmpPoller.java, ThresholdingServiceImpl.java
NMS-19449 Trapd configuration in the database and its page reference/…/daemon-config-files/trapd.adoc, snmp-traps.adoc, core-docker.adoc DefaultTrapdConfigDao.java, changelog-cm/36.0.0, ui/src/components/TrapdConfiguration/*
NMS-14422 Deleting device configuration backups (REST) operation/…/device-config-backup/dcb.adoc DeviceConfigRestService.java

Corrections to existing docs (separate NMS-19449: Fix … commits, each can be dropped on its own)

Topic Change Source of truth
Reportd, Tl1d, TL1 events Pages and remaining mentions removed: the daemons cannot be enabled on develop ServiceConfiguration.mergeWithDefaults(), defaults service-configuration.xml
Info REST example No Reportd in the services map InfoRestService.java
Meta-data page Trapd entry reflects database-stored configuration TrapdConfigFactory.java

Not addressed

  • NMS-10411: there is no reloadable attribute on develop; the code (NMS-10350) is unmerged.

The docs build adds no warnings (develop's two existing ones remain).

External References

The daemon table listed CORE_SERVICE_ENLINKD_ENABLED instead of CORE_SERVICE_ENHANCEDLINKD_ENABLED, a variable for Eventd that has no effect, and rows for the removed Reportd and Tl1d daemons. The names now match etc/service-configuration.xml and the container confd template exactly.
Pollerd, Collectd, SnmpPoller, and the thresholding service evaluate package filters only when they schedule an interface, and the docs did not say that a filter change needs a reload or restart. The new section lists, per daemon, what a reload re-evaluates and which node events trigger a partial re-evaluation, based on PollerEventProcessor, Collectd, SnmpPoller, and ThresholdingServiceImpl.
…ation page

The trapd pages still described trapd-configuration.xml as a live file, although the configuration now lives in the database and is managed through the Trap Configuration page and /api/v2/trapd. The trapd reference now covers the one-time import, the reload behavior, and the three tabs of the page, based on DefaultTrapdConfigDao, the 36.0.0 changelog-cm, Trapd, and ui/src/containers/TrapdConfiguration.vue.
The DCB pages did not say how to delete a backup. The Device Configs page has no delete action on develop (NMS-14276 is open), so the new section covers the DELETE endpoints of DeviceConfigRestService and their effect on the Device Configs list.
…pages

Both services were dropped from service-configuration.xml (NMS-18164, NMS-18169) and are absent from defaults/service-configuration.xml, so ServiceConfiguration.mergeWithDefaults() ignores any entry that tries to enable them.
Trapd reads its configuration from the database through TrapdConfigDao (TrapdConfigFactory), not from trapd-configuration.xml, and Trapd.interpolateUser() resolves the SNMPv3 user fields with a SecureCredentialsVaultScope only.
The Manager starts only services that ServiceConfiguration.mergeWithDefaults() keeps, and Tl1d is absent from defaults/service-configuration.xml with no Karaf feature to start it, so TL1 reception cannot be enabled.
InfoRestService reports the services that Manager.status() takes from ServiceConfigFactory, which no longer includes Reportd since it was dropped from defaults/service-configuration.xml.
@joseanesONMS

Copy link
Copy Markdown
Contributor Author

Reopened as #9002 from a branch without the -smoke suffix; this PR is docs-only, so it doesn't need a smoke run.

@joseanesONMS
joseanesONMS deleted the jira/NMS-19449-daemon-config-docs-smoke branch October 22, 2026 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant