kubespy
opentelemetry-collector-contrib
kubespy | opentelemetry-collector-contrib | |
---|---|---|
10 | 43 | |
2,830 | 2,567 | |
0.8% | 4.0% | |
5.4 | 10.0 | |
17 days ago | 4 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.
kubespy
-
How I get better feedback on my PRs (and how you can, too)
lang="en"> charset="utf-8"> Hello, world! Hello, world! 👋 Deployed with 💜 by new href="https://pulumi.com/">Pulumi.
-
AWS EC2 Auto Scaling, Target Tracking Policies and Prometheus Exporters
Pulumi IaC will help us bring up our infrastructure on the AWS Cloud. Check out pulumi.com if you still need to become familiar with it. You can deploy this demo stack using the Pulumi button below.
-
Terraform - How do you handle secrets?
There are other infrastructure as code tools that take secrets seriously. Pulumi encrypts all values in state and you can even bring your own key from your cloud provider
-
Observability Mythbusters: Yes, Observability-Landscape-as-Code is a Thing
*Codifying the deployment of the OTel Collector *(to Nomad, Kubernetes, or a VM) using tools such as Terraform, Pulumi, or Ansible. The Collector funnels your OTel data to your Observability back-end. ✅
-
Interesting tools?
KubeSpy - to see what's going on a deployment real time. https://github.com/pulumi/kubespy
-
My "infrastructure as code" tool to manage production-grade clusters
it takes too much time, terraform configs are not easy to use also. Pulumi is much better to maintenance. Cloudy is good enough for launching a production-ready cluster in 5-10 minutes. It could be an alternative to kops
-
We're building an open-source tool to deploy infrastructure in multiple clouds
Just wanted to mention a Terraform alternative I really like, especially cause it's infrastructure as code (IaC) http://pulumi.com/, though I'm not sure about their approach on multi cloud, haven't used it in quite a while
-
Deploying Kubernetes Clusters in Increasingly absurd languages
That is the entire point of Pulumi, you should give it a try
-
Tips: Conditional Expression on Terraform
pulumi.com if you are interested in doing anything dynamic inside of your templates (i.e. conditions) take a look at pulumi
- Ways to to trigger terraform modules
opentelemetry-collector-contrib
- 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...
-
Exploring the OpenTelemetry Collector
OpenTelemetry Operators
What are some alternatives?
pluto - A cli tool to help discover deprecated apiVersions in Kubernetes
uptrace - Open source APM: OpenTelemetry traces, metrics, and logs
kops - Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
cockpit-podman - Cockpit UI for podman containers
kured - Kubernetes Reboot Daemon
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
nginx-prometheus-exporter - NGINX Prometheus Exporter for NGINX and NGINX Plus
podman-compose - a script to run docker-compose.yml using podman
google-cloud-cpp - C++ Client Libraries for Google Cloud Services
traefik - The Cloud Native Application Proxy
multy - Multy - Easily deploy multi cloud infrastructure. Write cloud-agnostic config deployed across multiple clouds
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...