It is possible to overload gf_lg/gf_msg to send events to local eventsd.
But we have to do additional parsing if we need to select the logs to
convert as events. If we introduce new API, then it is not different
from existing wrt adding events code in multiple places. But if it helps
in sharing the host/port and other information(which we are discussing
to support client events), I can give it a try(Move gf_event inside
logging infra)
regards
Aravinda
On Wednesday 24 August 2016 05:15 PM, Pranith Kumar Karampuri wrote:
Just resending in case you missed this mail.
On Tue, Aug 23, 2016 at 2:31 AM, Pranith Kumar Karampuri
<[email protected] <mailto:[email protected]>> wrote:
hi Aravinda,
I was wondering what is your opinion in sending selected
logs as events instead of treating them specially. Is this
something you guys considered? Do you think it is a bad idea to do
it that way? We can even come up with a new api which logs and
then sends it as event.
--
Pranith
--
Pranith
_______________________________________________
Gluster-devel mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-devel
