mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-21 14:44:00 +00:00
820889cf53
While at it, mention vmctl-like tool for migrating logs from other systems to VictoriaLogs at docs/VictoriaLogs/Roadmap.md Thanks to the question from Xavier Pestel at https://www.linkedin.com/feed/update/urn:li:activity:7212093021301927937?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7212093021301927937%2C7212171550651731969%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287212171550651731969%2Curn%3Ali%3Aactivity%3A7212093021301927937%29
1.9 KiB
1.9 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:
- OpenTelemetry for logs
- Fluentd
- Journald (systemd)
- Datadog protocol for logs
- Add missing functionality to LogsQL:
- Integration with Grafana (partially done).
- 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.
- Data migration tool from Grafana Loki to VictoriaLogs (similar to vmctl).