Performance Log Data :: Kloudfuse Docs
Performance Log Data
Finding Performance Logs
In the Logs UI, you can filter for the performance logs using either filter:
| Filter | What it selects |
|---|---|
source="kf-performance-log" |
All performance log entries across all services |
perf_log="true" |
Equivalent; matches the raw field written into each log entry |
Use source="kf-performance-log" as the base filter for all performance log queries.
What Is Captured
Every query from the following services is marked as a performance log.
service_name |
Query type |
|---|---|
query-service |
Metrics queries (PromQL). |
logs-query-service |
Log queries (FuseQL and LogQL) |
events-query-service |
Events queries |
trace-query-service |
Trace queries (TraceQL) |
rum-query-service |
Real User Monitoring queries |
Performance logs capture all query origins:
- User-initiated queries from the UI
- API queries from service accounts or external tooling
- Internal service-to-service calls
- Alert evaluations
Alert evaluation queries do not carry a user_email value. |
Facets
Performance log fields have the following Facets.
| Facet | Type | Description |
|---|---|---|
user_email |
string | Email of the user who issued the query. Empty for service-to-service calls and alert evaluation queries. |
duration_ms |
integer | End-to-end query duration in milliseconds, measured at the service boundary and including Pinot execution time. |
service_name |
string | The Kloudfuse query service that processed the request: query-service, logs-query-service, events-query-service, trace-query-service, rum-query-service. |
request_id |
string | Unique request identifier for cross-service correlation. |