# Interface LogEvent

A data structure representing a log message, it represents the arguments passed to a logger statement, the level at which they were logged and the hierarchy of child bindings.

#### Description

By default serializers are not applied to log output in the browser, but they will always be applied to `messages` and `bindings` in the `logEvent` object. This allows us to ensure a consistent format for all values between server and client.

interface LogEvent {
ts: number;
messages: any[];
bindings: Bindings[];
level: {
label: string;
value: number;
};
}

- Defined in node_modules/pino/pino.d.ts:688

#####
Index

### Properties

ts
messages
bindings
level

##
Properties

### ts

ts: number

Unix epoch timestamp in milliseconds, the time is taken from the moment the logger method is called.

- Defined in node_modules/pino/pino.d.ts:692

### messages

messages: any[]

All arguments passed to logger method, (for instance `logger.info('a', 'b', 'c')` would result in `messages` array `['a', 'b', 'c']`).

- Defined in node_modules/pino/pino.d.ts:697

### bindings

bindings: Bindings[]

Represents each child logger (if any), and the relevant bindings.

#### Description

For instance, given `logger.child({a: 1}).child({b: 2}).info({c: 3})`, the bindings array would hold `[{a: 1}, {b: 2}]` and the `messages` array would be `[{c: 3}]`. The `bindings` are ordered according to their position in the child logger hierarchy, with the lowest index being the top of the hierarchy.

- Defined in node_modules/pino/pino.d.ts:705

### level

level: {
label: string;
value: number;
}

Holds the `label` (for instance `info`), and the corresponding numerical `value` (for instance `30`). This could be important in cases where client side level values and labels differ from server side.

- Defined in node_modules/pino/pino.d.ts:710