From e781f31466d29213f6af044661e6f3ca49b32814 Mon Sep 17 00:00:00 2001
From: Meng Zhang <meng@tabbyml.com>
Date: Mon, 5 Jun 2023 17:47:35 -0700
Subject: [PATCH] Delete Events.md

---
 docs/internal/Events.md | 33 ---------------------------------
 1 file changed, 33 deletions(-)
 delete mode 100644 docs/internal/Events.md

diff --git a/docs/internal/Events.md b/docs/internal/Events.md
deleted file mode 100644
index 3a16273..0000000
--- a/docs/internal/Events.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# Events System
-
-*Experimental*
-
-In Tabby, we use the [`vector`](../../deployment/config/vector.toml) to collect logs from various sources, transform them into a standard `Event`, and persist them in `/data/logs/events`.
-
-## Schema
-
-### Event
-
-```jsx
-{
-  "id": EventId,
-  "data": Any
-}
-```
-
-The `id` field can be used to uniquely identify an event.
-
-The `data`  field is a standard JSON object, and its definition is left to downstream tasks.
-
-### EventId
-
-```JSX
-{
-  "process_id": Number,
-  "thread_id": Number,
-  // Unix timestamp
-  "timestamp": Number,
-}
-```
-
-In the future, we might add `server_id` when Tabby evolves into a distributed environment.