db-benchmarks
opentelemetry-collector-co
db-benchmarks | opentelemetry-collector-co | |
---|---|---|
24 | 10 | |
111 | - | |
2.7% | - | |
4.9 | - | |
12 months ago | - | |
PHP | ||
GNU Affero General Public License v3.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
db-benchmarks
-
Dozer vs. AirByte and Elasticsearch: The Fast Lane to Data Serving Efficiency
> I decided to experiment with this setup and the NY Taxi Dataset. The initial goal was to populate ElasticSearch with ~14 million rows, loading data from a compressed parquet file of ~350 MB.
> I tried multiple times, but the operation failed continuously, due to JVM memory constraints
Here's a script https://github.com/db-benchmarks/db-benchmarks/blob/main/tes... which loads 1.7B NYC taxi ride documents into Elasticsearch.
-
Meilisearch vs Manticore Search
In general, you are correct about another missing key: since we added an exception for MySQL by including two keys, we should perhaps optimize it to the maximum and add the rest as well. However, it would be better to make this more visible directly within the results then. I've created a task about it https://github.com/db-benchmarks/db-benchmarks/issues/30 . Thank you for pointing this out. If you see more issues, feel free to file them on github.
- Elastic, Loki and SigNoz – A Perf Benchmark of Open-Source Logging Platforms
-
ZincSearch – lightweight alternative to Elasticsearch written in Go
> It's interesting to note that Elasticsearch and Opensearch are general purpose search engine, Solr as well. They are all powered by Lucene, the popular and performant search engine library.
Another search engine which can be considered general, is not based on Lucene and is not less powerful than Elasticsearch/Solr is Manticore Search [1]
[1]: https://github.com/manticoresoftware/manticoresearch
> I would love to see some benchmarks by category :)
I'd love too. We started this work on db-benchmarks [2] , hopefully we'll have resources to continue it. Contributions are very welcome. It's 100% opensource [3]
[2]: https://db-benchmarks.com/
-
Manticore Search: Elasticsearch Alternative
Comparing full-text search engines on queries that aren't full-text search are of course slow, these tests should be adapted to the proper usage of the tested DBs and not just benchmarked across the board..
Example: https://db-benchmarks.com/?cache=fast_avg&engines=elasticsea...
- No, QuestDB is not Faster than ClickHouse
- Announcing DB Benchmarks - the most fair open source database and search engines benchmarks
-
110 million comments from Hacker News benchmark
Clickhouse: no tuning , just CREATE TABLE ... ENGINE = MergeTree() ORDER BY id and standard clickhouse-server docker image.
-
1.1 million comments from Hacker News: small data full-text / analytics test
MySQL and Percona Server for MySQL: no tuning , just CREATE TABLE ..., FULLTEXT(story_text,story_author,comment_text,comment_author))and standard mysql docker image .
-
Announcing DB Benchmarks - the most fair open source database benchmarks
https://db-benchmarks.com is a platform and a framework for making the most fair, transparent and open source database and search engines benchmarks. No more benchmarketing, because:
opentelemetry-collector-co
-
All you need is Wide Events, not "Metrics, Logs and Traces"
The open telemetry collector does just that. https://github.com/open-telemetry/opentelemetry-collector-co...
-
Migrating to OpenTelemetry
If you are using the prometheus exporter, you can use the transform processor to get specific resource attributes into metric labels.
With the advantage that you get only the specific attributes you want, thus avoiding a cardinality explosion.
https://github.com/open-telemetry/opentelemetry-collector-co...
-
Vendor lock-in is in the small details
The article seems to suggest https://github.com/open-telemetry/opentelemetry-collector-co... was silently killed, yet it appears to have been merged in January, am I missing something?
-
Ask HN: What's Your Opinion on Opentelemetry?
OpenTelemetry is a large suite of software, that supports many use cases. I think you got what you wanted but didn't realised it!
The dedicated executable that you are after is called the OpenTelemtry Collector.
The OpenTelemetry SDK for language of choice should include many exporters, which describe the format and transport mechanism for the traces. The OpenTelemetry Collector can then use an appropriate receiver to ingest those traces.
Here is a file based receiver for the collector:
https://github.com/open-telemetry/opentelemetry-collector-co...
-
OpenTelemetry at Scale: Using Kafka to handle bursty traffic
This arch is how the big players do it at scale (ie. datadog, new relic - the second it passes their edge it lands in a kafka queue). Also otel components lack rate limiting(1) meaning its super easy to overload your backend storage (s3).
Grafana has some posts how they softened the s3 blow with memcached(2,3).
1. https://github.com/open-telemetry/opentelemetry-collector-co...
-
Show HN: HyperDX – open-source dev-friendly Datadog alternative
Ah yeah the easiest way is probably using the OpenTelemetry collector to set up a process to pull your logs out of jounrnald and send them via otel logs to HyperDX (or anywhere else that speaks otel) - the docs might be a bit tricky to go around depending on your familiarity with OpenTelemetry but this is what you'd be looking for:
https://github.com/open-telemetry/opentelemetry-collector-co...
Happy to dive more into the discord too if you'd like!
-
DataDog asked OpenTelemetry contributor to kill pull request
Link to exact comment: https://github.com/open-telemetry/opentelemetry-collector-co...
-
Elastic, Loki and SigNoz – A Perf Benchmark of Open-Source Logging Platforms
What schema does SigNoz use with Clickhouse? The Open Telemetry Collector uses this schema https://github.com/open-telemetry/opentelemetry-collector-co... and I found out that accesing map attributes is much slower (10-50x) compared to regular columns. I expected some slow down but this is too much.
-
Podman: A tool for managing OCI containers and pods
Podman does support docker API so you can use something like the OpenTelemetry Collector to fetch metrics using the docker API and forward them to prometheus.
Collector: https://github.com/open-telemetry/opentelemetry-collector-co...
Docker receiver: https://github.com/open-telemetry/opentelemetry-collector-co...
Prometheus exporters: https://github.com/open-telemetry/opentelemetry-collector-co... and https://github.com/open-telemetry/opentelemetry-collector-co...
What are some alternatives?
Elasticsearch - Free and Open, Distributed, RESTful Search Engine
podman-compose - a script to run docker-compose.yml using podman
mu - maildir indexer/searcher + emacs mail client + guile bindings
cockpit-podman - Cockpit UI for podman containers
pagefind - Static low-bandwidth search at scale
traefik - The Cloud Native Application Proxy
beir - A Heterogeneous Benchmark for Information Retrieval. Easy to use, evaluate your models across 15+ diverse IR datasets.
logs-benchmark - Logs performance benchmark repo: Comparing Elastic, Loki and SigNoz
ElasticPress - A fast and flexible search and query engine for WordPress.
dd-trace-py - Datadog Python APM Client
sonic - 🦔 Fast, lightweight & schema-less search backend. An alternative to Elasticsearch that runs on a few MBs of RAM.
opentelemetry-collector-contrib - Contrib repository for the OpenTelemetry Collector