Apache License 2.0

项目介绍

grafana/alloy 是一个托管在 GitHub 上的开源项目,主要使用 Go 编写,采用 Apache License 2.0 许可证,目前获得 3.7k 个 Star、770 次 Fork。

仓库全名
grafana/alloy
开源许可证
Apache License 2.0
Star 数
3.7k
Fork 数
770
未关闭 Issue
1.3k

README 摘要

Grafana Alloy is an open source OpenTelemetry Collector distribution with built-in Prometheus pipelines and support for metrics, logs, traces, and profiles. What can Alloy do? Programmable pipelines: Use a rich [expression-based syntax][syntax] for configuring powerful observability pipelines. OpenTelemetry Collector Distribution: Alloy is a [distribution][] of OpenTelemetry Collector and supports dozens of its…

完整内容见 GitHub 原始 README 或本页 。

常见问题

alloy 用什么语言开发?

主要使用 Go 编写,采用 Apache License 2.0 许可证,目前有 3.7k 个 Star。

alloy 可以免费商用吗?

仓库采用 Apache License 2.0 许可证,可免费使用与修改,商业使用请遵守许可证条款(例如保留版权声明与许可声明)。

如何获取 alloy 的源码?

可以直接克隆仓库:git clone https://github.com/grafana/alloy.git,默认分支为 main;安装与运行步骤见仓库 README。

alloy 最近还在维护吗?

仓库最近一次更新为 22 小时前,当前有 1.3k 个未关闭 Issue;Star 数为 3.7k,可作为社区活跃度的参考。

关于

GitHub 原始描述(英文)

OpenTelemetry Collector distribution with programmable pipelines

描述取自 GitHub 官方 API,保持仓库作者书写的原文。

简要分析

热度分
5332
价值分
2384
活跃状态
活跃

语言占比

Batchfile
CSS
Dockerfile
Go
Go Template
HTML
JavaScript
Jsonnet
Makefile
Shell
Smarty
TypeScript
Yacc

Release

README

Grafana Alloy logo Grafana Alloy logo

Latest Release Documentation link

Grafana Alloy is an open source OpenTelemetry Collector distribution with built-in Prometheus pipelines and support for metrics, logs, traces, and profiles.

What can Alloy do?

  • Programmable pipelines: Use a rich expression-based syntax for configuring powerful observability pipelines.

  • OpenTelemetry Collector Distribution: Alloy is a distribution of OpenTelemetry Collector and supports dozens of its components, alongside new components that make use of Alloy’s programmable pipelines.

  • Big tent: Alloy embraces Grafana’s “big tent” philosophy, where Alloy can be used with other vendors or open source databases. It has components to perfectly integrate with multiple telemetry ecosystems:

  • Kubernetes-native: Use components to interact with native and custom Kubernetes resources; no need to learn how to use a separate Kubernetes operator.

  • Shareable pipelines: Use modules to share your pipelines with the world.

  • Automatic workload distribution: Configure Alloy instances to form a cluster for automatic workload distribution.

  • Centralized configuration support: Alloy supports retrieving its configuration from a server for centralized configuration management.

  • Debugging utilities: Use the built-in UI for visualizing and debugging pipelines.

Example

otelcol.receiver.otlp "example" {
  grpc {
    endpoint = "127.0.0.1:4317"
  }

  output {
    metrics = [otelcol.processor.batch.example.input]
    logs    = [otelcol.processor.batch.example.input]
    traces  = [otelcol.processor.batch.example.input]
  }
}

otelcol.processor.batch "example" {
  output {
    metrics = [otelcol.exporter.otlp.default.input]
    logs    = [otelcol.exporter.otlp.default.input]
    traces  = [otelcol.exporter.otlp.default.input]
  }
}

otelcol.exporter.otlp "default" {
  client {
    endpoint = "my-otlp-grpc-server:4317"
  }
}

Getting started

Check out our documentation to see:

Release cadence

A new minor release is planned every three weeks. Patch releases are published every one to two weeks.

The release cadence is best-effort: if necessary, releases may be performed outside of this cadence, or a scheduled release date can be moved forwards or backwards.

Minor releases published on cadence include updating dependencies for upstream OpenTelemetry Collector code if new versions are available. Minor releases published outside of the release cadence may not include these dependency updates.

Patch and security releases may be published at any time.

Community

To engage with the Alloy community:

Contributing

Refer to our contributors guide to learn how to contribute.

Thanks to all the people who have already contributed!

评论

暂无评论