Question to piggyback configuration

[Man-in-Black (Sascha)]

CMK version: 2.0.0p18
OS version: Ubuntu 20.04.3

Hi there,

I have a question about piggyback data:
I built a local check on my local CheckMK server and it is also displayed correctly on the local server.
But now I would like to display the check on another host.

How exactly can I do this?

Thank you.

Best regards
Man-in-Black

[ricardoftribeiro (Ricardo Ribeiro)]

The output of your local check should look like this
<<<< hostname>>>>
<<< local>>>
script output

Notice the 4 <<<< instead of 3 for “marking” the hostname that you will piggyback to.
Trim the initial blank space

[Man-in-Black (Sascha)]

@ricardoftribeiro

<<<< hostname>>>>
<<< local>>>
script output

This works like a charm, Thank you very much

[r.sander (Robert Sander)]

@ricardoftribeiro

<<<< hostname>>>>
<<< local>>>
script output

SNMP Error, Agent OK - #4 by robin.gierse

[Man-in-Black (Sascha)]

Ok I just discovered a little problem.

Since i put in the 4 <<<< , all data pardes after this section will be put to the piggyback host.
Is there a way to stop this?

It’s lookling like this:

<<<omd_info:sep(59)>>>
[versions]
version;number;edition;demo
2.0.0p19.cre;2.0.0p19;cre;0
[sites]
site;used_version;autostart
xxx;2.0.0p19.cre;1
<<<local:sep(0)>>>
<<<<PIGGYBACKHOST>>>>
<<<local>>>
blabla
<<<fail2ban>>>
Detected jails:         sshd
Status for the jail: sshd
|- Filter
|  |- Currently failed: 0
|  |- Total failed:     0
|  `- File list:        /var/log/auth.log
`- Actions
   |- Currently banned: 0
   |- Total banned:     0
   `- Banned IP list:
<<<apt:sep(0)>>>
Inst ubuntu-advantage-tools [27.5~20.04.1] (27.6~20.04.1 Ubuntu:20.04/focal-updates [amd64])
Inst libdrm-common [2.4.105-3~20.04.2] (2.4.107-8ubuntu1~20.04.1 Ubuntu:20.04/focal-updates [all])
Inst libdrm2 [2.4.105-3~20.04.2] (2.4.107-8ubuntu1~20.04.1 Ubuntu:20.04/focal-updates [amd64])

All parts after the PIGGYBACKHOST are now not shown on the host itself but on the mentioned host.

Thanks.

edit: Ok I think i managed it with adding “<<<<>>>>” at the end of each section.