pcp
[Top] [All Lists]

Re: [pcp] PCP / Zabbix Agent Loadable Module

To: myllynen@xxxxxxxxxx
Subject: Re: [pcp] PCP / Zabbix Agent Loadable Module
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 5 Nov 2015 18:20:09 -0500 (EST)
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <563099A2.8040901@xxxxxxxxxx>
References: <563099A2.8040901@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: TGMMw9fquk7iq+hmDIPLZVkw9rPVVw==
Thread-topic: PCP / Zabbix Agent Loadable Module
Hi Marko,

----- Original Message -----
> [...]
> 
> - pmNewContext(PM_CONTEXT_LOCAL, "") of course works as expected from
> standalone clients but seems to fail from the DSO. This means that the

Can you paste the failure message somewhere?  (in case I can't get it
to work, below)  Off the top of my head I don't know why it would fail
in local context mode.

> What do you think, could this live in pcp.git?

Maybe - there seems to be alot of conceptual overlap between this and
the "pmrep -o zabbix ..." kind of approach - I suspect we should focus
on doing one way well rather than both?

How stable is the Zabbix module API/ABI?  Are those headers available
in distribution builds etc?

> An easy way to test this is to install just the Zabbix agent (e.g. from
> [2]) 

Done that - I'm missing a bit of the recipe here though: where do the
Zabbix headers come from?  (needed for compiling zbxpcp.c).  And once
I have that built, how do I inform Zabbix agent?  Taa.

> and then do something like "zabbix_agentd -p | grep pcp".
> 

(I have "zabbix_agentd -p" working, but obviously not the bridge part
yet, so no "pcp" found just yet).

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>