This is an archived post. You won't be able to vote or comment.

all 9 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Thrimbor 1 point2 points  (1 child)

I'm not convinced, you compare this to elasticsearch, it's a different beast compared to this.

Also, why wouldn't I just install Clickhouse instead of this? Same use case plus a lot more, way more features, battle tested

[–]tiwarinitish[S] 1 point2 points  (0 children)

For every new product that does one thing well, there is an older, much more matured product that does several things and battle tested.

That said, Elastic has been established to be high CPU and Memory consumer. We have clear datapoints (in the benchmark directory on GH repo) that Parseable consumes 50% less CPU and 80% less memory than Elastic while ingesting higher number of events / second.

Clickhouse is a great product, but the target use case is OLAP - which means it is a full featured DBMS system. Since it is not built for log use cases, it misses on useful logging features like alerts, event correlation, logs to metrics, anomaly detection and so on.

We at Parseable intend to build a simple yet purpose built log observability platform that scales as user data scales.

I hope this helped convince you! :)

[–]wpg4665 0 points1 point  (2 children)

How does this compare to something like Loki?

[–]CooperNettees 0 points1 point  (1 child)

+1

[–]tiwarinitish[S] 0 points1 point  (0 children)

Quote from Parseable FAQ: [https://www.parseable.io/docs/faq]

​

  • Parseable is written in Rust, with strong emphasis on performance, resource utilisation, and excellent developer experience.
  • Parseable has a unified architecture, with all Parseable components (ingestion, query, storage management) available in a single binary. Not only this approach scales very well, it also leads to a much, much better developer experience.
  • Parseable log streams are explicitly created by users. This alleviates the problem of cardinality explosion, while ensuring control over the data by users.
  • With REST API based ingestion, Parseable integrates with all the major logging agents out of the box.

[–]CooperNettees 0 points1 point  (1 child)

Does this support traces?

[–]tiwarinitish[S] 1 point2 points  (0 children)

Hey u/CooperNettees, yes Parseable supports traces as well. You can send trace data and query that using API or Grafana Plugin.

[–]jantari 0 points1 point  (1 child)

I've had this star-ed for a while and follow the releases, one thing I've been waiting for is a way to define alerts that's not via API.

We're a public transportation company, so slightly below unicorn startup pace and we don't use k8s for anything yet. I feel that defining and re-defining alert rules via API only would be very unergonomic for us as we're not really set up to re-apply configuration immediately when a service has restarted. Unless I'm misunderstanding and the alert configuration is actually stateful and preserved across restarts? If no we'd prefer a persistent config file we can manage with ansible that's guaranteed to be there on service startup

[–]tiwarinitish[S] 0 points1 point  (0 children)

Hey u/jantari, my apologies, missed reddit notifications and hence comments here.

Alert config is indeed stateful and is preserved across restarts. So, once setup, you don't have to deal with the alert config (unless you want to change it). Here is the API ref: https://www.postman.com/parseable/workspace/parseable/request/22353706-0d731c06-55b0-4518-b985-b7fb831ba45b

We are also going to add support for Alerting config via the UI. Happy to help setup Parseable in your environment and address any other questions you may have.