-
I have this log line: {"level":"INFO","loggerName":"logstash.agent","timeMillis":1662132959290,"thread":"Agent thread","logEvent":{"message":"Pipelines running","count":1,"running_pipelines":[{"metaClass":{"metaClass":{"metaClass":{"running_pipelines":"[:main]","non_running_pipelines":[]}}}}]}} …and this log format definition: Details{
"$schema": "https://lnav.org/schemas/format-v1.schema.json",
"logstash": {
"title": "Logstash JSON Log",
"file-pattern": "logstash-json\\.log",
"json": true,
"hide-extra": true,
"convert-to-local-time": true,
"line-format": [
{ "field": "__timestamp__" }, " ",
{ "field": "loggerName", "min-width": 30 }, " ",
{ "field": "level", "min-width": 5, "max-width": 5 }, " ",
{ "field": "logEvent/message" }, " ",
{ "field": "logEvent/path" }
],
"timestamp-field": "timeMillis",
"timestamp-divisor": 1000,
"level-field": "level",
"body-field": "logEvent/message",
"module-field": "loggerName",
"value": {
"timeMillis": { "kind": "integer" },
"loggerName": { "kind": "string" },
"level": { "kind": "string" },
"logEvent/message": { "kind": "string" },
"logEvent/path": { "kind": "string" }
},
"level": {
"fatal": "FATAL",
"error": "ERROR",
"warning": "WARN",
"info": "INFO",
"debug": "DEBUG|TRACE"
}
}
} The timestamp is
The log format definition specifies I'm seeing the same result with both Is this a bug in |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Yes, it's a bug. The local time conversion was only being done for textual time stamps. I've pushed a change that I think fixes the issue. |
Beta Was this translation helpful? Give feedback.
Yes, it's a bug. The local time conversion was only being done for textual time stamps. I've pushed a change that I think fixes the issue.