Catch up on the latest product updates, best practices, and expert insights from the Checkmk Conference #12 – Watch the livestream recordings now
back to website

Werk #22512: Deprecation of NagVis

Component NagVis
Title Deprecation of NagVis
Date Oct 19, 2026
Level Prominent Change
Class New Feature
Compatibility Incompatible - Manual interaction might be required
Checkmk versions & editions
3.0.0b1
Not yet released 		Checkmk Community, Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT

NagVis is deprecated with Checkmk 3.0 and will be removed in Checkmk 3.1. Its successor is Checkmk Maps, which ships with every edition.

Timeline

  • Checkmk 3.0: NagVis still ships, but is switched off by default.
  • Checkmk 3.1: NagVis is removed. Move your maps to Checkmk Maps before you update to 3.1.

What changes with 3.0

The new omd config option NAGVIS controls whether the site Apache serves NagVis.

  • New sites start with NagVis switched off.
  • Updated sites keep NagVis switched on if they have at least one NagVis map. The demo maps shipped with NagVis don't count. Sites without own maps get NagVis switched off. This is decided once, during the first update from 2.5 to 3.0. If you change the option afterwards, your choice is kept.

To switch NagVis on or off yourself, run as site user:

omd stop
omd config set NAGVIS on
omd start

Checkmk Cloud doesn't ship NagVis, so the option doesn't exist there.

Moving your maps to Checkmk Maps

The update to 3.0 moves your NagVis maps into Checkmk Maps automatically:

  • Each map becomes a map of the first admin user, including its background and shapes. Maps that are part of NagVis rotation pools keep rotating.
  • A map is published to the same users who could see it in NagVis: to the roles that saw all NagVis maps, or to the contact groups that list the map. If both applied, the map goes to the contact groups, and the update output names the roles that no longer see it. If NagVis used its own user database, the maps stay private to the admin.
  • A map whose name is already taken is stored as <name>_legacy.
  • The update output lists per map what couldn't be carried over, for example GIF images, missing shapes, URL entries of rotation pools and the markers of geographical maps. A map that can't be read is retried on every update.

Each map is migrated only once. If you keep editing a NagVis map after it has been migrated, later updates don't migrate it again. NagVis maps you create after an update are migrated by the next update.

To import a NagVis map yourself, for example after editing it, open More actions > Import map... in the map list and upload the .cfg file from ~/etc/nagvis/maps/.

To the list of all Werks