Extension Packages (mkp) legacy paths

Checkmk Exchange
,
1

Hi

After writing an Extension the Packaged files are market as Legacy

  • Agent based plugins (Checks, Inventory): xyz_mon_sessions.py
  • Agents: special/agent_xyz_mon
  • Legacy check plugins: agent_xyz_mon
  • Libraries: python3/cmk/special_agents/agent_xyz_mon.py
  • Legacy GUI extensions: plugins/wato/xyz_mon.py

How can I identify the Legacy Part of the Extension?

1 Like
2

This is normal.

The plugin for the special agent has to be in $OMD_ROOT/local/share/checks/check_mk which is now the legacy path for check plugins. Same with the WATO plugin.

1 Like
4

do you have a idea why cmk --paths does not show the new path?

OMD[test-site]:~$ cmk  --paths  
Locally installed addons
  Locally installed checks                       : /omd/sites/test-site/local/share/check_mk/checks/
  Locally installed notification scripts         : /omd/sites/test-site/local/share/check_mk/notifications/
  Locally installed inventory plugins            : /omd/sites/test-site/local/share/check_mk/inventory/
  Locally installed check man pages              : /omd/sites/test-site/local/share/check_mk/checkman/
  Locally installed agents and plugins           : /omd/sites/test-site/local/share/check_mk/agents/
  Locally installed Multisite addons             : /omd/sites/test-site/local/share/check_mk/web/
  Locally installed PNP templates                : /omd/sites/test-site/local/share/check_mk/pnp-templates/
  Locally installed documentation                : /omd/sites/test-site/local/share/doc/check_mk/
  Locally installed localizations                : /omd/sites/test-site/local/share/check_mk/locale/
1 Like
5

Because it’s an old option?

6

They forgot to migrate that option from 1.6 to 2.x. In other words – it’s a bug.

7

Hmm, I don’t get it … the legacy path is the correct place ?