coroot
opentelemetry-collector-contrib
coroot | opentelemetry-collector-contrib | |
---|---|---|
33 | 45 | |
4,189 | 2,612 | |
18.5% | 5.6% | |
9.2 | 10.0 | |
9 days ago | 3 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.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.
coroot
- Coroot: Open-source alternative to Datadog/NewRelic
-
Show HN: Coroot: Simplified Observability for Modern Environments
I'm Peter Zaitsev, co-founder at Coroot. I come from the database world where observability, or monitoring, was crucial for keeping databases running smoothly. But as technology evolves, so do the challenges we face.
Today, many applications are built using microservices architecture, making it harder to pinpoint issues. Developers now have more ownership over the entire environment, but they lack the expertise to navigate intricate infrastructure details. And with the complexity of modern observability systems, crucial components often go unmonitored, leaving blind spots.
That's where Coroot comes in!
We're excited to announce the release of Coroot 1.0 – a simplified observability platform designed to provide actionable insights for modern environments. With Coroot you get:
- Comprehensive Visibility: Coroot covers your entire environment, ensuring no information gaps. Whether you're on Kubernetes, traditional VMs, or cloud services, Coroot has you covered.
- Simple Deployment: We've made deploying Coroot a breeze. Leveraging modern Linux features like eBPF and Netlink, setup requires zero configuration. Coroot also identifies and configures additional components for you.
- Actionable Insights: Coroot prioritizes the most important information, helping you resolve issues up to 80% faster than with legacy solutions.
And the best part? Coroot has open-source version. If you prefer a hosted solution, there is Coroot Cloud, which comes with a free trial and transparent affordable pricing.
While Coroot is already an awesome open-source observability platform, we're not stopping there. We have ambitious plans to automate issue resolution and minimize human intervention.
Got ideas? Let us know on GitHub - https://github.com/coroot/coroot
See detailed overview of Coroot Features - https://coroot.com/overview
- Coroot – Open-source Datadog/NewRelic alternative
-
Grafana Labs Observability Survey 2024
Take a look at https://github.com/coroot/coroot (Apache 2.0). It offers plenty of ready-to-use dashboards and inspections
-
All you need is Wide Events, not "Metrics, Logs and Traces"
I think ClickHouse is becoming a default storage for observability nowdays: https://clickhouse.com/use-cases/logging-and-metrics
And there are quite a few solutions on top of it.
A couple of examples that seem to be interesting (however I didn't use them in real life):
https://coroot.com/
-
Show HN: Coroot – A Copilot for Application Performance Troubleshooting
Landing page: https://coroot.com
- Show HN: Coroot – Copilot for Application Performance Troubleshooting
- Ask HN: Which project(s) made you go “I can't believe this is open-source”?
- Coroot v0.17 with Distributed Tracing capabilities + eBPF-based instrumentation for situations where integrating OpenTelemetry is not feasible
opentelemetry-collector-contrib
-
Ask HN: How to do dead simple heartbeat monitoring?
you can add https://github.com/open-telemetry/opentelemetry-collector-co... at signoz's otel-collector which will scrape your service's endpoint periodically. If your service is down, this will give 5xx error and you can set an alert on that.
Another alternative is to use an alert to notify on a metric being absent for sometime. Both of these should work
- OpenTelemetry at Scale: what buffer we can use at the behind to buffer the data?
-
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...
-
OpenTelemetry Collector Anti-Patterns
There are two official distributions of the OpenTelemetry Collector: Core, and Contrib.
-
OpenTelemetry Journey #00 - Introduction to OpenTelemetry
Maybe, you are asking yourself: "But I already had instrumented my applications with vendor-specific libraries and I'm using their agents and monitoring tools, why should I change to OpenTelemetry?". The answer is: maybe you're right and I don't want to encourage you to update the way how you are doing observability in your applications, that's a hard and complex task. But, if you are starting from scratch or you are not happy with your current observability infrastructure, OpenTelemetry is the best choice, independently of the backend telemetry tool that you are using. I would like to invite you to take a look at the number of exporters available in the collector contrib section, if your backend tracing tool is not there, probably it's already using the Open Telemetry Protocol (OTLP) and you will be able to use the core collector. Otherwise, you should consider changing your backend telemetry tool or contributing to the project creating a new exporter.
-
Building an Observability Stack with Docker
To receive OTLP data, you set up the standard otlp receiver to receive data in HTTP or gRPC format. To forward traces and metrics, a batch processor was defined to accumulate data and send it every 100 milliseconds. Then set up a connection to Tempo (in otlp/tempo exporter, with a standard top exporter) and to Prometheus (in prometheus exporter, with a control exporter). A debug exporter also was added to log info on container standard I/O and see how the collector is working.
-
Spotlight: Sentry for Development
Thanks for the reply. Would the Spotlight sidecar possibly be able to run independently and consume spans emitted by the Sentry exporter[0] or some other similar flow beyond strictly exporting directly from the Sentry SDK provided by Spotlight?
This tooling looks really cool and I'd love to play around with it, but am already pretty entrenched into OTel and funneling data through the collector and don't want to introduce too much additional overhead for devs.
[0] https://github.com/open-telemetry/opentelemetry-collector-co...
-
Amazon EKS Monitoring with OpenTelemetry [Step By Step Guide]
A list of all metric definitions can be found here.
-
Spring Boot Monitoring with Open-Source Tools
receivers: otlp: protocols: grpc: endpoint: 0.0.0.0:4317 http: endpoint: 0.0.0.0:4318 hostmetrics: collection_interval: 60s scrapers: cpu: {} disk: {} load: {} filesystem: {} memory: {} network: {} paging: {} process: mute_process_name_error: true mute_process_exe_error: true mute_process_io_error: true processes: {} prometheus: config: global: scrape_interval: 60s scrape_configs: - job_name: otel-collector-binary scrape_interval: 60s static_configs: - targets: ["localhost:8889>"] - job_name: "jvm-metrics" scrape_interval: 10s metrics_path: "/actuator/prometheus" static_configs: - targets: ["localhost:8090>"] processors: batch: send_batch_size: 1000 timeout: 10s # Ref: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/resourcedetectionprocessor/README.md resourcedetection: detectors: [env, system] # Before system detector, include ec2 for AWS, gcp for GCP and azure for Azure. # Using OTEL_RESOURCE_ATTRIBUTES envvar, env detector adds custom labels. timeout: 2s system: hostname_sources: [os] # alternatively, use [dns,os] for setting FQDN as host.name and os as fallback extensions: health_check: {} zpages: {} exporters: otlp: endpoint: "ingest.{region}.signoz.cloud:443" tls: insecure: false headers: "signoz-access-token": logging: verbosity: normal service: telemetry: metrics: address: 0.0.0.0:8888 extensions: [health_check, zpages] pipelines: metrics: receivers: [otlp] processors: [batch] exporters: [otlp] metrics/internal: receivers: [prometheus, hostmetrics] processors: [resourcedetection, batch] exporters: [otlp] traces: receivers: [otlp] processors: [batch] exporters: [otlp] logs: receivers: [otlp] processors: [batch] exporters: [otlp]
-
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...
What are some alternatives?
awesome-apm - A list of awesome APM products (commercial and OSS)
uptrace - Open source APM: OpenTelemetry traces, metrics, and logs
prometheus - The Prometheus monitoring system and time series database.
cockpit-podman - Cockpit UI for podman containers
hubble - Hubble - Network, Service & Security Observability for Kubernetes using eBPF
signoz - SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
skywalking - APM, Application Performance Monitoring System
podman-compose - a script to run docker-compose.yml using podman
VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database
traefik - The Cloud Native Application Proxy
self-hosted - Sentry, feature-complete and packaged up for low-volume deployments and proofs-of-concept
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...