cnosdb
pq
cnosdb | pq | |
---|---|---|
1 | 7 | |
1,584 | 356 | |
2.0% | - | |
9.7 | 0.0 | |
8 days ago | over 1 year ago | |
Rust | Rust | |
GNU Affero General Public License v3.0 | MIT License |
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.
cnosdb
pq
- Pq – Parse and Query files with PromQL-like query language
- pq - Parse and Query files with PromQL-like query language
- Pq – parse and query log files as time series
-
Reading metrics from not instrumented servers
Hi folks! I’m working on a tool for ad-hoc metric extraction and I’m really curious to hear back from the fellow DevOps people. I often find myself in situations when some metrics aren’t collected. Some servers may be simply not onboarded to the metric collection system yet. Some breakdowns may not exist because of the high-cardinality issue, especially per-pod breakdowns. And some metrics we just may haven’t thought about in advance. So, I hacked a tool called pq to parse and query logs as metrics. It seems to work and I have some ideas for further development. For instance, by adding a tiny HTTP adapter to it, it would be able to mimic Prometheus API, so one would be able to attach Grafana to an exposed port and query metrics from the UI. But before going any further with it, I’d like to hear back from the potential users.
Hi fellow SREs! What do you usually do when you need to make an ad-hoc analysis of some metrics that aren't collected yet? For instance, if there is no per-pod request latency measurement, but you want to see how a particular pod behaves? I often find myself in situations like that but I'm not aware of a common solution, so I hacked a tool called pq. It can parse log files into structured streams and then query these steams with PromQL-like language.
- pq - Parse and Query log files as time series
- Show HN: Pq – parse and query log files as time series
What are some alternatives?
InfluxDB - Scalable datastore for metrics, events, and real-time analytics
grok_exporter - Export Prometheus metrics from arbitrary unstructured log data.
greptimedb - An open-source, cloud-native, distributed time-series database with PromQL/SQL/Python supported. Available on GreptimeCloud.
tstorage - An embedded time-series database
marketstore - DataFrame Server for Financial Timeseries Data
qrono - Qrono time-ordered queue server
sonic - 🦔 Fast, lightweight & schema-less search backend. An alternative to Elasticsearch that runs on a few MBs of RAM.
MeiliSearch - A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
rustDTW - Python extension backed by a multi-threaded Rust implementation of Dynamic Time Warping (DTW).