Schema of LogEvent described below:
LogEvent:
utcOffset?: Long # Utc offset on 100ns ticks
level?: String # Log level, possible values are Debug, Info, Warn (Warning), Error, Fatal.
message?: String # Rendered message
messageTemplate?: String # Message template
exception?: Exception # Exception
stackTrace?: String # Exception tree string representation (stacktrace)
properties?: Properties # Key-value dictionary where values are primitives or string representation in case of object
Exception:
type?: String # Exception runtime type
message?: String # Exception message
innerExceptions?: Vector<Exception> # Inner exceptions
stackFrames?: Vector<StackFrame> # Exception stack frames
StackFrame:
function?: String # Name of function
type?: String # Type where function is declared
file?: String # File name
line?: Integer # Line number
column?: [Short, Integer] # Column number
Properties:
project?: String # Project name
subproject?: String # Subproject name
environment?: String # Environment
release?: String # Release version of application
traceId?: String or UUID # Trace identifier
fingerprint?: Vector<String> or String # Labels for grouping in Sentry
platform?: String # Platform of application
logger?: String # Logger which created the event
Tags properties/project
, properties/subproject
and properties/environment
are common tags.
- Elastic Sink processes LogEvent as described in its documentation