### Clone and Run GreptimeDB

Source: https://docs.greptime.com/0.12/contributor-guide/getting-started

This snippet demonstrates how to clone the GreptimeDB repository, navigate into the directory, and start a standalone instance using Cargo.

```Shell
git clone https://github.com/GreptimeTeam/greptimedb.git
cd greptimedb
cargo run -- standalone start
```

--------------------------------

### Install and Run GreptimeDB Unit Tests

Source: https://docs.greptime.com/0.15/contributor-guide/getting-started

This section details how to install the `cargo-nextest` tool to run GreptimeDB's unit tests. After installation, the tests can be executed using the provided command.

```Shell
cargo install cargo-nextest --locked
cargo nextest run
```

--------------------------------

### Install Nextest

Source: https://docs.greptime.com/0.12/contributor-guide/getting-started

This snippet explains how to install the 'nextest' tool, which is used for running GreptimeDB's unit test suite, using Cargo.

```Rust
cargo install cargo-nextest --locked
```

--------------------------------

### Install Nextest for Unit Testing

Source: https://docs.greptime.com/0.14/contributor-guide/getting-started

This command installs the `nextest` tool using Cargo, which is recommended for running GreptimeDB's unit test suite. Ensure you have Rust and Cargo installed.

```Shell
cargo install cargo-nextest --locked
```

--------------------------------

### Install and Run GreptimeDB Unit Tests

Source: https://docs.greptime.com/0.16/contributor-guide/getting-started

This section details how to install the 'nextest' tool using Cargo and then execute the entire unit test suite for GreptimeDB. This is crucial for verifying the integrity of the codebase.

```Rust
cargo install cargo-nextest --locked
```

```Rust
cargo nextest run
```

--------------------------------

### Install and Run Greptime Cloud Quick Start

Source: https://docs.greptime.com/nightly/greptimecloud/getting-started/python

Installs and runs the Greptime Cloud quick start application using pipx. This command collects system metric data and sends it to GreptimeDB via HTTP OTLP.

```bash
pipx run --no-cache greptime-cloud-quick-start -e https://<host>/v1/otlp/v1/metrics -db <dbname> -u <username> -p <password>
```

--------------------------------

### Clone and Run GreptimeDB

Source: https://docs.greptime.com/0.13/contributor-guide/getting-started

This snippet shows the basic commands to clone the GreptimeDB repository from GitHub, navigate into the directory, and start a standalone instance using Cargo.

```Shell
git clone https://github.com/GreptimeTeam/greptimedb.git
cd greptimedb
cargo run -- standalone start
```

--------------------------------

### Install Nextest

Source: https://docs.greptime.com/0.13/contributor-guide/getting-started

This command installs the `nextest` tool, which is used for running GreptimeDB's unit test suite. It requires Cargo, the Rust package manager.

```Rust
cargo install cargo-nextest --locked
```

--------------------------------

### Run GreptimeDB Standalone Instance

Source: https://docs.greptime.com/0.14/contributor-guide/getting-started

This snippet shows the commands to clone the GreptimeDB repository, navigate into the directory, and start a standalone instance of the database using Cargo.

```Shell
git clone https://github.com/GreptimeTeam/greptimedb.git
cd greptimedb
cargo run -- standalone start
```

--------------------------------

### Install and Run GreptimeDB Unit Tests

Source: https://docs.greptime.com/nightly/contributor-guide/getting-started

This section details how to install the 'nextest' tool using Cargo and subsequently run the entire unit test suite for GreptimeDB. This ensures the database functions correctly according to its test cases.

```bash
cargo install cargo-nextest --locked
cargo nextest run
```

--------------------------------

### Clone and Run GreptimeDB Standalone

Source: https://docs.greptime.com/0.15/contributor-guide/getting-started

This snippet shows how to clone the GreptimeDB repository, navigate into the directory, and start a standalone instance using Cargo. It's a quick way to get a GreptimeDB server running locally.

