mirror of https://github.com/fleetdm/fleet synced 2026-04-21 13:37:30 +00:00

Victor Lyuboslavsky 544d2a4731

ADR: Attribute naming conventions for logs, traces, and metrics (#41818 )

We are planning to productize OTEL for our on-prem customers. This makes
our on-prem offering more attractive against our competition. As part of
our on-prem story, we need to make telemetry a first-class experience.

---------

Co-authored-by: Luke Heath <luke@fleetdm.com>

2026-03-27 13:48:15 -05:00

2.2 KiB

Raw Permalink Blame History

Architectural Decision Records (ADRs)

This directory contains Architectural Decision Records (ADRs) for Fleet.

What are ADRs?

Architectural Decision Records (ADRs) are documents that capture important architectural decisions made along with their context and consequences. They provide a record of architectural decisions that affect the system, the context in which they were made, and the rationale behind them.

Why use ADRs?

ADRs help teams:

Document important decisions for future reference
Communicate the reasoning behind decisions
Onboard new team members by providing context
Track the evolution of the system architecture over time

ADR format

Each ADR follows a standard format:

Title: A descriptive title that summarizes the decision
Status: Proposed, Accepted, Rejected, Deprecated, or Superseded
Context: The context and problem statement that led to this decision
Decision: The decision that was made
Consequences: The consequences of the decision, both positive and negative
References: Any references to related documents or resources

Creating a new ADR

To create a new ADR:

Copy the template to a new file named NNNN-descriptive-title.md where NNNN is the next number in sequence
Fill in the template with your decision
Submit a pull request with your new ADR

2.2 KiB Raw Permalink Blame History