docs: add systemd journal example to Promtail migration guide#6108
Open
ferr079 wants to merge 1 commit intografana:mainfrom
Open
docs: add systemd journal example to Promtail migration guide#6108ferr079 wants to merge 1 commit intografana:mainfrom
ferr079 wants to merge 1 commit intografana:mainfrom
Conversation
The migration guide only covers file-based scrape configs. Systemd journal scraping is a very common Promtail pattern on Linux hosts and the conversion to loki.source.journal + loki.relabel wasn't documented. Signed-off-by: Stephane <stephane@pixelium.win>
|
|
ferr079
added a commit
to ferr079/pixelium-site
that referenced
this pull request
Apr 23, 2026
… README refresh Ground truth via GitHub API: Stéphane shipped 4 contributions on 2026-04-22, all currently 'open' / awaiting review (none merged yet). Previous /contributions page only listed 1 and claimed 'merged' — both wrong. Changes: - /contributions (EN+FR): now lists the 4 real contributions · ublue-os/homebrew-experimental-tap#309 (PR, claude-code-linux cask) — first of the day · requarks/wiki#7986 (discussion, render IS NULL bug report) · grafana/alloy#6108 (PR, Promtail docs migration guide) · wazuh/wazuh-documentation#9512 (PR, warn about wazuh-agent postinst) - Status field: 'merged' → 'open' (honest; none merged upstream yet) - 'merged' date field → 'shipped' field semantically (day submitted) - /making-of/v3: 'first OSS PR accepted' → 'four OSS contributions shipped in one day' - Homepage OSS brick (EN+FR): contextualized PR #309 as 'first of four that day' - README.md: full refresh — 55 services (was 36), 4 PVE (was 3), 13 pages (was 8), SessionImprint, TopologyMap, DynNum, data pipelines documented Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Adds a new example section to the Migrate from Promtail guide showing how to convert a systemd journal scrape configuration, which is one of the most common Promtail patterns on Linux hosts but isn't currently covered in the migration examples.
Why
The current guide only demonstrates converting
static_configs+ file-based scraping. For anyone running Promtail on bare Linux (VMs, LXC containers, physical servers), the primary use case is scrapingsystemd-journald— and nothing in the guide shows that mapping. New users have to piece the conversion together fromloki.source.journal+loki.relabelreference pages without a concrete before/after example.This PR adds a third example block (after the existing file-match example, before
## Limitations) with:scrape_configs: journal:YAMLloki.source.journalandloki.relabeladm/systemd-journalgroup membership (already present onloki.source.journal.mdbut easy to miss during migration)Context
Real-world source: I migrated ~50 systemd-based hosts from Promtail to Alloy in a homelab and went through this exact translation. The Alloy
converttool handles it but the doc gap makes the output harder to reason about for people doing the conversion by hand to understand what they're shipping.Checklist
from-promtail.mdloki.source.journal.md