このページは、まだ日本語ではご利用いただけません。翻訳中です。
Looking for the plugin's configuration parameters? You can find them in the HTTP Log configuration reference doc.
The HTTP Log plugin lets you send request and response logs to an HTTP server.
It also supports stream data (TCP, TLS, and UDP).
Queueing
The HTTP Log plugin uses internal queues to decouple the production of
log entries from their transmission to the upstream log server. In
contrast to other plugins that use queues, it shares one queue
between all plugin instances that use the same log server parameter.
The equivalence of the log server is determined by the parameters
http_endpoint
, method
, content_type
, timeout
, and keepalive
.
All plugin instances that have the same values for these parameters
share one queue.
Queues are not shared between workers and queueing parameters are scoped to one worker. For whole-system capacity planning, the number of workers need to be considered when setting queue parameters.
Kong process errors
This logging plugin logs HTTP request and response data, and also supports stream data (TCP, TLS, and UDP).
The Kong process error file is the Nginx error file. You can find it at the following path:
{prefix}/logs/error.log
Configure the prefix in
kong.conf
.
Get started with the HTTP Log plugin
- Configuration reference
- Basic configuration example
- Log format
- Custom fields and headers
- Configure HTTP Log to send logs to Splunk