opentelemetry-collector
over-golang
Our great sponsors
opentelemetry-collector | over-golang | |
---|---|---|
16 | 1 | |
3,810 | 4,260 | |
4.3% | 0.1% | |
9.9 | 0.0 | |
about 9 hours ago | about 1 year ago | |
Go | Go | |
Apache License 2.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.
opentelemetry-collector
-
OpenTelemetry Collector Anti-Patterns
But how does one monitor a Collector? The OTel Collector already emits metrics for the purposes of its own monitoring. These can then be sent to your Observability backend for monitoring.
-
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.
-
Amazon EKS Monitoring with OpenTelemetry [Step By Step Guide]
You can find more details on advanced configurations here.
-
Go 1.21
> opentelemetry is basically a house of antipatterns
"Look on My Works Ye Mighty and Despair!"
https://github.com/open-telemetry/opentelemetry-collector/tr... -> https://github.com/open-telemetry/opentelemetry-collector-re... ... and then a reasonable person trying to load that mess into their head may ask 'err, what's the difference between go.opentelemetry.io/collector and github.com/open-telemetry/opentelemetry-collector-contrib?'
$ curl -fsS go.opentelemetry.io/collector | grep go-import
-
Display CockroachDB metrics in Splunk Dashboards
There are 2 collector types: the core and the contrib. I have used the contrib as it features the splunk_hec exporter.
-
Observability Mythbusters: How hard is it to get started with OpenTelemetry?
Lightstep ingests data in native OpenTelemetry Protocol (OTLP) format, so we will use the OTLP Exporter. The exporter can be called either otlp or follow the naming format otlp/. We could call it otlp/bob if we wanted to. We're calling our exporter otlp/ls to signal to us that we are using the OTLP exporter to send the data to Lightstep.
-
OpenTelemetry Collector: A Friendly Guide for Devs
Then, we set up a batch processor that batches up the spans together and every 1 second sends the batch forward. In production, you would want more than 1 second, but I set this here to 1 second for instant feedback in Jaeger.
-
OpenTelemetry in Dotnet
Batch allows for metrics, traces etc to be batched into bundles. The default is 8192 and then it will send, the timeout is the max time before sending regardless. I'd highly recommend utilising batches if you're dealing with high volumes of traffic.
-
Prometheus Agent Mode, for Metric Forwarding
There were a bunch of alternatives to solve this before, like grafana agent [0], vm agent [1] or opentelemetry collector [2].
[0] - https://github.com/grafana/agent
[1] - https://github.com/VictoriaMetrics/VictoriaMetrics/tree/mast...
[2] - https://github.com/open-telemetry/opentelemetry-collector
over-golang
-
Gopher Gold #10 - Wed Sep 09 2020
overnote/over-golang (Go): Golang相关:[进度80%]Go语法、Go并发思想、Go与web开发、Go微服务设施等
What are some alternatives?
go-sql-driver/mysql - Go MySQL Driver is a MySQL driver for Go's (golang) database/sql package
GORM - The fantastic ORM library for Golang, aims to be developer friendly
jaeger - CNCF Jaeger, a Distributed Tracing Platform
go-ethereum - Official Go implementation of the Ethereum protocol
argo-cd - Declarative Continuous Deployment for Kubernetes
prometheus - The Prometheus monitoring system and time series database.
terraform-provider-aws - Terraform AWS provider [Moved to: https://github.com/hashicorp/terraform-provider-aws]
VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database
learn-go-with-tests - Learn Go with test-driven development
bettercap - The Swiss Army knife for 802.11, BLE, IPv4 and IPv6 networks reconnaissance and MITM attacks.
go - The Go programming language
Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD