mirror of
https://github.com/grafana/mimir.git
synced 2026-04-16 11:31:05 +00:00
Grafana Mimir provides horizontally scalable, highly available, multi-tenant, long-term storage for Prometheus.
f6619bc2c9This PR contains the following updates:
| Package | Change |
[Age](https://docs.renovatebot.com/merge-confidence/) |
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
|
[go.opentelemetry.io/collector/pdata](https://redirect.github.com/open-telemetry/opentelemetry-collector)
| `v1.54.0` → `v1.56.0` |
|
|
---
> [!WARNING]
> Some dependencies could not be looked up. Check the warning logs for
more information.
---
### Release Notes
<details>
<summary>open-telemetry/opentelemetry-collector
(go.opentelemetry.io/collector/pdata)</summary>
###
[`v1.56.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1560v01500)
##### 💡 Enhancements 💡
- `all`: Update semconv package from 1.38.0 to 1.40.0
([#​15095](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/15095))
- `cmd/mdatagen`: Only allow the `ToVersion` feature flag attribute to
be set for the `Stable` and `Deprecated` stages.
([#​15040](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/15040))
To better match the feature flag README
(<https://github.com/open-telemetry/opentelemetry-collector/blob/main/featuregate/README.md#feature-lifecycle>).
##### 🧰 Bug fixes 🧰
- `exporter/debug`: Guard from out of bounds profiles dictionary indices
([#​14803](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/14803))
- `pdata/pprofile`: create a copy when the input is marked as read-only
([#​15080](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/15080))
- `pkg/otelcol`: Fix missing default values in unredacted print-config
command by introducing confmap.WithUnredacted MarshalOption.
([#​14750](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/14750))
Resolves an issue where the unredacted mode output omitted all
default-valued options. By introducing a new MarshalOption to disable
redaction directly at the confmap encoding level, the unredacted mode
now preserves all component defaults natively without requiring
post-processing.
- `pkg/service`: Headers on the internal telemetry OTLP exporter are now
redacted when the configuration is marshaled
([#​14756](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/14756))
<!-- previous-version -->
###
[`v1.55.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1550v01490)
##### 🛑 Breaking changes 🛑
- `pkg/service`: Remove `service_name`, `service_instance_id`, and
`service_version` as constant labels on every internal metric datapoint.
These attributes are already present in `target_info` and were being
duplicated on each series for OpenCensus backwards compatibility.
([#​14811](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/14811))
Previously, the collector stamped every internal metric series (e.g.
`otelcol_process_runtime_heap_alloc_bytes`)
with `service_name`, `service_instance_id`, and `service_version` labels
to match the old OpenCensus behavior.
These attributes are now only present in the `target_info` metric, which
is the correct Prometheus/OTel convention.
Users who filter or group by these labels on individual metrics will
need to update their queries to use
`target_info` joins instead.
##### 💡 Enhancements 💡
- `all`: Move aix/ppc64 to tier 3 support
([#​13380](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13380))
- `all`: Upgrade the profiles stability status to alpha
([#​14817](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/14817))
The following components have their profiles status upgraded from
development to alpha:
- pdata/pprofile
- connector/forward
- exporter/debug
- receiver/nop
- exporter/nop
- exporter/otlp\_grpc
- exporter/otlp\_http
- `cmd/mdatagen`: Add semconv reference for attributes
([#​13297](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13297))
##### 🧰 Bug fixes 🧰
- `cmd/mdatagen`: Fix entity code generation so `extra_attributes` are
emitted as resource attributes instead of entity descriptive attributes.
([#​14778](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/14778))
<!-- previous-version -->
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- Branch creation
- Between 12:00 AM and 03:59 AM (`* 0-3 * * *`)
- Automerge
- At any time (no schedule defined)
🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
## Need help?
You can ask for more help in the following Slack channel:
#proj-renovate-self-hosted. In that channel you can also find ADR and
FAQ docs in the Resources section.
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My42NS4wIiwidXBkYXRlZEluVmVyIjoiNDMuMTEwLjE2IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmN5LXVwZGF0ZSIsInVwZGF0ZS1taW5vciJdfQ==-->
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> **Medium Risk**
> Dependency upgrades with refreshed vendored code; moderate risk due to
upstream API/behavior changes in `pdata` and the `go-version`
`NewVersion` signature, which could break consumers if used.
>
> **Overview**
> Bumps OpenTelemetry Collector dependencies, updating
`go.opentelemetry.io/collector/pdata` (and the related `featuregate`) to
`v1.56.0` and refreshing `go.sum`/`vendor` accordingly.
>
> Also updates `github.com/hashicorp/go-version` to `v1.9.0`, which
introduces a new optional `WithPrefix` parsing option and changes
`version.NewVersion` to accept variadic options in the vendored module.
>
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
|
||
|---|---|---|
| .claude/skills/split-file | ||
| .config/go | ||
| .github | ||
| cmd | ||
| development | ||
| docs | ||
| images | ||
| integration | ||
| mimir-build-image | ||
| operations | ||
| packaging | ||
| pkg | ||
| tools | ||
| vendor | ||
| .gitattributes | ||
| .gitconfig | ||
| .gitignore | ||
| .golangci.yml | ||
| .lintignore | ||
| .prettierignore | ||
| ADOPTERS.md | ||
| AGENTS.md | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| CODE_OF_CONDUCT.md | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| go.mod | ||
| go.sum | ||
| GOVERNANCE.md | ||
| LICENSE | ||
| LICENSING.md | ||
| MAINTAINERS.md | ||
| Makefile | ||
| Makefile.local.example | ||
| README.md | ||
| RELEASE.md | ||
| renovate.json5 | ||
| VERSION | ||
Grafana Mimir
Grafana Mimir is an open source software project that provides a scalable long-term storage for Prometheus. Some of the core strengths of Grafana Mimir include:
- Easy to install and maintain: Grafana Mimir’s extensive documentation, tutorials, and deployment tooling make it quick to get started. Using its monolithic mode, you can get Grafana Mimir up and running with just one binary and no additional dependencies. Once deployed, the best-practice dashboards, alerts, and runbooks packaged with Grafana Mimir make it easy to monitor the health of the system.
- Massive scalability: You can run Grafana Mimir's horizontally-scalable architecture across multiple machines, resulting in the ability to process orders of magnitude more time series than a single Prometheus instance. Internal testing shows that Grafana Mimir handles up to 1 billion active time series.
- Global view of metrics: Grafana Mimir enables you to run queries that aggregate series from multiple Prometheus instances, giving you a global view of your systems. Its query engine extensively parallelizes query execution, so that even the highest-cardinality queries complete with blazing speed.
- Cheap, durable metric storage: Grafana Mimir uses object storage for long-term data storage, allowing it to take advantage of this ubiquitous, cost-effective, high-durability technology. It is compatible with multiple object store implementations, including AWS S3, Google Cloud Storage, Azure Blob Storage, OpenStack Swift, as well as any S3-compatible object storage.
- High availability: Grafana Mimir replicates incoming metrics, ensuring that no data is lost in the event of machine failure. Its horizontally scalable architecture also means that it can be restarted, upgraded, or downgraded with zero downtime, which means no interruptions to metrics ingestion or querying.
- Natively multi-tenant: Grafana Mimir’s multi-tenant architecture enables you to isolate data and queries from independent teams or business units, making it possible for these groups to share the same cluster. Advanced limits and quality-of-service controls ensure that capacity is shared fairly among tenants.
Migrating to Grafana Mimir
If you're migrating to Grafana Mimir, refer to the following documents:
Deploying Grafana Mimir
For information about how to deploy Grafana Mimir, refer to Deploy Grafana Mimir.
Getting started
If you’re new to Grafana Mimir, read the Get started guide.
Before deploying Grafana Mimir in a production environment, read:
Documentation
Refer to the following links to access Grafana Mimir documentation:
- Latest release
- Upcoming release, at the tip of the
mainbranch
Contributing
To contribute to Grafana Mimir, refer to Contributing to Grafana Mimir.
Join the Grafana Mimir discussion
If you have any questions or feedback regarding Grafana Mimir, join the Grafana Mimir Discussion. Alternatively, consider joining the monthly Grafana Mimir Community Call.
Your feedback is always welcome, and you can also share it via the #mimir Slack channel.
License
Grafana Mimir is distributed under AGPL-3.0-only.