Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurable extraTags when shipping kernel logs externally #9769

Open
jtcressy opened this issue Nov 20, 2024 · 0 comments
Open

Configurable extraTags when shipping kernel logs externally #9769

jtcressy opened this issue Nov 20, 2024 · 0 comments

Comments

@jtcressy
Copy link

Feature Request

Addition of a new kernel arg talos.logging.kernel.extra-tag to apply extra tags to the logging destination configuration, similar to service logs.

We could format this new kernel arg similar to talos.environment so that multiple tags can be defined.

Also, if possible, include the support of templating into the value portion similar to talos.config with the options ${uuid} ${serial} ${mac} ${hostname} - this would enable us to include these identifiers as tags without hard-coding them.

Description

Metadata is distinctly lacking when shipping kernel logs to centralized logging systems. Ideally, I would want logs to include the source node's hostname at a minimum. As it stands, when one machine is having issues, it is almost impossible to identify it without opening the console of every machine and inspecting the logs manually.

If we had a way to include metadata via kernel arguments just like we can with service logs, this would solve the problem.

Example

Kernel cmdline for external logging with multiple templated tags
talos.logging.kernel=udp://ingest.local:1234 talos.logging.extra-tag=hostname=${hostname} talos.logging.extra-tag=machine_serial=${serial} talos.logging.extra-tag=machine_uuid=${uuid} talos.logging.extra-tag=machine_mac_addr=${mac}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant