What's the plan/roadmap of the 1st GA version ?

[chenlujjj]

Is your question related to a specific component?

N/A

Describe the question in detail

We're evaluating VictoriaTrace as our primary trace storage solution, so we want to know the estimated timeline of the 1st GA (production-ready) version

Key concepts docs

• VictoriaTraces key concepts - https://docs.victoriametrics.com/victoriatraces/keyconcepts/
• LogsQL - https://docs.victoriametrics.com/victorialogs/logsql/

[jiekun]

Hi! We have some users running it in production environments already, Haven't announced GA mainly because we want to allocate more engineers in the coming months to jointly review and audit the current design to make it more robust. Currently, we expect experienced engineers to start working on this review in the second half of the year, and we hope to announce GA within this year.

How long do you store Traces data normally? Our main concern for GA is the underlying data structure, not feature backlogs. After GA releases, data structures will be hard to change due to backward compatibility. If you don’t need half-year or one-year trace storage, you can easily take advantage of the current version and save cost comparing to other traces backends. If we ever change the base data structure (it may not happen), you can just wait briefly for old data to expire, then fully move to the new structure.

[chenlujjj]

Hi @jiekun , we store traces for around one week now.

save cost comparing to other traces backends.

Do you have any public report about the cost comparison ?

[chenlujjj]

btw, will VictoriaTraces support full compatibility with Tempo API and its TraceQL as well?

[jiekun]

Do you have any public report about the cost comparison?

We may consider redo the benchmark again after the vtagent release, and compare it with the Jaeger v2 (native support with ClickHouse) and maybe other backends.

will VictoriaTraces support full compatibility with Tempo API and its TraceQL as well?

The TraceQL support has some limitation, structural operators (>>, !<, ...) are not supported and we don't have plan to extend the support for now.

[gravese]

@jiekun Hi, is there any progress on this plan? When is it expected to be released?

[jiekun]

@gravese Hello. In Q3 we're working on vtagent now. And for the GA, the current pending issue is the helper index which we want to remove. So there's plan to test VictoriaTraces without such index (or build an internal indexDB which is not visible to the users), and then we can announce the GA.