Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Way to pass OUTPUT context to the function FLBPluginFlush ? #5

Open
keyolk opened this issue Aug 1, 2017 · 8 comments
Open

Way to pass OUTPUT context to the function FLBPluginFlush ? #5

keyolk opened this issue Aug 1, 2017 · 8 comments

Comments

@keyolk
Copy link

keyolk commented Aug 1, 2017

I have problem that supporting multiple OUPUT target using custom plugin.
From that it needs to distinguish caller of FLBPluginFlush.

from C written plugin source code,
I can see the function "flb_output_set_context"

Is there similar method on golang ?
Or schedule to support ?

@edsiper
Copy link
Member

edsiper commented Aug 1, 2017

@keyolk there is no API for that at the moment. Make sense to add it. How urgent it is ?

@keyolk
Copy link
Author

keyolk commented Aug 1, 2017

@edsiper
Thanks.

If it takes long time.
It would be better to start changing my plugin to C based thing. : (
Hope it supports the API soon.

@edsiper
Copy link
Member

edsiper commented Aug 1, 2017

what kind of output plugin are you implementing ?

@keyolk
Copy link
Author

keyolk commented Aug 2, 2017

@edsiper
I have to send my logs through raw TCP based protocol.
Now I do copy&modify C based fluentd output plugin. : )

@jasonkeene
Copy link

I also need this. I have multiple [OUTPUT] sections for the same plugin, intending to send some messages to one destination and others to a different destination. Right now I don't see a way of telling what messages are intended to go to what destination when my FLBPluginFlush is called. Perhaps passing in the ctx to FLBPluginFlush?

@edsiper
Copy link
Member

edsiper commented Oct 24, 2018

update: if is there any volunteer to work on this feel free to ping me (quite busy now)

@jasonkeene
Copy link

jasonkeene commented Apr 17, 2019

@jasonkeene
Copy link

@edsiper This can be closed since #15 was merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants