docs/VictoriaLogs: small clarifications

This commit is contained in:
Aliaksandr Valialkin 2023-07-09 11:00:35 -07:00
parent 51a9cc9783
commit fe57e99a5b
No known key found for this signature in database
GPG key ID: A72BEC6CD3D0DED1
2 changed files with 5 additions and 5 deletions

View file

@ -25,9 +25,6 @@ For example, the following query finds all the logs with `error` word:
error error
``` ```
This query matches logs with any [timestamp](https://docs.victoriametrics.com/VictoriaLogs/keyConcepts.html#time-field),
e.g. it may return logs from the previous year alongside recently ingested logs.
If the queried [word](#word) clashes with LogsQL keywords, then just wrap it into quotes. If the queried [word](#word) clashes with LogsQL keywords, then just wrap it into quotes.
For example, the following query finds all the log messages with `and` [word](#word): For example, the following query finds all the log messages with `and` [word](#word):
@ -48,6 +45,9 @@ finds log messages with the `error: cannot find file` phrase:
"error: cannot find file" "error: cannot find file"
``` ```
Queries above match logs with any [timestamp](https://docs.victoriametrics.com/VictoriaLogs/keyConcepts.html#time-field),
e.g. they may return logs from the previous year alongside recently ingested logs.
Usually logs from the previous year aren't so interesting comparing to the recently ingested logs. Usually logs from the previous year aren't so interesting comparing to the recently ingested logs.
So it is recommended adding [time filter](#time-filter) to the query. So it is recommended adding [time filter](#time-filter) to the query.
For example, the following query returns logs with the `error` [word](#word), For example, the following query returns logs with the `error` [word](#word),

View file

@ -2,8 +2,8 @@
## Data model ## Data model
[VictoriaLogs](https://docs.victoriametrics.com/VictoriaLogs/) works with structured logs. [VictoriaLogs](https://docs.victoriametrics.com/VictoriaLogs/) works with both structured and unstructured logs.
Every log entry may contain arbitrary number of `key=value` pairs (aka fields). Every log entry must contain at least [log message field](#message-field) plus arbitrary number of additional `key=value` fields.
A single log entry can be expressed as a single-level [JSON](https://www.json.org/json-en.html) object with string keys and values. A single log entry can be expressed as a single-level [JSON](https://www.json.org/json-en.html) object with string keys and values.
For example: For example: