II.
Page overview
Reference · livepage:docs-harness-features-backlog-gaps-observability-gap-obs-006
GAP-OBS-006: Analytics and Feature Flags overview
Inspect the raw attributes, linked wiki pages, and inbound or outbound graph edges for page:docs-harness-features-backlog-gaps-observability-gap-obs-006.
Attributes
nodeKind
Page
sourcePath
docs/harness-features-backlog/gaps/observability/GAP-OBS-006.md
sourceKind
repo-docs
title
GAP-OBS-006: Analytics and Feature Flags
displayName
GAP-OBS-006: Analytics and Feature Flags
slug
docs/harness-features-backlog/gaps/observability/gap-obs-006
articlePath
wiki/docs/harness-features-backlog/gaps/observability/GAP-OBS-006.md
article
# GAP-OBS-006: Analytics and Feature Flags
| Field | Value |
|-------|-------|
| Category | observability |
| Priority | Medium |
| Effort | L |
| Status | Partial |
## Description
Implement a structured event pipeline with configurable analytics sinks and a unified feature flag management system for the orchestration platform.
## Current State
Structured JSONL logging exists. No analytics platform integration, no feature flag evaluation system. Features scattered across env vars and config.
## Target State
Structured event pipeline with configurable sinks (file, HTTP, custom). Unified feature flag system with evaluation context (user, project, run). Feature flag status queryable at runtime.
## Dependencies
- [GAP-ECO-004](../ecosystem/GAP-ECO-004.md) -- feature registry
## Key Files
| Component | Path |
|-----------|------|
| Logging module | `packages/babysitter-sdk/src/logging/` |
| Config module | `packages/babysitter-sdk/src/config/` |
## Recommendation
Phase 4 implementation. Build analytics pipeline on top of existing JSONL logging. Integrate feature registry for flag management.
documents
[]
Outgoing edges
None.
Incoming edges
contains_page1
- page:docs-harness-features-backlog·PageHarness Features Backlog: Gap Analysis (Restructured)