diff --git a/CHANGES.md b/CHANGES.md
index a4248dfc..9b6eef06 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -13,6 +13,11 @@ Release Notes.
 #### Plugins
 * Support [goframev2](https://github.com/gogf/gf) goframev2.
 
+#### Documentation
+* Add docs for `AddEvent` in `Tracing APIs`
+* Add `Logging APIs` document into Manual APIs.
+* Add `Metric APIs` document into Manual APIs.
+
 #### Bug Fixes
 * Fix wrong docker image name and `-version` command.
 * Fix redis plugin cannot work in cluster mode.
diff --git a/docs/en/advanced-features/manual-apis/toolkit-log.md b/docs/en/advanced-features/manual-apis/toolkit-log.md
new file mode 100644
index 00000000..35532456
--- /dev/null
+++ b/docs/en/advanced-features/manual-apis/toolkit-log.md
@@ -0,0 +1,51 @@
+# Logging APIs
+
+## Add Logging Toolkit
+
+toolkit/logging provides the APIs to attaching log information to the Span in the current context, such as debug, info, warn, error.
+Add the toolkit/logging dependency to your project.
+
+```go
+import "github.com/apache/skywalking-go/toolkit/logging"
+```
+
+## Use Native Logging
+
+toolkit/logging provides common log level APIs. We need to pass a required "Message" parameter and multiple optional string type key-value pairs.
+
+```go
+// Debug logs a message at DebugLevel
+func Debug(msg string, keyValues ...string) 
+
+// Info logs a message at InfoLevel
+func Info(msg string, keyValues ...string) 
+
+// Warn logs a message at DebugLevel
+func Warn(msg string, keyValues ...string) 
+
+// Error logs a message at ErrorLevel
+func Error(msg string, keyValues ...string)
+```
+
+### Associate Span
+
+When we call logging APIs to log, it will attach the log information to the active Span in the current Context. Even if we log across different Goroutines, it can correctly attach the log to span.
+
+### Example
+
+We create a LocalSpan in the `main` func, and we call `logging.debug` to record a log. The log will be attached to the Span of the current context.
+
+```go
+func main() {
+    span, err := trace.CreateLocalSpan("foo")
+    if err != nil {
+        log.Fatalln(err)
+    }
+	
+    logging.Debug("this is debug info", "foo", "bar")
+}
+```
+
+### More Information
+
+Log analyzer of OAP server supports native log data. OAP could use Log Analysis Language to structure log content through parsing, extracting and saving logs. The analyzer also uses Meter Analysis Language Engine for further metrics calculation. [see reference for details](https://skywalking.apache.org/docs/main/latest/en/setup/backend/log-analyzer/#log-analysis)
\ No newline at end of file
diff --git a/docs/en/advanced-features/manual-apis/toolkit-metric.md b/docs/en/advanced-features/manual-apis/toolkit-metric.md
new file mode 100644
index 00000000..300f3b37
--- /dev/null
+++ b/docs/en/advanced-features/manual-apis/toolkit-metric.md
@@ -0,0 +1,98 @@
+# Metric APIs
+
+## Add Metrics Toolkit
+
+toolkit/metic provides APIs to support manual reporting of metric data. Currently supports main metric types: `Counter`, `Gauge`, `Histogram`.
+Add the toolkit/metric dependency to your project.
+
+```go
+import "github.com/apache/skywalking-go/toolkit/metric"
+```
+
+## Use Native Metric
+
+### Counter
+
+Counter are particularly useful for monitoring the rate of events in your application.
+To manually build a Counter and get its value, you would typically follow these steps:
+
++ Create a Counter: You would create a Counter metric instance using the provided metric package functions `NewCounter(name string, opt ...MeterOpt)`. This Counter can then be used to increment its value as needed.
+
++ Register the Counter: After creating the Counter, it is automatically registered with the Metric Registry so that it can be tracked and exposed for monitoring purposes.
+
++ Increment the Counter: During the execution of your application, you would increment the Counter by `func (c *CounterRef) Inc(val float64)` method to reflect the occurrence of specific events.
+
++ Retrieve the Value: To get the current value of the Counter, you would access it through the `func (c *CounterRef) Get() float64`  methods.
+
+For example:
+
+```go
+func main() {
+    counter := metric.NewCounter("http_request_total")
+    counter.Inc(1)
+    val := counter.Get()
+}	
+```
+
+### Gauge
+
+Gauge metrics are used to represent a single numeric value that can increase or decrease, and are often used to represent metrics that can go up and down, such as memory usage, concurrency, temperature, etc.
+To manually build a Gauge metric and get its value, you can follow these steps:
+
++ Create a Gauge metric: Use the function `NewGauge(name string, getter func() float64, opts ...MeterOpt)` provided by the metric package to create a Gauge metric instance.
+
++ Register Gauge Metrics: After creating a Gauge, it is automatically registered in the Metric Registry so that it can be tracked and exposed for monitoring.
+
++ Set Gauge Values: When creating a Gauge, we dynamically set val through a `getter func() float64` callback function type
+
++ Get Gauge Values: Retrieve the current value from the Gauge metric through the `(g *GaugeRef) Get() float64` method
+
+For example:
+
+```go
+func main() {
+    getCPUUsage := func() float64 {
+        return 10.00
+    }
+
+    gauge := metric.NewGauge("cpu_usage_rate", getCPUUsage)
+    curVal := gauge.Get()
+}
+```
+
+### Histogram
+
+Histogram metric is used to count the distribution of events. It records the frequency distribution of event values and is usually used to calculate statistics such as averages, percentiles, etc. The Histogram metric is very suitable for measuring metrics that change over time, such as request latency and response time.
+To manually build a Histogram metric and get its value, you can follow these steps:
+
++ Create a Histogram metric: Use the `NewHistogram(name string, steps []float64, opts ...MeterOpt)` method to create a Histogram metric instance. Steps represents multiple steps in the Histogram (also called buckets in some components)
+
++ Register the Histogram metric: After creating the Histogram, it is automatically registered in the metric registry so that it can be tracked and exposed for monitoring.
+
++ Record event values to Histogram: Record event values by calling the `Observe(val float64)/ObserveWithCount(val float64, count int64)` method of the Histogram metric.
+
+For example:
+
+```go
+func main() {
+	steps := []float64{5, 10, 20, 50, 100}
+	histogram := metric.NewHistogram("request_duration", steps)
+
+	histogram.Observe(30)
+	// find the value associate bucket and add specific count.
+	histogram.ObserveWithCount(60, 50)
+}
+```
+
+### MeterOpt
+
+MeterOpt is a common Option for metric types. Currently, only `WithLabels` is supported to attach labels to the metric.
+
+```go
+// WithLabels Add labels for metric
+func WithLabels(key, val string) MeterOpt
+```
+
+### More Information
+
+Custom metrics may be collected by the Manual Meter API. Custom metrics collected cannot be used directly; they should be configured in the meter-analyzer-config configuration files. [see reference for details](https://skywalking.apache.org/docs/main/latest/en/setup/backend/backend-meter/#report-meter-telemetry-data)
\ No newline at end of file
diff --git a/docs/en/advanced-features/manual-apis/toolkit-trace.md b/docs/en/advanced-features/manual-apis/toolkit-trace.md
index 4febd8bf..0b3da0c0 100644
--- a/docs/en/advanced-features/manual-apis/toolkit-trace.md
+++ b/docs/en/advanced-features/manual-apis/toolkit-trace.md
@@ -3,7 +3,7 @@
 ## Add trace Toolkit
 
 toolkit/trace provides the APIs to enhance the trace context, such as createLocalSpan, createExitSpan, createEntrySpan, log, tag, prepareForAsync and asyncFinish. 
-Add the toolkit dependency to your project.
+Add the toolkit/trace dependency to your project.
 
 ```go
 import "github.com/apache/skywalking-go/toolkit/trace"
@@ -97,6 +97,32 @@ trace.SetComponent(ComponentID)
 
 The Component ID in Span is used to identify the current component, which is declared in the [component libraries YAML](https://github.com/apache/skywalking/blob/master/oap-server/server-starter/src/main/resources/component-libraries.yml) from the OAP server side.
 
+### Attach an event to a span
+
+Use the `trace.AddEvent(et EventType, event string)` API to attach an event to the Span
+
+Currently, we support the following four types of events:
+
+```go
+// DebugEventType Indicates the event type is "debug"
+DebugEventType EventType = "debug"
+
+// InfoEventType Indicates the event type is "info"
+InfoEventType EventType = "info"
+
+// WarnEventType Indicates the event type is "warn"
+WarnEventType EventType = "warn"
+
+// ErrorEventType Indicates the event type is "error"
+ErrorEventType EventType = "error"
+```
+
+For example, we can add a "request timeout" event:
+
+```go
+trace.AddEvent(WarnEventType, "current request has timed out!")
+```
+
 ### Async Prepare/Finish
 
 `SpanRef` is the return value of `CreateSpan`.Use `SpanRef.PrepareAsync()` to make current span still alive until `SpanRef.AsyncFinish()` called.
diff --git a/docs/menu.yml b/docs/menu.yml
index 53f41755..86c1f510 100644
--- a/docs/menu.yml
+++ b/docs/menu.yml
@@ -46,6 +46,10 @@ catalog:
           catalog:
             - name: Tracing APIs
               path: /en/advanced-features/manual-apis/toolkit-trace
+            - name: Logging APIs
+              path: /en/advanced-features/manual-apis/toolkit-log
+            - name: Metric APIs
+              path: /en/advanced-features/manual-apis/toolkit-metric
     - name: Plugins
       catalog:
         - name: Supported Libraries