hashicorp / hashicorp/nomad

Feature Idea: Better Support for 3rd party logging solutions.

Open
#9,211 13 comments 8 reactions 0 assignees View on GitHub
stage/needs-discussion theme/logging type/enhancement
Dominant language
Go
Stars
17k
Forks
2.1k
Avg merge
1d 9h
Merged PRs (30d)
105

Description

Logs are something that should just be automagic in a clustered environment. Teams shouldn't need to think about them and they should be managed by the infrastructure. Supporting these systems also shouldn't break nomad's built-in log management, so changing things like the global docker logging configuration isn't really a solution.

I propose a patch to logmon to allow it to dupe the log streams to a second well-known location. This location should name the files something like {{.NodeName}}-{{.Job}}-{{.Group}}-{{.Task}}-{{.AllocID}}. Bonus points for making this a templatable string!

I don't think this is a particularly complex feature to support, but it would open up running log management solutions like loki as one-click options within nomad. More importantly, it would generally allow other log indexing to work without breaking build in logs commands.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating Nomad's logmon implementation and reading how its existing log management handles task log streams. Define the second destination and filename template behavior without changing built-in log commands; done means streams can be duplicated to the additional location with the proposed allocation details in filenames.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
infrastructure, observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.