```Shell
git clone https://github.com/GreptimeTeam/greptimedb.git
cd greptimedb
cargo run -- standalone start
```

--------------------------------

### Install Nextest for Unit Testing

Source: https://docs.greptime.com/contributor-guide/getting-started

This command installs the 'nextest' tool using Cargo, which is recommended for running GreptimeDB's unit test suite. Ensure you have Rust and Cargo installed.

```rust
cargo install cargo-nextest --locked
```

--------------------------------

### Add Example Configs for pg_kvbackend

Source: https://docs.greptime.com/release-notes/release-0-9-3

Includes example configurations for the `pg_kvbackend`, demonstrating its usage and setup.

```Markdown
docs: add example configs introduced by pg_kvbackend by @lyang24 in #4573
```

--------------------------------

### Run GreptimeDB Unit Tests

Source: https://docs.greptime.com/0.12/contributor-guide/getting-started

This snippet demonstrates how to execute the entire unit test suite for GreptimeDB using the 'nextest run' command.

```Rust
cargo nextest run
```

--------------------------------

### Run GreptimeDB Unit Tests

Source: https://docs.greptime.com/0.13/contributor-guide/getting-started

After installing `nextest`, this command executes the entire unit test suite for GreptimeDB.

```Rust
cargo nextest run
```

--------------------------------

### Compile and Run GreptimeDB

Source: https://docs.greptime.com/nightly/contributor-guide/getting-started

This snippet shows the basic commands to clone the GreptimeDB repository, navigate into the directory, and start a standalone instance using Cargo. It's the primary method for running the database locally from source.

```bash
git clone https://github.com/GreptimeTeam/greptimedb.git
cd greptimedb
cargo run -- standalone start
```

--------------------------------

### Install GreptimeDB Cluster with Monitoring and Grafana

Source: https://docs.greptime.com/0.12/user-guide/deployments/deploy-on-kubernetes/getting-started

This command installs the GreptimeDB cluster using Helm, enabling monitoring and Grafana features. It specifies the cluster name, enables monitoring and Grafana, and sets the namespace.

```bash
helm install mycluster \
  --set monitoring.enabled=true \
  --set grafana.enabled=true \
  --set flownode.enabled=true \
  greptime/greptimedb-cluster \
  -n default
```

--------------------------------

### Run GreptimeDB Unit Tests

Source: https://docs.greptime.com/0.14/contributor-guide/getting-started

After installing `nextest`, this command executes the entire unit test suite for GreptimeDB. This helps ensure the code's integrity and functionality.

```Shell
cargo nextest run
```

--------------------------------

### Install GreptimeDB Operator with kubectl and bundle.yaml

Source: https://docs.greptime.com/0.12/user-guide/deployments/deploy-on-kubernetes/getting-started

This command applies a 'bundle.yaml' file from the latest release to install the GreptimeDB Operator. This method is suitable for quick testing but not recommended for production.

```bash
kubectl apply -f \  
  https://github.com/GreptimeTeam/greptimedb-operator/releases/latest/download/bundle.yaml \  
  --server-side  
```

--------------------------------

### Start GreptimeDB Standalone (Binary)

Source: https://docs.greptime.com/getting-started/installation/greptimedb-standalone

Starts the GreptimeDB server in standalone mode after the binary has been downloaded and is available in the current directory.

```bash
./greptime standalone start
```

--------------------------------

### Install GreptimeDB Go Client

Source: https://docs.greptime.com/nightly/user-guide/ingest-data/for-iot/grpc-sdks/go

Installs the GreptimeDB client library for Go using the go get command. This is the first step to using the Go ingester SDK.

```bash
go get -u github.com/GreptimeTeam/greptimedb-ingester-go@v0.6.2
```

--------------------------------

### Start GreptimeDB Standalone (Binary)

