You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parseable is a log analytics platform, built for the modern, cloud native era. Parseable uses a index-free mechanism to organize and query data allowing low latency, and high throughput ingestion and query.
22
+
Parseable is a **cloud native, log analytics platform, with a focus on performance & resource efficiency**. Parseable is useful for use cases where **complete data ownership, security and privacy are paramount**.
23
23
24
-
To get started, download the Parseable binary from [releases page ↗︎](https://github.com/parseablehq/parseable/releases/latest) and run it on your machine.
24
+
To experience Parseable UI, checkout [demo.parseable.com ↗︎](https://demo.parseable.com/login?q=eyJ1c2VybmFtZSI6ImFkbWluIiwicGFzc3dvcmQiOiJhZG1pbiJ9). You can also view the [demo video ↗︎](https://www.parseable.com/video.mp4).
25
25
26
-
For comparison, Parseable consumes up to **_~80% lower memory_** and **_~50% lower CPU_** than Elastic for similar ingestion throughput. Read more in the [benchmarks directory ↗︎](./benchmarks/).
You can <ahref="https://www.parseable.com/docs/docker-quick-start">get started with Parseable Docker</a> with a simple Docker run and then send data via cURL to understand how you can ingest data to Parseable. Below is the command to run Parseable in local storage mode with Docker.
31
33
32
-
## :zap: Quickstart
33
-
34
-
Deploy Parseable in local storage mode with Docker.
35
-
36
-
```sh
34
+
```bash
37
35
docker run -p 8000:8000 \
38
36
parseable/parseable:latest \
39
37
parseable local-store
@@ -43,7 +41,7 @@ Once this runs successfully, you'll see dashboard at [http://localhost:8000 ↗
43
41
44
42
To ingest data, run the below command. This will send logs to the `demo` stream. You can see the logs in the dashboard.
45
43
46
-
```sh
44
+
```bash
47
45
curl --location --request POST 'http://localhost:8000/api/v1/ingest' \
Traditionally, logging has been seen as a text search problem. Log volumes were not high, and data ingestion or storage were not really issues. This led us to today, where all the logging platforms are primarily text search engines.
75
+
- MacOS (Apple Silicon)
79
76
80
-
But with log data growing exponentially, today's log data challenges involve whole lot more – Data ingestion, storage, and observation, all at scale. We are building Parseable to address these challenges.
Once this runs successfully, you'll see dashboard at [http://localhost:8000 ↗︎](http://localhost:8000). You can login to the dashboard default credentials `admin`, `admin`.
91
99
92
-
### License report
100
+
To ingest data, run the below command. This will send logs to the `demo` stream. You can see the logs in the dashboard.
93
101
94
-
A license report lists all the licenses of all dependencies in a project. You can use [cargo-about ↗︎](https://embarkstudios.github.io/cargo-about/) to generate a license report for the Parseable.
102
+
```bash
103
+
curl --location --request POST 'http://localhost:8000/api/v1/ingest' \
If not already installed, install `cargo-about` using the below command.
116
+
</p>
117
+
</details>
97
118
98
-
```sh
99
-
cargo install --locked cargo-about && cargo about init
100
-
```
119
+
## Why Parseable :question:
101
120
102
-
To generate a license report, run the below command.
121
+
### Performance & resource efficiency
103
122
104
-
```sh
105
-
cargo about generate about.hbs > parseable-license.html
106
-
```
123
+
Parseable is written in Rust, with a clear focus on performance while ensuring a much lower CPU and memory footprint (compared to Java, Go based systems). When compared with Elastic, Parseable uses ~80% lesser memory and ~50% lesser CPU, while offering a better ingestion rate. This means you can run Parseable on smaller instances, saving costs.
124
+
125
+
### Easy of use
126
+
127
+
One of the key challenges users said they face today is the complexity of setting a logging system like Elastic. There are so many moving parts, and it's hard to get started. Parseable is designed to be simple to use, with a single binary that can be run on almost anywhere. The Console is built in the binary itself, so you can start using it without any additional setup.
128
+
129
+
### Take control of your data
130
+
131
+
With Apache Arrow and Apache Parquet as the underlying data formats, Parseable stores log data in an optimized, compressed manner as Parquet files. This means you get complete control and access to your data. You can use Parseable query and analysis, but also can plugin tools from wider Parquet ecosystem for further processing, analysis, and visualization.
132
+
133
+
### Enterprise ready
134
+
135
+
- High availability & Cluster mode
136
+
- Local cache & storage
137
+
-[OpenTelemetry support ↗︎](https://opentelemetry.io/)
You can see the license report in the file parseable-license.html.
145
+
## How do people use Parseable :bulb:
146
+
147
+
-**Audit & Compliance** - Organizations that need to store logs in a secure, compliant manner. Parseable's direct to S3 bucket storage mode ensures that logs are stored in a secure, cost effective manner, and can be accessed only by authorized users, while all the data is queryable in real-time.
148
+
149
+
-**Observability & Monitoring** - A very large chunk of observability data is logs. Organizations that need to monitor their systems, applications, and infrastructure in real-time use Parseable as the primary log storage system so they get timely alerts, and can analyze logs in real-time.
150
+
151
+
-**Log Analytics** - Not all logs are created equal. For example application logs are seldom useful after a few days pass, but if same application also logs all the user interactions, that data is very valuable for product managers, and can be stored for a longer period. Several businesses store such high value logs and slice / dice them as needed.
152
+
153
+
## Motivation :dart:
154
+
155
+
Traditionally, logging has been seen as a text search problem. Log volumes were not high, and data ingestion or storage were not really issues. This led us to today, where all the logging platforms are primarily text search engines.
156
+
157
+
But with log data growing exponentially, today's log data challenges involve whole lot more – Data ingestion, storage, and observation, all at scale. We are building Parseable to address these challenges.
Copy file name to clipboardExpand all lines: USERS.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
The following document is a list of users and adopters who use Parseable. The users themselves directly maintain the list. You can add your organization by editing this file directly.
4
4
5
-
If you're using Parseable in your organization, please add your company name to this list. It really helps the project gain momentum and credibility. It's a small contribution to the project with a big impact.
5
+
If you're using Parseable in your organization, please add your company name to this list. It really helps the project gain momentum and credibility. It's a small contribution to the project with a big impact.
0 commit comments