8000 Update README.rst · fluent/fluent-logger-python@da4c73a · GitHub
[go: up one dir, main page]

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit da4c73a

Browse files
committed
Update README.rst
1 parent 06dac3e commit da4c73a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -353,8 +353,8 @@ the thread, unless forcibly killed.
353353
In some applications it can be especially important to guarantee that the logging process won't block under *any*
354354
circumstance, even when it's logging faster than the sending thread could handle (_backpressure_). In this case it's
355355
possible to enable the `circular queue` mode, by passing `True` in the `queue_circular` parameter of
356-
``asyncsender.FluentSender``. By doing so the thread doing the logging won't block even when the queue is full, the
357-
new event will be added to the queue by discarding the oldest one.
356+
``asyncsender.FluentSender`` or ``asynchandler.FluentHandler``. By doing so the thread doing the logging won't block
357+
even when the queue is full, the new event will be added to the queue by discarding the oldest one.
358358

359359
**WARNING**: setting `queue_circular` to `True` will cause loss of events if the queue fills up completely! Make sure
360360
that this doesn't happen, or it's acceptable for your application.

0 commit comments

Comments
 (0)
0