Source: https://docs.greptime.com/0.12/getting-started/installation/greptimedb-standalone

Starts the GreptimeDB server in standalone mode after the binary has been downloaded and placed in the current directory. This command initiates the database process.

```bash
./greptime standalone start
```

--------------------------------

### Build GreptimeDB

Source: https://docs.greptime.com/0.12/contributor-guide/getting-started

This snippet shows how to build the GreptimeDB server without running it, using Cargo. The resulting artifacts are located in the target directory.

```Rust
cargo build
```

--------------------------------

### Install GreptimeDB Go Client

Source: https://docs.greptime.com/0.16/user-guide/ingest-data/for-iot/grpc-sdks/go

Installs the GreptimeDB client library for Go using the go get command. This is the first step to using the Go ingester SDK.

```bash
go get -u github.com/GreptimeTeam/greptimedb-ingester-go@v0.6.2
```

--------------------------------

### Install GreptimeDB Go Client

Source: https://docs.greptime.com/0.15/user-guide/ingest-data/for-iot/grpc-sdks/go

Installs the GreptimeDB client library for Go using the go get command. This is the first step to using the Go ingester SDK.

```bash
go get -u github.com/GreptimeTeam/greptimedb-ingester-go@v0.6.2
```

--------------------------------

### Start GreptimeDB Standalone (Binary)

Source: https://docs.greptime.com/0.13/getting-started/installation/greptimedb-standalone

Starts the GreptimeDB service in standalone mode after the binary has been downloaded and placed in the current directory.

```Shell
./greptime standalone start
```

--------------------------------

### Start GreptimeDB Standalone (Binary)

Source: https://docs.greptime.com/nightly/getting-started/installation/greptimedb-standalone

This command starts the GreptimeDB server in standalone mode after the binary has been downloaded and placed in the current directory.

```Bash
./greptime standalone start
```

--------------------------------

### Start GreptimeDB Component with Configuration File

Source: https://docs.greptime.com/user-guide/deployments-administration/configuration

This command demonstrates how to start a GreptimeDB component (e.g., standalone, frontend, datanode, metasrv) using a specified TOML configuration file.

```bash
greptime [standalone | frontend | datanode | metasrv]  start -c config/standalone.example.toml
```

```bash
greptime standalone start -c standalone.example.toml
```

--------------------------------

### Install etcd Cluster using Helm

Source: https://docs.greptime.com/0.12/user-guide/deployments/deploy-on-kubernetes/getting-started

Installs a 3-replica etcd cluster using Bitnami's Helm chart in a dedicated namespace. It configures etcd to not use RBAC for simplicity in this example.

```bash
helm install etcd \
  oci://registry-1.docker.io/bitnamicharts/etcd \
  --version 10.2.12 \
  --set replicaCount=3 \
  --set auth.rbac.create=false \
  --set auth.rbac.token.enabled=false \
  --create-namespace \
  -n etcd-cluster
```

--------------------------------

### Compile and Run GreptimeDB Standalone

Source: https://docs.greptime.com/contributor-guide/getting-started

This snippet shows how to clone the GreptimeDB repository, navigate into the directory, and start a standalone instance using Cargo. It's the primary method for running GreptimeDB locally from source.

```bash
git clone https://github.com/GreptimeTeam/greptimedb.git
cd greptimedb
cargo run -- standalone start
```

--------------------------------

### Install GreptimeDB Binary (Linux/macOS)

Source: https://docs.greptime.com/0.12/getting-started/installation/greptimedb-standalone

Downloads and installs the GreptimeDB binary for Linux and macOS using a curl script. This is the simplest way to get started with GreptimeDB on these operating systems.

```bash
curl -fsSL \
  https://raw.githubusercontent.com/greptimeteam/greptimedb/main/scripts/install.sh | sh -s v0.12.2
```

--------------------------------

### Show GreptimeDB Frontend Start Help

Source: https://docs.greptime.com/0.15/reference/command-lines/frontend

