Avoid piggybacking

Hi,

I like the idea of piggybacked data, but sometimes it’s unwanted. A lot of plugins make use of it, but often I’m confronted with the request to have the information centralized on one host, most of the time, the retrieving one.
Is there a simple way to ignore piggyback stanzas, without rewriting the plugin or putting a wrapper around it, to delete them?
I also don’t want to ignore piggybacked data in general, just for certain hosts/plugins/sections.

BR
Benjamin

You can ignore piggyback data on a per destination host basis by disabling piggyback data processing in the host properties.

The piggyback sender (e.g. the vSphere special agent) is the “decider” how to process or present the piggybacked data. Sometimes it is possible to configure a little bit in its settings. Sometimes it does not make sense to change it.

BTW: I would love to see an automatically generated service label for the piggybacked services. This way one could see which service is “original” and which was piggybacked.

6 Likes

Oh, I like that last point. That seems useful.

3 Likes

thanks for the tip. Sometimes the destination host is not even monitored, for reasons…
I thought about “Hostname translation for piggybacked hosts” rule - writing it back to the original host. But that would be only an ugly workaround.

Pay attention that you do not rewrite too much and piggyback data doubles or triples itself. This could lead to unwanted effects.

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.