Comments (8)
the main reason of getting a reference to the input/output instance, is to be able to set properties or any other kind of future modification.
Note that when the end-user call flb_stop(ctx), the engine receives the message and it start releasing resources, internally it does an exit for all input/output instances associated to the main context.
The user never need to do an explicit release of the instances, all this happens in the background.
from fluent-bit.
Thank you for your comment.
I noticed that flb_ctx_t
already contains plugin instances.
the main reason of getting a reference to the input/output instance, is to be able to set properties or any other kind of future modification.
So, why should we expose a plugin instance ?
User passes these instances to flb_*put_set
as identifier.
I think structure of instance is not necessarily need, only identifier value is needed.
The user never need to do an explicit release of the instances, all this happens in the background.
I understand. But I think it is odd from user side.
Because flb_stop(ctx)
doesn't contain plugin instances at first sight.
However this function influences plugin instances.
This means fluent-bit treats these instances as part of context implicitly.
So , I proposed that plugin instances should be hid from user and modify API.
flb_input_set( input_ins, ... )
-> flb_input_set( input_id, ctx, ... )
from fluent-bit.
I am thinking about this, no strong opinion yet, once I finish buffering/scheduling stuff I will focus on API and share more updates.
from fluent-bit.
I see, I'm waiting.
Thanks!
from fluent-bit.
I am reviewing this. I think it make sense to have an integer as identifier, thanks for pointing that.
from fluent-bit.
@nokute78 I have pushed the changes into api_ffd branch.
note: the remaining part are tests.
from fluent-bit.
I just migrated all tests/examples, changes rebased on master.
If is there anything pending or something not working as suggested please add your comments to this tickets.
from fluent-bit.
Amazing!! That's what I imagined!
Thanks.
from fluent-bit.
Related Issues (20)
- foward-to-forward network connections cause a huge memory leak on the server side HOT 2
- Fluent-bit OOM on Tail Input while assembling big CRI log lines in Kubernetes
- Add FIPS endpoint support for AWS S3 Output Plugin
- multiline parsing does not work when parser is used
- GBK Test Data Handling Issue
- flush_timeout of multiline parser does not reset the state machine HOT 1
- could not set systemd collector for Node Exporter Metrics plugin HOT 1
- Fluent-bit Match not working except for * HOT 1
- 2 connections are set up while sending logs to Loki HOT 2
- Hot reload issues
- Fluentbit keeps storage chunks busy, until the point we lose input logs, without notice. HOT 2
- Metrics report dropped logs with no other metrics indicating errors
- not able to upload logs from Fluentbit to OTelcollector HOT 4
- Influxdb output does not handle integer value correctly HOT 1
- Elasticsearch Output Plugin: Add support for following http redirects
- flb-pipeline worker CPU stays high even when there is no input or output events. HOT 2
- gelf output plugin creates invalid GELF messages from JSON arrays parsed in kubernetes filter
- fluentbit.io/parser not working with nginx if not correct tag HOT 5
- Unable to forward logs of Jobs and Cronjob from EKS to Opensearch
- mem buf overlimit - Potential deadlock HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fluent-bit.