This document describes all log formats that Vector can automatically parse and extract metadata from.
Vector's Kubernetes log collector automatically detects and parses the following log formats:
Best practice: All applications should emit logs in JSON format for optimal parsing and querying.
Supported JSON field names (case-insensitive, multiple variants supported):
- Level:
level,severity,lvl - Message:
message,msg,text - Timestamp:
timestamp,time,ts,@timestamp - Trace ID:
trace_id,traceId - Span ID:
span_id,spanId - User ID:
user_id,userId - Request ID:
request_id,requestId - Error Type:
error_type,exception
Example JSON log:
{
"timestamp": "2026-02-23T05:50:32.047Z",
"level": "error",
"message": "Database connection failed",
"service": "flui-api",
"trace_id": "abc123def456",
"user_id": "12345",
"error_type": "DatabaseConnectionError"
}Extracted in Loki:
level=errortrace_id=abc123def456user_id=12345- Message =
Database connection failed
For applications that cannot be modified to use JSON, Vector supports these common text patterns:
[2026-02-23 05:50:32.047 ERR] User authentication failed
[2026-02-23 05:50:32.047 INF] Request processed successfully
[2026-02-23 05:50:32.047 WRN] High memory usage detected
Level mappings:
TRC→traceDBG→debugINF→infoWRN→warnERR→errorFTL→fatal
Loki label: level="error"
2026-02-23 05:50:32.047 ERROR [com.flui.api.UserService] - Connection timeout
2026-02-23 05:50:32.047 INFO [com.flui.api.Controller] - Request received
2026-02-23 05:50:32.047 WARN [com.flui.api.Database] - Slow query detected
Supported levels: TRACE, DEBUG, INFO, WARN, ERROR, FATAL
Loki label: level="error"
error: User authentication failed
info: Server started on port 3000
warn: Deprecated API endpoint called
Supported levels: trace, debug, info, warn, error
Loki label: level="error"
[2026-02-23 05:50:32] production.ERROR: Database connection failed
[2026-02-23 05:50:32] production.INFO: User logged in
[2026-02-23 05:50:32] production.WARNING: Cache miss
Supported levels: DEBUG, INFO, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY
Loki label: level="error" (normalized to lowercase)
time="2026-02-23T05:50:32Z" level=error msg="Connection failed"
time="2026-02-23T05:50:32Z" level=info msg="Service started"
time="2026-02-23T05:50:32Z" level=warn msg="Retrying request"
Supported levels: Any lowercase level keyword
Loki label: level="error"
Vector will attempt to extract log levels from any of these patterns:
[ERROR] Something went wrong
ERROR: Connection timeout
2026-02-23 05:50:32 WARN Connection slow
INFO - Processing request
Supported keywords: TRACE, DEBUG, INFO, WARN, WARNING, ERROR, FATAL, CRITICAL (case-insensitive)
Loki label: level="error" (normalized to lowercase)
After parsing, the following labels are available in Loki:
cluster_id- Cluster identifiercluster_name- Cluster nameserver_id- Server identifierhostname- Node hostnameservice- Service namesource_type- Source type (e.g.,kubernetes,journald)level- Log level (trace,debug,info,warn,error,fatal)
namespace- Kubernetes namespacepod- Full pod nameapp- Application name (extracted from pod name)container- Container namenode- Node hostnamestream- Output stream (stdout,stderr)
trace_id- Distributed tracing IDuser_id- User identifierrequest_id- Request identifier
# All errors from flui-api
{app="flui-api", level="error"}
# All logs from a specific user (requires JSON logging with user_id)
{app="flui-api", user_id="12345"}
# All warnings and errors from default namespace
{namespace="default", level=~"warn|error"}
# Trace a specific distributed transaction (requires JSON logging with trace_id)
{trace_id="abc123def456"}
# All stderr logs (errors typically go to stderr)
{stream="stderr"}
# Logs from specific pod
{pod="flui-api-846c4f5dcc-66fzc"}
Recommended Library: Pino
const pino = require('pino');
const logger = pino({
level: 'info',
formatters: {
level: (label) => ({ level: label })
}
});
logger.info({ userId: 123, traceId: 'abc123' }, 'User logged in');
// Output: {"level":"info","time":1708664432047,"msg":"User logged in","userId":123,"traceId":"abc123"}Alternative: Winston (configure JSON format)
NestJS v11+ (Native JSON Support - Recommended)
Starting from version 11, NestJS supports native JSON logging without additional dependencies:
import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
async function bootstrap() {
const app = await NestFactory.create(AppModule, {
logger: {
logLevels: ['log', 'error', 'warn', 'debug', 'verbose'],
json: true, // Enable JSON output
},
});
await app.listen(3000);
}
bootstrap();Output example:
{
"level": "info",
"timestamp": "2026-02-23T05:50:32.047Z",
"message": "User logged in",
"context": "UserService",
"userId": 123,
"traceId": "abc123"
}NestJS Pre-v11 (Use Pino)
For versions before v11, use nestjs-pino:
npm install nestjs-pino pino-httpimport { Module } from '@nestjs/common';
import { LoggerModule } from 'nestjs-pino';
@Module({
imports: [
LoggerModule.forRoot({
pinoHttp: {
level: process.env.NODE_ENV !== 'production' ? 'debug' : 'info',
transport: process.env.NODE_ENV !== 'production'
? { target: 'pino-pretty' }
: undefined,
serializers: {
req: (req) => ({
method: req.method,
url: req.url,
}),
},
},
}),
],
})
export class AppModule {}Usage in services:
import { Injectable, Logger } from '@nestjs/common';
import { PinoLogger } from 'nestjs-pino';
@Injectable()
export class UserService {
constructor(private readonly logger: PinoLogger) {
this.logger.setContext(UserService.name);
}
login(userId: number) {
this.logger.info({ userId, traceId: 'abc123' }, 'User logged in');
}
}Recommended Library: Serilog with JSON formatter
using Serilog;
using Serilog.Formatting.Json;
Log.Logger = new LoggerConfiguration()
.WriteTo.Console(new JsonFormatter())
.CreateLogger();
Log.Information("User {UserId} logged in", userId);Alternative: Use text format (automatically parsed by Vector)
Log.Logger = new LoggerConfiguration()
.WriteTo.Console(outputTemplate: "[{Timestamp:yyyy-MM-dd HH:mm:ss.fff} {Level:u3}] {Message:lj}{NewLine}")
.CreateLogger();Recommended Library: Logback with logstash-logback-encoder
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder class="net.logstash.logback.encoder.LogstashEncoder">
<includeMdc>false</includeMdc>
</encoder>
</appender>Alternative: Standard Logback format (automatically parsed by Vector)
Recommended Library: Monolog with JSON formatter
use Monolog\Logger;
use Monolog\Handler\StreamHandler;
use Monolog\Formatter\JsonFormatter;
$logger = new Logger('flui-api');
$handler = new StreamHandler('php://stdout', Logger::INFO);
$handler->setFormatter(new JsonFormatter());
$logger->pushHandler($handler);
$logger->info('User logged in', ['userId' => 123]);Alternative: Laravel's default format is automatically parsed by Vector
Recommended Library: structlog
import structlog
structlog.configure(
processors=[
structlog.processors.JSONRenderer()
]
)
logger = structlog.get_logger()
logger.info("user_logged_in", user_id=123, trace_id="abc123")Recommended Library: zap or zerolog
import "go.uber.org/zap"
logger, _ := zap.NewProduction()
defer logger.Sync()
logger.Info("User logged in",
zap.Int("userId", 123),
zap.String("traceId", "abc123"),
)Best Practices:
- Use JSON structured logging for all new applications
- Vector automatically parses common text patterns for legacy applications
- Leverage
level,trace_id,user_idlabels for powerful filtering capabilities - Multi-language support: .NET, Java, Node.js, PHP, Python, Go
Troubleshooting:
For questions or issues with log parsing, check /var/log/vector/vector.log on the node.