Displays all available options for the `greptime frontend start` command, allowing users to understand and configure the frontend service.

```bash
greptime frontend start --help
```

--------------------------------

### Install GreptimeDB Go Client

Source: https://docs.greptime.com/0.12/user-guide/ingest-data/for-iot/grpc-sdks/go

Installs the GreptimeDB client library for Go using the go get command. This is the first step to using the SDK in your Go projects.

```bash
go get -u github.com/GreptimeTeam/greptimedb-ingester-go@v0.6.0
```

--------------------------------

### Show GreptimeDB Frontend Help

Source: https://docs.greptime.com/0.16/reference/command-lines/frontend

Displays all available options for the `greptime frontend start` command, allowing users to understand and configure the frontend service.

```bash
greptime frontend start --help
```

--------------------------------

### Compile and Run GreptimeDB

Source: https://docs.greptime.com/0.16/contributor-guide/getting-started

This snippet shows the basic commands to clone the GreptimeDB repository, navigate into the directory, and start a standalone instance using Cargo. It's the primary method for running GreptimeDB from source.

```Shell
git clone https://github.com/GreptimeTeam/greptimedb.git
cd greptimedb
cargo run -- standalone start
```

--------------------------------

### Show GreptimeDB Datanode Help

Source: https://docs.greptime.com/0.16/reference/command-lines/datanode

Lists all available options for the `greptime datanode start` command, allowing users to understand and configure the datanode service.

```bash
greptime datanode start --help
```

--------------------------------

### Start GreptimeDB Standalone with HTTP Address

Source: https://docs.greptime.com/user-guide/deployments-administration/configuration

This command starts GreptimeDB in standalone mode and configures the HTTP address. It's a basic example of using command-line arguments for GreptimeDB.

```bash
greptime standalone start --http-addr 127.0.0.1:4000
```

--------------------------------

### Install and Run Greptime Cloud Quick Start

Source: https://docs.greptime.com/greptimecloud/getting-started/python

This command uses `pipx` to run the `greptime-cloud-quick-start` Python application. It's designed to collect system metrics (CPU, memory) and send them to GreptimeDB using OpenTelemetry over HTTP. You need to provide your Greptime Cloud host, database name, username, and password.

```bash
pipx run --no-cache greptime-cloud-quick-start -e https://<host>/v1/otlp/v1/metrics -db <dbname> -u <username> -p <password>
```

--------------------------------

### Start GreptimeDB Standalone with HTTP Address

Source: https://docs.greptime.com/0.16/user-guide/deployments-administration/configuration

This command starts GreptimeDB in standalone mode and configures the HTTP address. It's a basic example of using command-line arguments for GreptimeDB configuration.

```bash
greptime standalone start --http-addr 127.0.0.1:4000
```

--------------------------------

### Start GreptimeDB in Standalone Mode with HTTP Address

Source: https://docs.greptime.com/0.13/user-guide/deployments/configuration

This command starts GreptimeDB in standalone mode and configures the HTTP address. It's a basic example of using command-line arguments for configuration.

```Shell
greptime standalone start --http-addr 127.0.0.1:4000
```

--------------------------------

### Show Greptime Flownode Start Help

Source: https://docs.greptime.com/reference/command-lines/flownode

Displays the help information for the 'greptime flownode start' command, listing all available options and their descriptions.

```bash
greptime flownode start --help
```

--------------------------------

### Run GreptimeDB Grafana Docker Image

Source: https://docs.greptime.com/nightly/user-guide/integrations/grafana

Starts a Docker container with Grafana pre-configured with the GreptimeDB data source plugin. This is a convenient way to get started without manual installation.

```bash
docker run -p 3000:3000 greptime/grafana-greptimedb:latest
```

--------------------------------

### Start GreptimeDB in Standalone Mode with HTTP Address

Source: https://docs.greptime.com/nightly/user-guide/deployments-administration/configuration

