Simplest options are:

1. Use wireshark to inspect the packets (if wireshark can't successfully
decode the packets, then you know there's a problem with how they're being
generated)
2. Fire up a standalone collectd server with the csv write plugin, and see
if any data is successfully written to csv files on disk.

It'd be worth checking the hawkular documentation to see what version of
collectd it's compatible with.

There were a couple of small changes between collectd 4 and 5 which could
cause hawkular to not decode the packets correctly.

On Sun, 27 Aug 2017 at 07:19, Mikhail Ramendik <m...@ramendik.ru> wrote:

> Hello,
>
> I apologize for a version of this email that was prematurely sent by
> mistake.
>
> I am trying to set up metric collection and storage with collectd and
> hawkular-services. As a start I just want to monitor the local host.
> So I have ptrans, a component of hawkular-services that can listen to
> the collectd prototol, running. It listens for collectd on UDP 25826.
>
> I can see a list of collectd metrics with "collectdctl listval", and I
> am getting meaningful results from these values with "collectdctl
> getval". But I am getting no metrics in hawkular-services. And ptrans
> does not log any connection from collectd.
>
> Of course it is possible that ptrans simply has no logging of such
> connections and the problem is elsewhere. But I need to troubleshoot
> this, and so I'd like to find out what collectd actually sends with
> the network plugin. How can I do this? Or is this not possible?
>
> Thanks!
>
> --
> Yours, Mikhail Ramendik
>
> Unless explicitly stated, all opinions in my mail are my own and do
> not reflect the views of any organization
>
> _______________________________________________
> collectd mailing list
> collectd@verplant.org
> https://mailman.verplant.org/listinfo/collectd
>
_______________________________________________
collectd mailing list
collectd@verplant.org
https://mailman.verplant.org/listinfo/collectd

Reply via email to