mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-29 23:30:04 +01:00
6f98b9c221
This reverts commit 3d7a77bf82.
Reason for revert: relative links do not work properly at GitHub code
and at GitHub wiki. For example, the following page contains broken links
before reverting this commit:
https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/docs/VictoriaLogs/CHANGELOG.md
It is always better to use absolute links thank relative links, since the page contents
can be copy-n-pasted to other pages, which are located in vastly different directories,
and all the links will remain working.
2.6 KiB
2.6 KiB
| sort | weight | title | disableToc | menu | aliases | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8 | 8 | VictoriaLogs roadmap | true |
|
|
VictoriaLogs roadmap
The VictoriaLogs Preview is ready for evaluation in production. It is recommended running it alongside the existing solutions such as Elasticsearch and Grafana Loki and comparing their resource usage and usability. It isn't recommended migrating from existing solutions to VictoriaLogs Preview yet.
The following functionality is available in VictoriaLogs Preview:
See these docs for details.
The following functionality is planned in the future versions of VictoriaLogs:
- Support for data ingestion from popular log collectors and formats:
- Fluentd
- Syslog
- Journald (systemd)
- Add missing functionality to LogsQL:
- Stream context.
- Transformation functions.
- Post-filtering.
- Stats calculations.
- Sorting.
- Limiters.
- The ability to use subqueries inside in() function.
- Live tailing for LogsQL filters aka
tail -f. - Web UI with the following abilities:
- Explore the ingested logs (partially done).
- Build graphs over time for the ingested logs.
- Integration with Grafana.
- Ability to make instant snapshots and backups in the way similar to VictoriaMetrics.
- Cluster version of VictoriaLogs.
- Ability to store data to object storage (such as S3, GCS, Minio).
- Alerting on LogsQL queries.