Open Issues Need Help
View All on GitHubFast and easy to use database for traces, which can efficiently handle terabytes of trace spans.
Fast and easy to use database for traces, which can efficiently handle terabytes of trace spans.
Fast and easy to use database for traces, which can efficiently handle terabytes of trace spans.
Fast and easy to use database for traces, which can efficiently handle terabytes of trace spans.
Fast and easy to use database for traces, which can efficiently handle terabytes of trace spans.
AI Summary: Enhance VictoriaLogs to export metrics including tenant ID information. This requires modifying the existing metrics exporter to incorporate tenant ID data into the exported metrics, allowing for per-tenant monitoring of event and storage usage.
Fast and easy to use database for traces, which can efficiently handle terabytes of trace spans.
AI Summary: Improve the performance of VictoriaTraces when querying by `trace_id` only by creating a helper stream (`trace_id_idx`) containing `trace_id` and timestamp information. This stream will be queried first to identify the relevant time range before querying the main data streams, thus avoiding full scans for old trace IDs.
Fast and easy to use database for traces, which can efficiently handle terabytes of trace spans.
AI Summary: Create a Grafana dashboard for monitoring VictoriaTraces, similar in style and functionality to the existing VictoriaLogs dashboard. This involves leveraging existing Grafana dashboards and adapting them to the specifics of VictoriaTraces.
Fast and easy to use database for traces, which can efficiently handle terabytes of trace spans.