opentelemetry-collector-co
cockpit-podman
opentelemetry-collector-co | cockpit-podman | |
---|---|---|
10 | 4 | |
- | 390 | |
- | 1.8% | |
- | 9.5 | |
- | 7 days ago | |
JavaScript | ||
- | GNU Lesser General Public License v3.0 only |
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.
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...
cockpit-podman
-
Monitoring and visibility of rootless containers running by different users on single server
Hey, I have homelab NUC server where I run different services as rootless podman pods and containers running by dedicated users, eg. nextcloud pod running by nextcloud user, gitea by gitea, znc by znc and more. Next step was trying to monitor these services. First trey was using cockpit-podman feature, but in UI I see only containers of my user and rootfull which both was empty. I cannot switch to another user because the're not capable for login to cockpit. Now I'm testing prometheus and podman-exporter which seems ok, but again I see containers only if I run prometheus-podman-exporter service as user who run another podman container (e.g. as nextcloud user). Of course I can run this service parallel as dedicated user with another port and add them as target to prometheus scrape config but from obvious reason I want to avoid that. Is it more gentle way to monitor my pods? I know that those namespaces are one of the main feature of Podman but I don't consider this before my deploys :)
- Cockpit Project
-
Front end ...gui for podman.
Cockpit has a podman module (cockpit-podman)
-
Podman: A tool for managing OCI containers and pods
Tested podman to replace docker (the cli) on a mac yesterday Most of it works fine. They have an easy way to setup a vm now with `podman machine`: https://podman.io/getting-started/installation#macos
If you want the management GUI, install cockpit: https://github.com/cockpit-project/cockpit-podman
Try podman, you'll be impressed.
What are some alternatives?
podman-compose - a script to run docker-compose.yml using podman
traefik - The Cloud Native Application Proxy
logs-benchmark - Logs performance benchmark repo: Comparing Elastic, Loki and SigNoz
machine
dd-trace-py - Datadog Python APM Client
opentelemetry-collector-contrib - Contrib repository for the OpenTelemetry Collector
toolbox - Tool for interactive command line environments on Linux
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
singularity - Singularity has been renamed to Apptainer as part of us moving the project to the Linux Foundation. This repo has been persisted as a snapshot right before the changes.