You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All type of events should be stored in Clickhouse via backend -> vector -> Clickhouse.
Possible Solution
No response
Context
When I turn on analytics, just few type of events are saving in Clickhouse (like create:job, update:task from server source), nothing more. Users activity, working time, create/delete project, delete task/job are not exist in Clickhouse.
By the way, looks like the server POST events:
The configuration looks mostly correct for enabling analytics, but the issue might lie in:
The Vector configuration, which might not be set up to capture all types of events.
The Clickhouse schema, which might need adjustments to store additional event types.
Connectivity or processing issues between Vector and Clickhouse.
You may need to check the Vector configuration for any missing event types and ensure Clickhouse is set up to store all event data. Additionally, reviewing the logs from both services (Vector and Clickhouse) can provide more insight into why some events are not being stored.
Actions before raising this issue
Steps to Reproduce
helm
ink8s
analytics.enabled=true
Expected Behavior
All type of events should be stored in Clickhouse via backend -> vector -> Clickhouse.
Possible Solution
No response
Context
When I turn on analytics, just few type of events are saving in Clickhouse (like
create:job
,update:task
fromserver
source), nothing more. Users activity, working time, create/delete project, delete task/job are not exist in Clickhouse.By the way, looks like the server POST events:
But nothing in
Vector
logs andClickhouse
DB.When I create a new task I see the logs in
Vector
and new row in DB, but just for this case.I found one same issue: Am I the only one whose client events are not being saved in k8s? · Issue #8205 · cvat-ai/cvat
Any good idea?
Environment
Used default
values.yaml
:The text was updated successfully, but these errors were encountered: