HTTP RPC enables you to manage your Fluentd instance through HTTP endpoints. You can use this feature as a replacement of Unix signals.

It is especially useful for environments where signals are not supported well e.g. Windows. This requires Fluentd to start not with --no-supervisor command-line option.


By default, HTTP RPC is not enabled. To use this feature, set the rpc_endpoint option:


Now, you can manage your Fluentd instance using an HTTP client:

$ curl

As evident from the output above, each endpoint returns a JSON object as its response.

HTTP Endpoints


Replacement of



Stops the daemon.


Stops the daemon.


Flushes buffer and stops the daemon.


Flushes the buffered messages.


Reloads configuration.


Reloads configuration.

If this article is incorrect or outdated, or omits critical information, please let us know. Fluentd is an open-source project under Cloud Native Computing Foundation (CNCF). All components are available under the Apache 2 License.

Last updated