View Connect Logs
Introduction
This guide explains how to access and query Connect application logs using Kibana. Connect uses two Elasticsearch data streams to store logs: flowserver-logs for flow-server logs and connect-services for other Connect services. Corresponding Kibana data views enable log exploration.
|
For Connect versions earlier than v1.26.0, logs from all Connect services except flow-server are stored in the |
Log Storage Architecture
Connect organizes logs into two Elasticsearch data streams, each with a corresponding Kibana data view:
| Data Stream | Component | Data View |
|---|---|---|
|
flow-server only |
|
|
Other Connect services |
|
Flow-server Logs
The flowserver-logs data view provides access to flow-server logs with flow-server specific fields. The following fields are useful when filtering logs:
-
appLog.contextMap.fs_flowId- Filter logs for a specific flow -
appLog.contextMap.fs_messageId- Filter logs for a specific message -
appLog.contextMap.fs_originalMessageId- Traces a message that has been split, distributed, or handed off.
The view is automatically created by the connect-kb-job Kubernetes job during Connect deployment. It is used for flow debugging and flow-server troubleshooting.
Access Logs
-
Sign in to Kibana.
-
In the left sidebar, select Discover.
-
Select the appropriate data view from the dropdown:
-
flowserver-logs- For flow-server logs. -
connect-services- For all other Connect services (use service filters to narrow down to specific services).
-
-
Set the time range in the top-right corner.
View Connect Service Logs (excluding flow-server)
To display logs for a specific Connect service in the connect-services data view, you can filter based on the service name. For example, to view logs for the connect-frontend service, use the following filter:
kubernetes.container_name.keyword : "connect-frontend" AND <additional query filters if needed>
This filter applies only to the connect-services data view, not to flowserver-logs.
|