Signed-off-by: Ganesh Vernekar <[email protected]>

Signed-off-by: Ganesh Vernekar <[email protected]>

Signed-off-by: Ganesh Vernekar <[email protected]>

Signed-off-by: Ganesh Vernekar <[email protected]>

Signed-off-by: Ganesh Vernekar <[email protected]>

Upgrade Go to 1.26.0 for building Prometheus

Signed-off-by: Ganesh Vernekar <[email protected]>

Signed-off-by: Ganesh Vernekar <[email protected]>

tsdb: Fix locking in Head.deleteSeriesByID

Signed-off-by: Divyansh Mishra <[email protected]>

Signed-off-by: Ganesh Vernekar <[email protected]>

Signed-off-by: Ganesh Vernekar <[email protected]>

Cut v3.10.0-rc.0

Upstream distroless does not support riskv64 yet

Signed-off-by: Julien Pivotto <[email protected]>

chore: Exclude riskv64 from distroless images

Signed-off-by: Ganesh Vernekar <[email protected]>

Cut v3.10.0-rc.1

Fixes #18123

Introduces DOCKER_REGISTRY_ARCH_EXCLUSIONS to exclude specific
architectures from specific registries. This allows riscv64 to be
excluded from quay.io (which returns unauthorized) while still
supporting it on docker.io.

The new registry_arch_is_excluded function extracts the registry
from DOCKER_REPO and checks if registry:arch is in the exclusion
list. This is applied during push, tag, and manifest creation steps.

This fix ensures s390x and other architectures are included in
quay.io manifests even when riscv64 fails to push.

Signed-off-by: Julien Pivotto <[email protected]>

…cific-arch-exclusion

chore(ci): Add registry-specific architecture exclusions

The query log embeds a spanID, but omits the traceID, making
log/trace correlation significantly more difficult.

Add the trace ID as well.

This might be better done with the otelslog wrapper in
https://github.com/go-slog/otelslog but this change is more
minimal.

This does not add trace and span IDs to other logging
emitted to Prometheus's standard logger during the processing
of activities in which traces may be active.

Fixes #18188

Signed-off-by: Craig Ringer <[email protected]>

The metric tracks the last update sent to SD consumers, and includes the
manager name. This allows for monitoring SD state based on far ago its
last heartbeat was.

Signed-off-by: Pranshu Srivastava <[email protected]>

Signed-off-by: Ganesh Vernekar <[email protected]>

Signed-off-by: Craig Ringer <[email protected]>

Signed-off-by: Ganesh Vernekar <[email protected]>

Following the discussion in #17349, adding myself as maintainer for
Consul service discovery.

Signed-off-by: Mohammad Varmazyar <[email protected]>

Merge release-3.10 branch to main

Add traceID to query logs

Signed-off-by: bwplotka <[email protected]>

…13.0 (#18141)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Move bwplotka to general maintainer

discovery/kubernetes: Support node role selectors for pod roles

chore(main): Fix typo SuqueryInterval to SubqueryInterval

… on arguments (#17313)

Some timestamp functions can be safely wrapped as a step invariant.
Then once we do that we never need to check or unwrap at evaluation time.

For instance; `timestamp(metric @ 1)` is step invariant, whereas
`timestamp(abs(metric @ 1))` is not.

Currently all `timestamp` `*parser.Call` are excluded from being
considered step invariant since it is listed in the
`AtModifierUnsafeFunctions` map.

This PR adds an extra check for timestamp functions which consider
the arguments, and if the argument is a simple VectorSelector then
the entire `*parser.Call` can be safely wrapped as a step invariant.

Signed-off-by: Andrew Hall <[email protected]>
Co-authored-by: Bryan Boreham <[email protected]>

discovery: Introduce `prometheus_sd_last_update_timestamp_seconds`

Signed-off-by: Owen Williams <[email protected]>