We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The amd64 version of grafana-agents support the Noble in the latest/candidate channel, however there is no support for Noble on arm64.
latest/candidate
$ juju info grafana-agent --base [email protected] --arch amd64 ... channels: | latest/stable: – latest/candidate: 260 2024-10-07 (260) 25MB amd64 latest/beta: ↑ latest/edge: 310 2024-11-14 (310) 26MB amd64
juju info grafana-agent --base [email protected] --arch arm64 name: grafana-agent publisher: Canonical Observability summary: Grafana Agent is a telemetry collector for sending metrics, logs,and trace data to the opinionated Grafana observability stack. description: | Grafana Agent Subordinate Charm store-url: https://charmhub.io/grafana-agent charm-id: Chha7geUVhDGaBLxlmc0b8wufSXoRvV4 supports: [email protected] subordinate: true relations: provides: grafana-dashboards-provider: grafana_dashboard requires: certificates: tls-certificates cos-agent: cos_agent grafana-cloud-config: grafana_cloud_config juju-info: juju-info logging-consumer: loki_push_api receive-ca-cert: certificate_transfer send-remote-write: prometheus_remote_write tracing: tracing
juju 3.5.4
---
No response
The text was updated successfully, but these errors were encountered:
We will address this in the near future with modernized CI. canonical/observability#248
Sorry, something went wrong.
Is there any update on this?
No branches or pull requests
Bug Description
The amd64 version of grafana-agents support the Noble in the
latest/candidate
channel, however there is no support for Noble on arm64.To Reproduce
Environment
juju 3.5.4
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: