mirror of
https://github.com/tstack/lnav
synced 2024-11-15 18:13:10 +00:00
17 KiB
17 KiB
✘ error: invalid value for option “/bad_json_log/line-format#/timestamp-format”
reason: empty values are not allowed
--> {test_dir}/bad-config/formats/invalid-json-format/format.json:11
| "timestamp-format": ""
= help: Property Synopsis
/bad_json_log/line-format#/timestamp-format <string>
Description
The strftime(3) format for this field
⚠ warning: unexpected value for property “/bad-name-log/title”
--> {test_dir}/bad-config/formats/invalid-name/format.json:4
| "title": "bad-format",
= help: Available Properties
$schema The URI of the schema for this file
(\w+)/
⚠ warning: unexpected value for property “/bad-name-log/description”
--> {test_dir}/bad-config/formats/invalid-name/format.json:5
| "description": "Log format with a name that has invalid characters",
= help: Available Properties
$schema The URI of the schema for this file
(\w+)/
⚠ warning: unexpected value for property “/bad-name-log/json”
--> {test_dir}/bad-config/formats/invalid-name/format.json:6
| "json": true
= help: Available Properties
$schema The URI of the schema for this file
(\w+)/
✘ error: “invalid(abc” is not a valid regular expression
reason: missing closing parenthesis
--> /invalid_props_log/tags/badtag3/pattern
| invalid(abc
| ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-properties/format.json:36
| "pattern": "invalid(abc"
= help: Property Synopsis
/invalid_props_log/tags/badtag3/pattern <regex>
Description
The regular expression to match against the body of the log message
Example
\w+ is down
✘ error: “abc(def” is not a valid regular expression
reason: missing closing parenthesis
--> /invalid_props_log/search-table/bad_table_regex/pattern
| abc(def
| ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-properties/format.json:41
| "pattern": "abc(def"
= help: Property Synopsis
/invalid_props_log/search-table/bad_table_regex/pattern <regex>
Description
The regular expression for this search table.
✘ error: “^(?<timestamp>\d+: (?<body>.*)$” is not a valid regular expression
reason: missing closing parenthesis
--> /bad_regex_log/regex/std/pattern
| ^(?<timestamp>\d+: (?<body>.*)$
| ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-regex/format.json:6
| "pattern": "^(?<timestamp>\\d+: (?<body>.*)$"
= help: Property Synopsis
/bad_regex_log/regex/std/pattern <message-regex>
Description
The regular expression to match a log message and capture fields.
✘ error: “(foo” is not a valid regular expression
reason: missing closing parenthesis
--> pattern
| (foo
| ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-regex/format.json:13
| "error": "(foo"
= help: Property Synopsis
/bad_regex_log/level/error <pattern|integer>
Description
The regular expression used to match the log text for this level. For JSON logs with numeric levels, this should be the number for the corresponding level.
✘ error: “abc(” is not a valid regular expression
reason: missing closing parenthesis
--> /bad_regex_log/highlights/foobar/pattern
| abc(
| ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-regex/format.json:25
| "pattern": "abc("
= help: Property Synopsis
/bad_regex_log/highlights/foobar/pattern <regex>
Description
A regular expression to highlight in logs of this format.
⚠ warning: format file is missing “$schema” property
--> {test_dir}/bad-config/formats/invalid-regex/format.json
= note: the schema specifies the supported format version and can be used with editors to automatically validate the file
= help: add the following property to the top-level JSON object:
"$schema": "https://lnav.org/schemas/format-v1.schema.json",
✘ error: “foo” is not a valid value for option “/bad_sample_log/value/pid/kind”
--> {test_dir}/bad-config/formats/invalid-sample/format.json:24
| "kind": "foo"
= help: Property Synopsis
/bad_sample_log/value/pid/kind <data-type>
Description
The type of data in the field
Allowed Values
string, integer, float, boolean, json, struct, quoted, xml
✘ error: 'bad' is not a supported log format $schema version
--> {test_dir}/bad-config/formats/invalid-schema/format.json:2
| "$schema": "bad"
= note: expecting one of the following $schema values:
https://lnav.org/schemas/format-v1.schema.json
= help: Property Synopsis
/$schema The URI of the schema for this file
Description
Specifies the type of this file
✘ error: invalid line format element “/bad_json_log/line-format/0/field”
reason: “” is not a defined value
--> {test_dir}/bad-config/formats/invalid-json-format/format.json:7
✘ error: invalid pattern: “incomplete-match”
reason: pattern does not match entire message
--> {test_dir}/bad-config/formats/invalid-regex/format.json:20
| 1428634687123; foo
| ^ matched up to here
= note: incomplete-match = ^(?<timestamp>\d+);
= help: update the regular expression to fully capture the sample message
✘ error: invalid sample log message: "abc: foo"
reason: unrecognized timestamp -- abc
--> {test_dir}/bad-config/formats/invalid-sample/format.json:34
= note: the following custom formats were tried:
abc
^ “%i” matched up to here
= help: If the timestamp format is not supported by default, you can add a custom format with the “timestamp-format” property
✘ error: invalid sample log message: "1428634687123| debug hello"
reason: “debug” does not match the expected level of “info”
--> {test_dir}/bad-config/formats/invalid-sample/format.json:37
= note: matched regex = with-level
captured level = “debug”
level regular expression match results:
/bad_sample_log/level/debug = debug
debug
^---^
/bad_sample_log/level/info = info
no match
= help: Level regexes are not anchored to the start/end of the string. Prepend “^” to the expression to match from the start of the string and append “$” to match up to the end of the string.
✘ error: invalid pattern: “with-level”
reason: pattern does not match entire multiline sample message
--> {test_dir}/bad-config/formats/invalid-sample/format.json:41
= note: with-level = ^(?<timestamp>\d+)\| (?<level>\w+) (?<body>\w+)$
= help: use “.*” to match new-lines
✘ error: invalid sample log message: "1428634687123; foo bar"
reason: sample does not match any patterns
--> {test_dir}/bad-config/formats/invalid-sample/format.json:45
= note: the following shows how each pattern matched this sample:
1428634687123; foo bar
^ bad-time matched up to here
^ semi matched up to here
^ std matched up to here
^ with-level matched up to here
= note: bad-time = “^(?<timestamp>\w+): (?<body>\w+)$”
semi = “^(?<timestamp>\d+); (?<body>\w+)$”
std = “^(?<timestamp>\d+): (?<pid>\w+) (?<body>.*)$”
with-level = “^(?<timestamp>\d+)\| (?<level>\w+) (?<body>\w+)$”
⚠ warning: invalid pattern: “/bad_sample_log/regex/semi”
reason: pattern does not match any samples
--> {test_dir}/bad-config/formats/invalid-sample/format.json:10
= help: every pattern should have at least one sample that it matches
⚠ warning: invalid pattern: “/bad_sample_log/regex/std”
reason: pattern does not match any samples
--> {test_dir}/bad-config/formats/invalid-sample/format.json:7
= help: every pattern should have at least one sample that it matches
⚠ warning: invalid value “/invalid_props_log/value/non-existent”
reason: no patterns have a capture named “non-existent”
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
= note: the following captures are available:
body, pid, timestamp
= help: values are populated from captures in patterns, so at least one pattern must have a capture with this value name
✘ error: invalid tag definition “/invalid_props_log/tags/badtag”
reason: tag definitions must have a non-empty pattern
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: invalid tag definition “/invalid_props_log/tags/badtag2”
reason: tag definitions must have a non-empty pattern
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: invalid tag definition “/invalid_props_log/tags/badtag3”
reason: tag definitions must have a non-empty pattern
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: “invalid_props_log” is not a valid log format
reason: “subsecond-unit” must be set when “subsecond-field” is used
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: invalid value for property “/invalid_props_log/timestamp-field”
reason: “ts” was not found in the pattern at /invalid_props_log/regex/std
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
= note: the following captures are available:
body, pid, timestamp
✘ error: “not a color” is not a valid color value for property “/invalid_props_log/highlights/hl1/color”
reason: Unknown color: 'not a color'. See https://jonasjacek.github.io/colors/ for a list of supported color names
--> {test_dir}/bad-config/formats/invalid-properties/format.json:24
✘ error: “also not a color” is not a valid color value for property “/invalid_props_log/highlights/hl1/background-color”
reason: Unknown color: 'also not a color'. See https://jonasjacek.github.io/colors/ for a list of supported color names
--> {test_dir}/bad-config/formats/invalid-properties/format.json:25
✘ error: “no_regexes_log” is not a valid log format
reason: no regexes specified
--> {test_dir}/bad-config/formats/no-regexes/format.json:4
✘ error: “no_regexes_log” is not a valid log format
reason: log message samples must be included in a format definition
--> {test_dir}/bad-config/formats/no-regexes/format.json:4
✘ error: “no_sample_log” is not a valid log format
reason: log message samples must be included in a format definition
--> {test_dir}/bad-config/formats/no-samples/format.json:4
✘ error: failed to compile SQL statement
reason: near "TALE": syntax error
--> {test_dir}/bad-config/formats/invalid-sql/init.sql:4
| -- comment test
| CREATE TALE invalid (x y z);
| ^ near "TALE": syntax error
✘ error: failed to execute SQL statement
reason: ✘ error: “abc(” is not a valid regular expression
| reason: missing closing parenthesis
| --> arg
| | abc(
| | ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-sql/init2.sql
| SELECT regexp_match('abc(', '123')
| FROM sqlite_master;
reason: empty values are not allowed
--> {test_dir}/bad-config/formats/invalid-json-format/format.json:11
| "timestamp-format": ""
= help: Property Synopsis
/bad_json_log/line-format#/timestamp-format <string>
Description
The strftime(3) format for this field
⚠ warning: unexpected value for property “/bad-name-log/title”
--> {test_dir}/bad-config/formats/invalid-name/format.json:4
| "title": "bad-format",
= help: Available Properties
$schema The URI of the schema for this file
(\w+)/
⚠ warning: unexpected value for property “/bad-name-log/description”
--> {test_dir}/bad-config/formats/invalid-name/format.json:5
| "description": "Log format with a name that has invalid characters",
= help: Available Properties
$schema The URI of the schema for this file
(\w+)/
⚠ warning: unexpected value for property “/bad-name-log/json”
--> {test_dir}/bad-config/formats/invalid-name/format.json:6
| "json": true
= help: Available Properties
$schema The URI of the schema for this file
(\w+)/
✘ error: “invalid(abc” is not a valid regular expression
reason: missing closing parenthesis
--> /invalid_props_log/tags/badtag3/pattern
| invalid(abc
| ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-properties/format.json:36
| "pattern": "invalid(abc"
= help: Property Synopsis
/invalid_props_log/tags/badtag3/pattern <regex>
Description
The regular expression to match against the body of the log message
Example
\w+ is down
✘ error: “abc(def” is not a valid regular expression
reason: missing closing parenthesis
--> /invalid_props_log/search-table/bad_table_regex/pattern
| abc(def
| ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-properties/format.json:41
| "pattern": "abc(def"
= help: Property Synopsis
/invalid_props_log/search-table/bad_table_regex/pattern <regex>
Description
The regular expression for this search table.
✘ error: “^(?<timestamp>\d+: (?<body>.*)$” is not a valid regular expression
reason: missing closing parenthesis
--> /bad_regex_log/regex/std/pattern
| ^(?<timestamp>\d+: (?<body>.*)$
| ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-regex/format.json:6
| "pattern": "^(?<timestamp>\\d+: (?<body>.*)$"
= help: Property Synopsis
/bad_regex_log/regex/std/pattern <message-regex>
Description
The regular expression to match a log message and capture fields.
✘ error: “(foo” is not a valid regular expression
reason: missing closing parenthesis
--> pattern
| (foo
| ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-regex/format.json:13
| "error": "(foo"
= help: Property Synopsis
/bad_regex_log/level/error <pattern|integer>
Description
The regular expression used to match the log text for this level. For JSON logs with numeric levels, this should be the number for the corresponding level.
✘ error: “abc(” is not a valid regular expression
reason: missing closing parenthesis
--> /bad_regex_log/highlights/foobar/pattern
| abc(
| ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-regex/format.json:25
| "pattern": "abc("
= help: Property Synopsis
/bad_regex_log/highlights/foobar/pattern <regex>
Description
A regular expression to highlight in logs of this format.
⚠ warning: format file is missing “$schema” property
--> {test_dir}/bad-config/formats/invalid-regex/format.json
= note: the schema specifies the supported format version and can be used with editors to automatically validate the file
= help: add the following property to the top-level JSON object:
"$schema": "https://lnav.org/schemas/format-v1.schema.json",
✘ error: “foo” is not a valid value for option “/bad_sample_log/value/pid/kind”
--> {test_dir}/bad-config/formats/invalid-sample/format.json:24
| "kind": "foo"
= help: Property Synopsis
/bad_sample_log/value/pid/kind <data-type>
Description
The type of data in the field
Allowed Values
string, integer, float, boolean, json, struct, quoted, xml
✘ error: 'bad' is not a supported log format $schema version
--> {test_dir}/bad-config/formats/invalid-schema/format.json:2
| "$schema": "bad"
= note: expecting one of the following $schema values:
https://lnav.org/schemas/format-v1.schema.json
= help: Property Synopsis
/$schema The URI of the schema for this file
Description
Specifies the type of this file
✘ error: invalid line format element “/bad_json_log/line-format/0/field”
reason: “” is not a defined value
--> {test_dir}/bad-config/formats/invalid-json-format/format.json:7
✘ error: invalid pattern: “incomplete-match”
reason: pattern does not match entire message
--> {test_dir}/bad-config/formats/invalid-regex/format.json:20
| 1428634687123; foo
| ^ matched up to here
= note: incomplete-match = ^(?<timestamp>\d+);
= help: update the regular expression to fully capture the sample message
✘ error: invalid sample log message: "abc: foo"
reason: unrecognized timestamp -- abc
--> {test_dir}/bad-config/formats/invalid-sample/format.json:34
= note: the following custom formats were tried:
abc
^ “%i” matched up to here
= help: If the timestamp format is not supported by default, you can add a custom format with the “timestamp-format” property
✘ error: invalid sample log message: "1428634687123| debug hello"
reason: “debug” does not match the expected level of “info”
--> {test_dir}/bad-config/formats/invalid-sample/format.json:37
= note: matched regex = with-level
captured level = “debug”
level regular expression match results:
/bad_sample_log/level/debug = debug
debug
^---^
/bad_sample_log/level/info = info
no match
= help: Level regexes are not anchored to the start/end of the string. Prepend “^” to the expression to match from the start of the string and append “$” to match up to the end of the string.
✘ error: invalid pattern: “with-level”
reason: pattern does not match entire multiline sample message
--> {test_dir}/bad-config/formats/invalid-sample/format.json:41
= note: with-level = ^(?<timestamp>\d+)\| (?<level>\w+) (?<body>\w+)$
= help: use “.*” to match new-lines
✘ error: invalid sample log message: "1428634687123; foo bar"
reason: sample does not match any patterns
--> {test_dir}/bad-config/formats/invalid-sample/format.json:45
= note: the following shows how each pattern matched this sample:
1428634687123; foo bar
^ bad-time matched up to here
^ semi matched up to here
^ std matched up to here
^ with-level matched up to here
= note: bad-time = “^(?<timestamp>\w+): (?<body>\w+)$”
semi = “^(?<timestamp>\d+); (?<body>\w+)$”
std = “^(?<timestamp>\d+): (?<pid>\w+) (?<body>.*)$”
with-level = “^(?<timestamp>\d+)\| (?<level>\w+) (?<body>\w+)$”
⚠ warning: invalid pattern: “/bad_sample_log/regex/semi”
reason: pattern does not match any samples
--> {test_dir}/bad-config/formats/invalid-sample/format.json:10
= help: every pattern should have at least one sample that it matches
⚠ warning: invalid pattern: “/bad_sample_log/regex/std”
reason: pattern does not match any samples
--> {test_dir}/bad-config/formats/invalid-sample/format.json:7
= help: every pattern should have at least one sample that it matches
⚠ warning: invalid value “/invalid_props_log/value/non-existent”
reason: no patterns have a capture named “non-existent”
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
= note: the following captures are available:
body, pid, timestamp
= help: values are populated from captures in patterns, so at least one pattern must have a capture with this value name
✘ error: invalid tag definition “/invalid_props_log/tags/badtag”
reason: tag definitions must have a non-empty pattern
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: invalid tag definition “/invalid_props_log/tags/badtag2”
reason: tag definitions must have a non-empty pattern
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: invalid tag definition “/invalid_props_log/tags/badtag3”
reason: tag definitions must have a non-empty pattern
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: “invalid_props_log” is not a valid log format
reason: “subsecond-unit” must be set when “subsecond-field” is used
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: invalid value for property “/invalid_props_log/timestamp-field”
reason: “ts” was not found in the pattern at /invalid_props_log/regex/std
--> {test_dir}/bad-config/formats/invalid-properties/format.json:4
= note: the following captures are available:
body, pid, timestamp
✘ error: “not a color” is not a valid color value for property “/invalid_props_log/highlights/hl1/color”
reason: Unknown color: 'not a color'. See https://jonasjacek.github.io/colors/ for a list of supported color names
--> {test_dir}/bad-config/formats/invalid-properties/format.json:24
✘ error: “also not a color” is not a valid color value for property “/invalid_props_log/highlights/hl1/background-color”
reason: Unknown color: 'also not a color'. See https://jonasjacek.github.io/colors/ for a list of supported color names
--> {test_dir}/bad-config/formats/invalid-properties/format.json:25
✘ error: “no_regexes_log” is not a valid log format
reason: no regexes specified
--> {test_dir}/bad-config/formats/no-regexes/format.json:4
✘ error: “no_regexes_log” is not a valid log format
reason: log message samples must be included in a format definition
--> {test_dir}/bad-config/formats/no-regexes/format.json:4
✘ error: “no_sample_log” is not a valid log format
reason: log message samples must be included in a format definition
--> {test_dir}/bad-config/formats/no-samples/format.json:4
✘ error: failed to compile SQL statement
reason: near "TALE": syntax error
--> {test_dir}/bad-config/formats/invalid-sql/init.sql:4
| -- comment test
| CREATE TALE invalid (x y z);
| ^ near "TALE": syntax error
✘ error: failed to execute SQL statement
reason: ✘ error: “abc(” is not a valid regular expression
| reason: missing closing parenthesis
| --> arg
| | abc(
| | ^ missing closing parenthesis
--> {test_dir}/bad-config/formats/invalid-sql/init2.sql
| SELECT regexp_match('abc(', '123')
| FROM sqlite_master;