This command starts GreptimeDB in standalone mode and configures the HTTP address for communication. It's a basic example of using command-line arguments for configuration.

```bash
greptime standalone start --http-addr 127.0.0.1:4000
```

--------------------------------

### GreptimeDB Frontend Start Help

Source: https://docs.greptime.com/0.12/reference/command-lines

Displays the help information for the 'greptime frontend start' command, listing all available configuration options for the frontend service.

```bash
greptime frontend start --help
```

--------------------------------

### Install etcd Cluster with Helm

Source: https://docs.greptime.com/0.13/user-guide/deployments/deploy-on-kubernetes/getting-started

Installs a 3-replica etcd cluster using the Bitnami etcd Helm chart in a dedicated namespace. It configures etcd to disable RBAC for simplicity in this example.

```bash
helm install etcd \
  oci://registry-1.docker.io/bitnamicharts/etcd \
  --version 10.2.12 \
  --set replicaCount=3 \
  --set auth.rbac.create=false \
  --set auth.rbac.token.enabled=false \
  --create-namespace \
  -n etcd-cluster
```

--------------------------------

### Start GreptimeDB in Standalone Mode with HTTP Address

Source: https://docs.greptime.com/0.12/user-guide/deployments/configuration

This command starts GreptimeDB in standalone mode and configures the HTTP address for communication. It's a basic example of using command-line arguments for configuration.

```shell
greptime standalone start --http-addr 127.0.0.1:4000
```

--------------------------------

### Start GreptimeDB Frontend with Configuration

Source: https://docs.greptime.com/0.14/reference/command-lines

Demonstrates starting a GreptimeDB Frontend instance using a specified configuration file with the '-c' option.

```bash
greptime frontend start -c config/frontend.example.toml
```

--------------------------------

### GreptimeDB Frontend Start Help

Source: https://docs.greptime.com/0.13/reference/command-lines

Displays the help information for the 'greptime frontend start' command, listing all available configuration options for the frontend service.

```bash
greptime frontend start --help
```

--------------------------------

### Install GreptimeDB Operator with Helm

Source: https://docs.greptime.com/0.12/user-guide/deployments/deploy-on-kubernetes/getting-started

This command installs the GreptimeDB Operator using Helm into the 'greptimedb-admin' namespace, creating the namespace if it doesn't exist. It manages the lifecycle of GreptimeDB clusters.

```bash
helm install greptimedb-operator greptime/greptimedb-operator -n greptimedb-admin --create-namespace  
```

--------------------------------

### Start GreptimeDB Standalone (Binary)

Source: https://docs.greptime.com/0.15/getting-started/installation/greptimedb-standalone

Starts the GreptimeDB server in standalone mode after the binary has been downloaded and is available in the current directory.

```bash
./greptime standalone start
```

--------------------------------

### Install GreptimeDB Cluster with Custom Configuration

Source: https://docs.greptime.com/0.12/user-guide/deployments/deploy-on-kubernetes/getting-started

This command installs the GreptimeDB cluster using Helm with a custom values file and specified namespace. It assumes a `values.yaml` file is present for configuration.

```bash
helm install {cluster} \
  --set monitoring.enabled=true \
  --set grafana.enabled=true \
  greptime/greptimedb-cluster \
  -f values.yaml \
  -n ${namespace}
```

--------------------------------

### Show Greptime Frontend Start Help

Source: https://docs.greptime.com/reference/command-lines/frontend

Displays all available options for the `greptime frontend start` command, allowing users to see configuration parameters and their descriptions.

```bash
greptime frontend start --help
```

--------------------------------

### Create Kubernetes Cluster with Kind

Source: https://docs.greptime.com/0.12/user-guide/deployments/deploy-on-kubernetes/getting-started

This command initiates the creation of a local Kubernetes cluster using the 'kind' tool. It's suitable for testing but not recommended for production environments.

```bash
kind create cluster  
```

--------------------------------

### Run GreptimeDB Unit Tests

Source: https://docs.greptime.com/contributor-guide/getting-started

After installing nextest, this command executes the entire unit test suite for GreptimeDB. This is crucial for verifying the integrity of the codebase.

```rust
cargo nextest run
```

--------------------------------

### Build GreptimeDB

Source: https://docs.greptime.com/0.13/contributor-guide/getting-started

This command demonstrates how to build the GreptimeDB server without running it. The `--release` flag can be used for an optimized build.

```Rust
cargo build # --release
```

--------------------------------

### GreptimeDB Standalone Start Help

Source: https://docs.greptime.com/0.13/reference/command-lines

Displays the help information for the 'greptime standalone start' command, outlining all available configuration options for the standalone mode.

```bash
greptime standalone start --help
```

--------------------------------

### Check Greptime Custom Resource Definitions (CRDs)

Source: https://docs.greptime.com/0.12/user-guide/deployments/deploy-on-kubernetes/getting-started

This command lists all Custom Resource Definitions (CRDs) in the Kubernetes cluster and filters them for those related to 'greptime'. It verifies the installation of CRDs necessary for managing GreptimeDB resources.

```bash
kubectl get crds | grep greptime  
```

--------------------------------

### GreptimeDB Standalone Start Help

Source: https://docs.greptime.com/0.12/reference/command-lines

Displays the help information for the 'greptime standalone start' command, outlining all available configuration options for the standalone mode.

```bash
greptime standalone start --help
```

--------------------------------

### Ingest Data using InfluxDB Line Protocol

Source: https://docs.greptime.com/0.14/getting-started/quick-start

Example data formatted in InfluxDB Line Protocol for ingestion into GreptimeDB. This format includes measurement, tags, fields, and a timestamp, allowing for efficient data loading.

```InfluxDB Line Protocol
grpc_metrics,host=host1,method_name=GetUser latency=100,code=0 1720728021000000000
grpc_metrics,host=host2,method_name=GetUser latency=110,code=1 1720728021000000000
```

--------------------------------

### Ingest Data using SQL INSERT in GreptimeDB

Source: https://docs.greptime.com/user-guide/ingest-data/for-iot/overview

This guide explains how to use SQL INSERT statements to create tables and insert data into GreptimeDB. It provides examples for the 'monitor' table, demonstrating the process of getting data into the database.

```SQL
CREATE TABLE monitor (ts TIMESTAMP NOT NULL, cpu DOUBLE, memory DOUBLE);
INSERT INTO monitor (ts, cpu, memory) VALUES (1678886400000, 0.5, 2048);
```

--------------------------------

### Show Metasrv Start Help

Source: https://docs.greptime.com/nightly/reference/command-lines/metasrv

Displays all available options and their descriptions for the `greptime metasrv start` command. This is useful for understanding the full range of configurations available.

```bash
greptime metasrv start --help
```

--------------------------------

### Greptime CLI Example: Get Single Key-Value Pair

Source: https://docs.greptime.com/0.15/reference/command-lines/utilities/metadata-interaction

An example demonstrating how to retrieve a single key-value pair using the 'greptime cli meta get key' command, specifying the store address and backend.

```bash
greptime cli meta get key --store-addrs=$ENDPOINT \
    --backend=postgres-store \
    __table_name/greptime/public/metric_table_2
```

```json
__table_name/greptime/public/metric_table_2  
{"table_id":1059}  
```

--------------------------------

### Start GreptimeDB Standalone (Binary)

Source: https://docs.greptime.com/0.14/getting-started/installation/greptimedb-standalone

This command starts the GreptimeDB server in standalone mode after the binary has been downloaded and placed in the current directory.

```bash
./greptime standalone start
```

--------------------------------

### Ingest Data using InfluxDB Line Protocol

Source: https://docs.greptime.com/nightly/getting-started/quick-start

This example shows how to ingest data into GreptimeDB using the InfluxDB Line Protocol format. It demonstrates writing metric data points with associated tags and values, which will automatically create the 'grpc_metrics' table if it doesn't exist.

```Shell
grpc_metrics,host=host1,method_name=GetUser latency=100,code=0 1720728021000000000  
grpc_metrics,host=host2,method_name=GetUser latency=110,code=1 1720728021000000000  
```

--------------------------------

### Ingest Data using InfluxDB Line Protocol

Source: https://docs.greptime.com/getting-started/quick-start

This example shows how to ingest data into GreptimeDB using the InfluxDB Line Protocol format. It demonstrates writing metric data points with associated tags and values, which will automatically create the 'grpc_metrics' table if it doesn't exist.

```Shell
grpc_metrics,host=host1,method_name=GetUser latency=100,code=0 1720728021000000000  
grpc_metrics,host=host2,method_name=GetUser latency=110,code=1 1720728021000000000  
```

--------------------------------

### GreptimeDB Flownode Start Help

Source: https://docs.greptime.com/0.12/reference/command-lines

Displays the help information for the 'greptime flownode start' command, detailing all available configuration options for the flownode service.

```bash
greptime flownode start --help
```

--------------------------------

### Install Strimzi Kafka Operator

Source: https://docs.greptime.com/0.14/user-guide/administration/remote-wal/cluster-deployment

Creates the 'kafka' namespace and installs the Strimzi Kafka operator using its latest installation manifest. Strimzi simplifies Kafka deployment on Kubernetes.

```bash
kubectl create namespace kafka
kubectl create -f 'https://strimzi.io/install/latest?namespace=kafka' -n kafka
```

--------------------------------

### Connect to GreptimeDB using MySQL Client

Source: https://docs.greptime.com/nightly/getting-started/quick-start

This snippet shows the command to connect to a GreptimeDB instance using the MySQL client. It assumes the instance is running on the default host and port.

```Shell
mysql -h 127.0.0.1 -P 4002
```

--------------------------------

### GreptimeDB Flownode Start Help

Source: https://docs.greptime.com/0.13/reference/command-lines

Displays the help information for the 'greptime flownode start' command, detailing all available configuration options for the flownode service.

```bash
greptime flownode start --help
```

--------------------------------

### Show GreptimeDB Standalone Start Help

Source: https://docs.greptime.com/0.15/reference/command-lines/standalone

Displays all available options for the `greptime standalone start` command. This is useful for understanding the various configurations and flags that can be used when launching GreptimeDB in standalone mode.

```bash
greptime standalone start --help
```

--------------------------------

### Upgrade GreptimeDB Version

Source: https://docs.greptime.com/user-guide/deployments-administration/overview

Follow this upgrade guide to keep your GreptimeDB installation up-to-date with the latest features and security patches.

```bash
# Example command for upgrading GreptimeDB (conceptual)
# greptimedb-ctl upgrade --version 0.18.0
```

--------------------------------

### Fix install script

Source: https://docs.greptime.com/release-notes/release-0-9-2

Resolves issues with the installation script, ensuring a smoother and more reliable setup process. Contributed by @v0y4g3r.

```Rust
fix: install script by @v0y4g3r in #4527
```

--------------------------------

### Connect to GreptimeDB using PostgreSQL Client

Source: https://docs.greptime.com/getting-started/quick-start

Connect to a GreptimeDB instance running on the default PostgreSQL port (4003) using the PostgreSQL command-line client.

```Shell
psql -h 127.0.0.1 -p 4003 -d public
```

--------------------------------

### Connect to GreptimeDB using PostgreSQL Client

Source: https://docs.greptime.com/0.13/getting-started/quick-start

This snippet demonstrates connecting to a GreptimeDB instance using the PostgreSQL client. It specifies the host, port, and database name for the connection.

