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

HTTP Input #18

Closed
edsiper opened this issue Jun 17, 2015 · 16 comments
Closed

HTTP Input #18

edsiper opened this issue Jun 17, 2015 · 16 comments

Comments

@edsiper
Copy link
Member

edsiper commented Jun 17, 2015

support HTTP input, payload as JSON or MessagePack.

note: work in process.

@edsiper edsiper added this to the 0.1 milestone Jun 17, 2015
@edsiper
Copy link
Member Author

edsiper commented Jul 1, 2015

Work in process:

0bca1e0 lib: monkey: upgrade http stack
29abd99 in_http: fix static linking and start server for testing purposes
f600c1e lib: monkey: scheduler timeout improvement / updates on exception handling and general reports by Coverity tool
613720f in_http: handle HTTP server setup, custom C headers and config
bc2757a in_http: fix linking to http library
a2ee8dc Build: fix configuration override for in_http (monkey lib)
0144c08 in_http: add plugin skeleton files
7f564d2 in_http: merging HTTP server and working in plugin
3ab208c Merge branch 'master' into http
7fd3c10 mk_core: upgrade to newer version used in Monkey Server
3e731e9 in_http: prepare build system

@Globegitter
Copy link

Globegitter commented Jul 31, 2017

@edsiper Does fluent-bit now support json input over http? Couldn't find anything in the docs.

@edsiper
Copy link
Member Author

edsiper commented Jul 31, 2017

@Globegitter not yet

@felixzh2020
Copy link

@edsiper Do you have a plan to support json input over http? Work in process now?

@StevenACoffman
Copy link
Contributor

StevenACoffman commented Jun 28, 2018

Supporting in_http might be very useful for property-based testing purposes. If we could input and output both via HTTP, we could specify a configuration (like a filter) and some "For All" (∀) expectations or rules. This lets you generate input to find obscure bugs, then reduce to minimal failing input. In C, I believe theft is the most mature.

@felixzh2015 What is your use case for in_http?

@ashleyschuett
Copy link

Is there any progress with this? or is there a way I can assist with getting this feature in?

@faisal-khalique
Copy link

Will this be available anytime soon please? I checked the current version 1.1.2 still has http input set to No.

fujimotos pushed a commit to fujimotos/fluent-bit that referenced this issue Jul 22, 2019
output: file: add documentation for out_file
@mvlbarcelos
Copy link

Hi Fluentbit team,

Is the http input already available?

Best Regards,
Marcus Barcelos

@majoyz
Copy link

majoyz commented Jun 18, 2020

Is there still any plan on in_http?

allamand pushed a commit to allamand/fluent-bit that referenced this issue Oct 26, 2020
@edsiper
Copy link
Member Author

edsiper commented Nov 26, 2020

it's coming, first PoC:

@edsiper edsiper self-assigned this Nov 26, 2020
@edsiper edsiper modified the milestones: 0.1, Fluent Bit v1.7 Nov 26, 2020
edsiper added a commit that referenced this issue Jan 7, 2021
edsiper added a commit that referenced this issue Jan 8, 2021
@agup006
Copy link
Member

agup006 commented Feb 19, 2021

it's here! We get to close this one out

in_http is available in 1.7.0, note: the doc site had some issues and we expect the in_http documentation to be available by end of the week.

@agup006 agup006 closed this as completed Feb 19, 2021
@DrackThor
Copy link

Can you give an update on the docs @agup006 ? Is the input ready to be used (in 1.7.x)?
Thanks in advance :)

@agup006
Copy link
Member

agup006 commented Mar 29, 2021

Docs were published here https://docs.fluentbit.io/manual/pipeline/inputs/http @DrackThor

@DrackThor
Copy link

Docs were published here https://docs.fluentbit.io/manual/pipeline/inputs/http @DrackThor

sorry, my bad - thanks for the hint!

@agup006
Copy link
Member

agup006 commented Mar 29, 2021

No apologies needed @DrackThor :) glad I could help - let us know your feedback

@popaconsta
Copy link

Does this plugin handle well many incoming requests (i.e. hundreds or even thousands of applications writing to the same endpoint where Fluent Bit is listening)? As fare as I am aware there is no way no configure the number or workers or anything like that. Thanks in advance to whoever can shed some light.

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

No branches or pull requests