Skip to content

Commit 36c3cc2

Browse files
authored
refactor: GreptimeDB enterprise (#1942)
1 parent a344a28 commit 36c3cc2

File tree

48 files changed

+283
-330
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

48 files changed

+283
-330
lines changed

docs/enterprise/administration/overview.md

Lines changed: 0 additions & 8 deletions
This file was deleted.
File renamed without changes.
File renamed without changes.
File renamed without changes.
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
keywords: [Kubernetes deployment, Operator pattern, automated management, cluster deployment, standalone instance, private cloud, public cloud]
3+
description: Overview of deploying GreptimeDB on Kubernetes, including cluster installation, upgrades, and monitoring.
4+
---
5+
6+
# Deploy GreptimeDB on Kubernetes
7+
8+
The deployment process for GreptimeDB Enterprise on Kubernetes is almost the same as the open-source version.
9+
This chapter focuses on the specific deployment configurations and features of the enterprise version.
10+
11+
## Installation
12+
13+
To learn how to start GreptimeDB through Helm Chart, please see the [Install GreptimeDB](./installation.md) page.
14+
15+
## Upgrade
16+
17+
Please visit the [Upgrade GreptimeDB](./upgrade.md) page to learn how to upgrade GreptimeDB enterprise.
18+
File renamed without changes.
File renamed without changes.
File renamed without changes.
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
keywords: [GreptimeDB health check, GreptimeDB status, GreptimeDB deployment status, GreptimeDB metrics]
3+
description: Check GreptimeDB health status, deployment status, and runtime metrics through HTTP endpoints.
4+
---
5+
6+
# Check GreptimeDB Status
7+
8+
GreptimeDB provides a series of HTTP endpoints to query the operational status of GreptimeDB.
9+
The following HTTP requests assume that GreptimeDB is running on node `127.0.0.1` with the HTTP service listening on the default port `4000`.
10+
11+
## Check if GreptimeDB is running normally
12+
13+
You can use the `/health` endpoint to check if GreptimeDB is running normally.
14+
An HTTP status code `200 OK` indicates that GreptimeDB is running normally.
15+
16+
Example:
17+
18+
```bash
19+
curl -i -X GET http://127.0.0.1:4000/health
20+
HTTP/1.1 200 OK
21+
content-type: application/json
22+
content-length: 2
23+
date: Tue, 31 Dec 2024 02:15:22 GMT
24+
25+
{}
26+
```
27+
28+
For more information about the health check endpoint, please refer to [the Health endpoint](/reference/http-endpoints.md#health-check).
29+
30+
## Check GreptimeDB status
31+
32+
You can use the `/status` endpoint to check the deployment status of GreptimeDB.
33+
34+
```bash
35+
curl -X GET http://127.0.0.1:4000/status | jq
36+
37+
{
38+
"source_time": "2024-12-27T07:57:47Z",
39+
"commit": "b4bd34c530d62b95346a26a9470c03b9f6fb15c8",
40+
"branch": "main",
41+
"rustc_version": "rustc 1.84.0-nightly (e92993dbb 2024-10-18)",
42+
"hostname": "127.0.0.1",
43+
"version": "0.12.0"
44+
}
45+
```
46+
47+
Please refer to [the Status endpoint](/reference/http-endpoints.md#status) for more details.
48+

0 commit comments

Comments
 (0)