Kiu/VictoriaMetrics
Kiu/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-12-15 00:13:30 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

docs/VictoriaLogs: small clarifications

Browse Source
This commit is contained in:
Aliaksandr Valialkin 2023-07-09 11:00:35 -07:00
parent ddd918b93c
commit 371036eb35
No known key found for this signature in database
GPG Key ID: A72BEC6CD3D0DED1
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/VictoriaLogs/LogsQL.md
View File

@ -25,9 +25,6 @@ For example, the following query finds all the logs with `error` word:
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.
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"
```
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.
So it is recommended adding [time filter](#time-filter) to the query.
For example, the following query returns logs with the `error` [word](#word),

4
docs/VictoriaLogs/keyConcepts.md
View File

@ -2,8 +2,8 @@
## Data model
[VictoriaLogs](https://docs.victoriametrics.com/VictoriaLogs/) works with structured logs.
Every log entry may contain arbitrary number of `key=value` pairs (aka fields).
[VictoriaLogs](https://docs.victoriametrics.com/VictoriaLogs/) works with both structured and unstructured logs.
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.
For example: