Skip to content

Commit f72d1d0

Browse files
committed
modified getting started page
1 parent 72f40e0 commit f72d1d0

File tree

1 file changed

+273
-5
lines changed

1 file changed

+273
-5
lines changed

docs/getting-started.md

Lines changed: 273 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,277 @@
1-
# Getting Started
1+
# OpenObserve Quickstart Guide
22

3-
Check [quickstart](./quickstart.md) to experience the power and simplicity of OpenObserve.
3+
This guide will help you get started with OpenObserve in under 10 minutes. You can choose between [OpenObserve Cloud](https://cloud.openobserve.ai) (recommended) or a self-hosted installation.
44

5-
Check the below video for a quick demo/getting started of OpenObserve.
5+
## Choose Your Installation Method
66

7-
## OpenObserve introduction video
7+
### [OpenObserve Cloud](https://cloud.openobserve.ai) (Recommended)
88

9-
[![OpenObserve Youtube](./images/zo_intro_youtube.webp)](https://www.youtube.com/watch?v=fZ-ErfMdF-o)
9+
OpenObserve Cloud is the fastest way to get started and is recommended for most users because:
10+
11+
- **Zero maintenance**: No infrastructure setup or maintenance required
12+
- **Generous free tier**: Suitable for hobby projects, small companies, and startups
13+
- **Latest features**: Access to newest features and bug fixes first
14+
- **High availability**: Built-in redundancy and reliability
15+
16+
### Self-Hosted Installation
17+
18+
Choose self-hosted if you need:
19+
20+
- Full control over your data and infrastructure
21+
- Custom configurations or integrations
22+
- On-premises deployment requirements
23+
24+
25+
## Option 1: OpenObserve Cloud Setup
26+
27+
### Step 1: Create Your Account
28+
29+
1. Navigate to [https://cloud.openobserve.ai](https://cloud.openobserve.ai)
30+
2. Sign up using social login or create a new account
31+
32+
![Sign in page](./images/quickstart/signin.png)
33+
34+
### Step 2: Get Your Ingestion Credentials
35+
36+
1. After logging in, navigate to the **Data Sources** section in the sidebar
37+
38+
![Ingestion](./images/quickstart/ingestion_credentials.png)
39+
40+
2. Copy the provided cURL command - it contains your unique credentials
41+
3. Your endpoint will look like: `https://api.openobserve.ai/api/[YOUR_ORG]/default/_json`
42+
43+
You are ready to ingest data. Now head over to [Load sample data](#load-sample-data) section.
44+
45+
## Option 2: Self-Hosted Installation
46+
47+
**Important**: These instructions are for single-node installations. For production high-availability setups, see our [HA deployment guide](./ha_deployment.md).
48+
49+
You'll need to set root user credentials (ZO_ROOT_USER_EMAIL and ZO_ROOT_USER_PASSWORD) on first startup only. They are not required for subsequent runs.
50+
51+
### Windows Installation
52+
53+
1. Download the Windows binary from our [releases page](https://github.com/openobserve/openobserve/releases)
54+
2. Open Command Prompt or PowerShell as Administrator
55+
3. Run the following commands:
56+
57+
```cmd
58+
# Command Prompt
59+
60+
set ZO_ROOT_USER_PASSWORD=Complexpass#123
61+
openobserve.exe
62+
```
63+
64+
```powershell
65+
# PowerShell
66+
$env:ZO_ROOT_USER_EMAIL="[email protected]"
67+
$env:ZO_ROOT_USER_PASSWORD="Complexpass#123"
68+
.\openobserve.exe
69+
```
70+
> **Note:** You can set email and password based on your preference
71+
72+
### macOS/Linux Installation
73+
74+
**Option A: Quick Install Script**
75+
```bash
76+
# Download and install latest version automatically
77+
curl -L https://raw.githubusercontent.com/openobserve/openobserve/main/download.sh | sh
78+
79+
# Run OpenObserve
80+
ZO_ROOT_USER_EMAIL="[email protected]" ZO_ROOT_USER_PASSWORD="Complexpass#123" ./openobserve
81+
```
82+
83+
**Option B: Manual Download**
84+
85+
1. Download the appropriate binary from our [releases page](https://github.com/openobserve/openobserve/releases)
86+
2. Make it executable: `chmod +x openobserve`
87+
3. Run with environment variables as shown:
88+
```bash
89+
# Run OpenObserve
90+
ZO_ROOT_USER_EMAIL="[email protected]" ZO_ROOT_USER_PASSWORD="Complexpass#123" ./openobserve
91+
```
92+
93+
**Troubleshooting glibc Errors**
94+
95+
If you see an error like `version GLIBC_2.27 not found`, download the `musl` binary instead:
96+
- Look for files ending in `-linux-musl.tar.gz` on the releases page
97+
98+
> Note: musl binaries have slightly lower performance but no external dependencies
99+
100+
### Docker Installation
101+
102+
**Prerequisites**: Ensure Docker is installed and running on your system.
103+
104+
Docker images are available at [https://gallery.ecr.aws/zinclabs/openobserve](https://gallery.ecr.aws/zinclabs/openobserve)
105+
106+
```bash
107+
# Create a data directory
108+
mkdir -p ./openobserve-data
109+
110+
# Run OpenObserve container
111+
docker run -d \
112+
--name openobserve \
113+
-v ./openobserve-data:/data \
114+
-e ZO_DATA_DIR="/data" \
115+
-e ZO_ROOT_USER_EMAIL="[email protected]" \
116+
-e ZO_ROOT_USER_PASSWORD="Complexpass#123" \
117+
-p 5080:5080 \
118+
public.ecr.aws/zinclabs/openobserve:latest
119+
```
120+
121+
**Windows Docker Command**:
122+
```cmd
123+
# Windows Command Prompt
124+
docker run -d --name openobserve -v %cd%/openobserve-data:/data -e ZO_DATA_DIR="/data" -e ZO_ROOT_USER_EMAIL="[email protected]" -e ZO_ROOT_USER_PASSWORD="Complexpass#123" -p 5080:5080 public.ecr.aws/zinclabs/openobserve:latest
125+
```
126+
127+
**Docker Image Options**:
128+
129+
- `latest`: Compatible with most environments
130+
- `latest-simd`: Optimized for systems with AVX512 (Intel) or NEON (ARM) for better performance
131+
132+
**Troubleshooting Docker Issues**:
133+
134+
If you encounter AWS ECR login issues:
135+
```bash
136+
aws ecr-public get-login-password --region us-east-1 | docker login --username AWS --password-stdin public.ecr.aws
137+
```
138+
139+
### Kubernetes Installation
140+
141+
**Prerequisites**: Ensure `kubectl` is configured and you have cluster access.
142+
143+
1. Create namespace:
144+
```bash
145+
kubectl create namespace openobserve
146+
```
147+
148+
2. Deploy OpenObserve:
149+
```bash
150+
kubectl apply -f https://raw.githubusercontent.com/zinclabs/openobserve/main/deploy/k8s/statefulset.yaml
151+
```
152+
153+
3. Access the service:
154+
```bash
155+
kubectl -n openobserve port-forward svc/openobserve 5080:5080
156+
```
157+
158+
## Verify Installation
159+
160+
After installation, verify OpenObserve is running:
161+
162+
1. Open your browser and navigate to:
163+
- **Self-hosted**: [http://localhost:5080](http://localhost:5080)
164+
- **Cloud**: [https://cloud.openobserve.ai](https://cloud.openobserve.ai)
165+
166+
2. Log in with your credentials:
167+
- **Self-hosted**: Use the email/password you set in environment variables
168+
- **Cloud**: Use your account credentials
169+
170+
3. You should see the OpenObserve dashboard
171+
172+
173+
## Load Sample Data
174+
175+
Let's load some real-world log data to explore OpenObserve's features.
176+
177+
### Step 1: Download Sample Data
178+
179+
```bash
180+
# Download and extract sample Kubernetes logs
181+
curl -L https://zinc-public-data.s3.us-west-2.amazonaws.com/zinc-enl/sample-k8s-logs/k8slog_json.json.zip -o k8slog_json.json.zip
182+
unzip k8slog_json.json.zip
183+
```
184+
185+
**What's in the sample data**: This file contains real Kubernetes application logs with various log levels (info, warning, error) and structured JSON fields.
186+
187+
### Step 2: Load Data into OpenObserve
188+
189+
**For OpenObserve Cloud**:
190+
```bash
191+
# Use the cURL command from your Ingestion page
192+
curl -u [email protected]:your-password \
193+
-H "Content-Type: application/json" \
194+
https://api.openobserve.ai/api/YOUR_ORG/default/_json \
195+
-d "@k8slog_json.json"
196+
```
197+
198+
**For Self-Hosted Installation**:
199+
```bash
200+
curl -u "[email protected]:Complexpass#123" \
201+
-H "Content-Type: application/json" \
202+
http://localhost:5080/api/default/default/_json \
203+
-d "@k8slog_json.json"
204+
```
205+
206+
### Step 3: Verify Data Upload
207+
208+
You should see output similar to:
209+
```json
210+
{"code":200,"status":"ok","records":1000}
211+
```
212+
213+
If you see errors, check:
214+
- Your credentials are correct
215+
- The JSON file was downloaded completely
216+
- OpenObserve is running and accessible
217+
218+
219+
## Search Your Data
220+
221+
Now let's explore the data you just loaded.
222+
223+
**Step 1: Access the Logs Interface**
224+
225+
1. Navigate to your OpenObserve instance
226+
2. Click on **Logs** in the left sidebar
227+
3. Select **default** from the stream dropdown (top-left)
228+
229+
![Logs page](./images/quickstart/logs_page.png)
230+
231+
232+
**Step 2: Try These Sample Searches**
233+
234+
**Basic searches** (click the **Run Query** button after each):
235+
236+
1. **View all logs**: Leave search box empty and click search
237+
2. **Find errors**: `level='error'` or `match_all('error')`
238+
239+
*Congratulations! You now have OpenObserve running with sample data.*
240+
241+
242+
## Next Steps - Send Your Own Data
243+
244+
- **Application logs**: Use our [logging libraries](./ingestion/logs/otlp.md) for your applications
245+
- **Metrics**: Set up [Prometheus integration](./ingestion/metrics/prometheus.md)
246+
- **Traces**: Configure [OpenTelemetry](./ingestion/traces/opentelemetry.md) for distributed tracing
247+
248+
249+
## Troubleshooting Common Issues
250+
251+
**Can't access OpenObserve web interface**:
252+
253+
- Check if the process is running
254+
- Verify port 5080 is not blocked by firewall
255+
- For Docker: ensure port mapping is correct (`-p 5080:5080`)
256+
257+
**Authentication errors**:
258+
259+
- Verify your email/password combination
260+
- For self-hosted: ensure environment variables were set correctly
261+
- For cloud: check your account credentials
262+
263+
**Data not appearing**:
264+
265+
- Verify the curl command returned success (200 status)
266+
- Check the time range in the web interface
267+
- Ensure you selected the correct stream/index
268+
269+
**Performance issues**:
270+
271+
- Consider using the SIMD Docker image for better performance
272+
- Check available memory and CPU resources
273+
- For large datasets, consider the high-availability deployment
274+
275+
### Getting Support
276+
277+
If you're still having issues, Join our [Slack Community](https://short.openobserve.ai/community) for help

0 commit comments

Comments
 (0)