Add heartbeat API.

ossrs · Apr 12, 2024 · cf1f78e · cf1f78e
1 parent 9fc0241
commit cf1f78e
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 0 deletions.
diff --git a/i18n/en-us/docusaurus-plugin-content-docs/current/doc/http-callback.md b/i18n/en-us/docusaurus-plugin-content-docs/current/doc/http-callback.md
@@ -267,6 +267,8 @@ heartbeat {
 By enable the `summaries`, you can get the SRS server states, such as `self.pid` and `self.srs_uptime`, so you
 can use this to determine whether SRS restarted.
 
+> Note: About fileds of `summaries`, see [HTTP API: summaries](./http-api.md#summaries) for details.
+
 ## Go Example
 
 Write Go code to handle SRS callback, for example, handling `on_publish`:

diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/doc/http-callback.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/doc/http-callback.md
@@ -264,6 +264,8 @@ heartbeat {
 
 通过启用`summaries`，您可以获取SRS服务器状态，例如`self.pid`和`self.srs_uptime`，因此您可以使用它来判断SRS是否重新启动。
 
+> Note: 关于`summaries`的字段，请参阅 [HTTP API: summaries](./http-api.md#summaries) 了解详细信息。
+
 ## Go Example
 
 使用Go处理SRS的回调，以`on_publish`为例：

diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-5.0/doc/http-callback.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-5.0/doc/http-callback.md
@@ -264,6 +264,8 @@ heartbeat {
 
 通过启用`summaries`，您可以获取SRS服务器状态，例如`self.pid`和`self.srs_uptime`，因此您可以使用它来判断SRS是否重新启动。
 
+> Note: 关于`summaries`的字段，请参阅 [HTTP API: summaries](./http-api.md#summaries) 了解详细信息。
+
 ## Go Example
 
 使用Go处理SRS的回调，以`on_publish`为例：

diff --git a/versioned_docs/version-5.0/doc/http-callback.md b/versioned_docs/version-5.0/doc/http-callback.md
@@ -267,6 +267,8 @@ heartbeat {
 By enable the `summaries`, you can get the SRS server states, such as `self.pid` and `self.srs_uptime`, so you 
 can use this to determine whether SRS restarted.
 
+> Note: About fileds of `summaries`, see [HTTP API: summaries](./http-api.md#summaries) for details.
+
 ## Go Example
 
 Write Go code to handle SRS callback, for example, handling `on_publish`: