Skip to main content

Show HN: Columnar store for fast, lightweight logging https://ift.tt/EO0SoZ1

Show HN: Columnar store for fast, lightweight logging Founder here, Parseable is a lightweight log ingestion and query engine written in Rust. Parseable can ingest data from existing logging agents (FluentBit, LogStash, Vector, syslog-ng and more) using HTTP + JSON output. Ingested logs are stored as semi-indexed Parquet files (on disk or S3). You can query the data with builtin query engine using SQL or use a query engines of choice like Spark, Presto, Trino and so on. We also developed a Grafana data source plugin that lets you visualise log data via Grafana. Sample dashboard link in readme. As log data grew, our industry has responded with SaaS and fully managed offerings, but if you're looking for freedom, interoperability and full control over your data - there are no great options. With Parseable, we are looking to provide an strong, viable and FOSS alternative. https://ift.tt/WgAex9z January 18, 2023 at 10:06PM

Comments

Popular posts from this blog

Show HN: TypeScript query builder with full type inference https://ift.tt/xZp9HOm

Show HN: TypeScript query builder with full type inference Hey HN! Colin here - a TypeScripter, open sourcer, and engineer at EdgeDB. As the creator of Zod and tRPC, I'm interested in designing tools/APIs that use type inference and generics to make life easier for devs. This query builder represents another step in that direction. We set out to build an EdgeQL query builder that can express queries of arbitrary complexity (EdgeQL has feature parity with SQL, roughly) and infer the static type of the query result. We introspect the database and generate a schema-aware client that represent any query, including ones that use built-in functions, operators, string/array/tuple indexing, aggregations, conditionals, type casting, subqueries, computed properties, etc—things most ORMs can’t represent. This post mostly discusses the API design, which I think will be interesting regardless of familiarity with EdgeQL. I’d love to see some of these ideas bleed into future generations of TypeSc...