DGARM Nagios Core - Infosys Kick-off Meeting Summary

Source video: Dgarm-Nagios-Core-infosys-Kick-off-Meeting-2026-07-10_11-30-52.mkv (19 min)

Summary

Kick-off call between the Infosys team and the Nagios/Tetra engineering lead to scope the migration of device monitoring from Nagios XI to Nagios Core for DGARM. The client (DGARM) already onboarded most devices in Nagios XI, but XI has a device-count limitation, so the remaining devices must be onboarded in Nagios Core instead.

Key points raised:

• Why Core, not XI: Nagios XI has a licensing/scale limit on host count; devices that don't fit are being pushed to a separate Nagios Core instance.
• Gaps vs. XI: Nagios Core ships without graphing (PNP4Nagios/RRD graphs need to be installed separately) and without a GUI-based host/config manager — XI's built-in config manager UI doesn't exist in Core. This has to be replaced with NagiosQL, which the team plans to deploy as the CCM (configuration/change manager) equivalent.
• Plugin parity: Plugins already compiled/working in XI are not guaranteed to run unmodified on Core — many will need to be recompiled and retested against Core's environment before use (explicitly called out for SNMP/MRTG-style and "Promise"-type plugins).
• Device scope: Three device categories — Windows, Linux/physical+virtual servers, and network devices (switches, routers, security appliances — WAF, sandbox, NetApp storage). Laptops are explicitly excluded from monitoring.
• Templatization plan: Existing XI templates will be copied over and reused in Core once NagiosQL is in place, rather than rebuilding host templates from scratch.
• Timeline estimate (given by the engineering lead):
  • ~1 week for base install/configuration of Nagios Core + NagiosQL + graphing.
  • +1 day to onboard one representative device per category (Windows, Linux, network).
  • +1 additional week of shadowing/handover so the client's own team can onboard the rest independently, with escalation back to the lead only for blockers.
  • Total: ~2 weeks to a working, handed-off state (target: by the 23rd/24th).
• Staffing plan: The lead's team works the weekend (Sat/Sun) on initial setup so the client's team can start hands-on Monday; the lead joins periodically to validate direction rather than doing hands-on work throughout.
• Access/logistics: Inventory list (Excel) to be shared/reused from the original XI onboarding. Remote access discussed — either a VPN for the vendor team (pending security-policy check with DGARM's VPN team) or a WebEx screen-share session with a client-side team member present at all times. VPN was called out as enabling faster, after-hours debugging.
• Next step agreed: Work starts Monday ~10:30–11:30, beginning with base installation.

Action items

Item	Owner	Notes
Share device inventory (Excel)	DGARM/client team	Reuse existing XI onboarding inventory, expect minor additions
Check VPN feasibility for vendor team	DGARM (security/VPN team)	Alternative: WebEx remote session with client rep present
Schedule Monday working session	Both	~10:30–11:30 start, install phase begins
Recompile/validate plugins for Core	Infosys engineering team	Plugins from XI are not guaranteed to work as-is

Source recording