```Shell
psql -h 127.0.0.1 -p 4003 -d public  
```

--------------------------------

### Install telemetrygen

Source: https://docs.greptime.com/nightly/user-guide/traces/read-write

This command installs the `telemetrygen` tool, which is used to generate trace data. Ensure you have Go installed and configured in your PATH. The `@latest` tag ensures you get the most recent version.

```Go
go install github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen@latest
```

--------------------------------

### GreptimeDB Specific Database Backup and Restore Example

Source: https://docs.greptime.com/0.13/user-guide/administration/disaster-recovery/back-up-%26-restore-data

Provides examples for exporting and importing a specific database in GreptimeDB.

```bash
# To export a specific database
greptime cli export --addr localhost:4000 --output-dir /tmp/backup/greptimedb --database '{my_database_name}'

# The same applies to import tool
greptime cli import --addr localhost:4000 --input-dir /tmp/backup/greptimedb --database '{my_database_name}'
```

--------------------------------

### Start GreptimeDB Frontend with Configuration File

Source: https://docs.greptime.com/0.15/reference/command-lines/frontend

Starts a GreptimeDB frontend instance using a specified configuration file, enabling customized service behavior.

```bash
greptime frontend start -c config/frontend.example.toml
```

--------------------------------

### Install GreptimeDB Standalone (Basic)

Source: https://docs.greptime.com/user-guide/deployments-administration/deploy-on-kubernetes/deploy-greptimedb-standalone

Installs the GreptimeDB standalone Helm chart with default configurations in the 'default' namespace. This is a quick start option.

```bash
helm upgrade --install greptimedb-standalone greptime/greptimedb-standalone -n default  
```

--------------------------------

### Install Strimzi Kafka Operator

Source: https://docs.greptime.com/0.12/user-guide/administration/remote-wal/cluster-deployment

Creates the 'kafka' namespace and installs the Strimzi Kafka operator, which is used to manage Kafka clusters in Kubernetes.

```bash
kubectl create namespace kafka
kubectl create -f 'https://strimzi.io/install/latest?namespace=kafka' -n kafka
```

--------------------------------

### Connect to GreptimeDB using MySQL Client

Source: https://docs.greptime.com/getting-started/quick-start

Connect to a GreptimeDB instance running on the default MySQL port (4002) using the MySQL command-line client.

```Shell
mysql -h 127.0.0.1 -P 4002
```

--------------------------------

### GreptimeDB EXPLAIN Example Query

Source: https://docs.greptime.com/0.15/reference/sql/explain

An example of using the EXPLAIN command to get the logical and physical execution plan for a SELECT statement in GreptimeDB.

```SQL
EXPLAIN SELECT * FROM monitor where host='host1'\G  
```

--------------------------------

### Start GreptimeDB Frontend with Configuration

Source: https://docs.greptime.com/0.13/reference/command-lines

Starts a GreptimeDB frontend instance using a custom configuration file.

```bash
greptime frontend start -c config/frontend.example.toml
```

--------------------------------

### Start GreptimeDB Standalone (Windows)

Source: https://docs.greptime.com/nightly/getting-started/installation/greptimedb-standalone

This command starts the GreptimeDB server in standalone mode on Windows using PowerShell, assuming the binary is in the current directory.

```PowerShell
.\greptime standalone start
```

--------------------------------

### Start GreptimeDB Standalone (Binary)

Source: https://docs.greptime.com/0.16/getting-started/installation/greptimedb-standalone

This command starts the GreptimeDB server in standalone mode after the binary has been downloaded and placed in the current directory. It assumes the 'greptime' binary is executable.

```bash
./greptime standalone start
```

--------------------------------

### Start GreptimeDB Frontend with Configuration

Source: https://docs.greptime.com/0.12/reference/command-lines

Starts a GreptimeDB frontend instance using a custom configuration file.

```bash
greptime frontend start -c config/frontend.example.toml
```