# Do not expect metric relabeling to remove Prometheus up

> Prometheus excludes automatically generated series such as up from metric relabeling.

- Canonical URL: https://update.dsesecurity.com/updates/choose-the-prometheus-relabeling-stage-from-the-intended-effect/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-10-20T18:15:35+00:00
- Modified: 2026-10-20T18:34:33+00:00
- Last reviewed by DSE: 2026-10-20
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Prometheus excludes automatically generated series such as up from metric relabeling.

## Potentially affected

Review native Prometheus metric filtering separately from target selection, including the automatically generated up exception.

## DSE recommendation

DSE recommends treating scrape-health series and filtered application samples as separate expected outputs of a collection change.

## Article

Prometheus excludes automatically generated series such as up from metric relabeling.

## Source facts

Prometheus target relabeling rewrites the target label set before scraping and applies steps in configuration order. Metric relabeling operates on samples immediately before ingestion. Metric relabeling does not apply to automatically generated series such as up. The same-looking rule syntax therefore has a different boundary depending on where it is configured.

Source: [Prometheus documentation — Configuration](https://prometheus.io/docs/prometheus/latest/configuration/configuration/).

## Applicability

Review native Prometheus metric filtering separately from target selection, including the automatically generated up exception.

## DSE recommendation

DSE recommends treating scrape-health series and filtered application samples as separate expected outputs of a collection change. Write an explicit decision for up: retain it as the scrape signal, or change target selection when the intended outcome is to stop scraping that target. Do not present an ingestion filter as proof that the network request stopped. Review rule order when one target transformation supplies another’s input. Keep a small expected-series list with the job so a responder can distinguish an intentional application-metric exclusion from an unavailable exporter.

## Verification

In a nonproduction scrape job, compare discovered targets, scrape activity, up, and a disposable application metric before and after the rule. Confirm the chosen stage produces the intended effect without losing unrelated samples. Review the resulting labels for unique series identity. Retain the target state, observed scrape and queries for up and the application metric together. Ask the monitoring owner to approve the result specifically against the expected-series list rather than a single empty dashboard panel.

## Official reference

[Prometheus documentation — Configuration](https://prometheus.io/docs/prometheus/latest/configuration/configuration/). Reviewed October 20, 2026.

## Primary reference

- Name: Prometheus documentation — Configuration
- Authority: prometheus.io
- URL: https://prometheus.io/docs/prometheus/latest/configuration/configuration/
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Do not expect metric relabeling to remove Prometheus up,” DSE Security, https://update.dsesecurity.com/updates/choose-the-prometheus-relabeling-stage-from-the-intended-effect/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.