Could you please tell me the general logic of how logstash-async processes logs?

[klin111]

Are logs first written into a db file and then sent to Logstash?
If so, is the logging to the db file done asynchronously?
Can the database-path be omitted, i.e., not specified in the configuration file?
I've noticed that omitting it leads to an error indicating that the database-path must be provided.
thanks
@bngsudheer @skwashd @rmihael @sarg @eht16

[skwashd]

@klin111 I'm not sure why you tagged on this issue.

I contributed a small patch about a decade ago to support TLS connections. I only dug into the internals enough to add the feature I needed. I haven't used this library for many year.

I'm unsubscribing myself from this issue, so I won't see any more followups.

[eht16]

@klin111

I will answer your questions only in short because the questions are already answered in detail in the documentation. In particular I recommend to read https://python-logstash-async.readthedocs.io/en/stable/about.html and https://python-logstash-async.readthedocs.io/en/stable/persistence.html.

Are logs first written into a db file and then sent to Logstash? If so, is the logging to the db file done asynchronously?

Yes and yes.

Can the database-path be omitted, i.e., not specified in the configuration file?

Simply set it to None to use an in-memory cache.

I've noticed that omitting it leads to an error indicating that the database-path must be provided.

What exactly did you, can you share your configuration?

[klin111]

@eht16

Thank you for sharing. I had configured it as: database_path="" or database_path=":memory:". However, later when I set it to: database_path="None", the error disappeared.