docs/VictoriaLogs: cut v1.0.0-victorialogs

This commit is contained in:
Aliaksandr Valialkin 2024-11-12 18:31:59 +01:00 committed by f41gh7
parent 674be3c387
commit e012a996aa
No known key found for this signature in database
GPG key ID: 4558311CF775EC72
2 changed files with 14 additions and 1 deletions

View file

@ -15,6 +15,14 @@ according to [these docs](https://docs.victoriametrics.com/victorialogs/quicksta
## tip
## [v1.0.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.0.0-victorialogs)
Released at 2024-11-12
This release is identical to [v0.42.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v0.42.0-victorialogs).
VictoriaLogs reached production quality since the [initial v0.1.0 release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v0.1.0-victorialogs) 1.5 years ago,
so it can be safely used in production.
## [v0.42.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v0.42.0-victorialogs)
Released at 2024-11-08

View file

@ -11,6 +11,11 @@ aliases:
- /VictoriaLogs/FAQ.html
- /VictoriaLogs/faq.html
---
## Is VictoriaLogs ready for production use?
Yes. VictoriaLogs is ready for production use starting from [v1.0.0](https://docs.victoriametrics.com/victorialogs/changelog/).
## What is the difference between VictoriaLogs and Elasticsearch (OpenSearch)?
Both Elasticsearch and VictoriaLogs allow ingesting structured and unstructured logs
@ -169,4 +174,4 @@ And for the following log, its `_msg` will be `foo bar in body`:
"message": "",
"body": "foo bar in body"
}
```
```