Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add a monitoring capability to the Deployment Profile

Open
  • Is something wrong?
#332 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
cloud, observability

Research direction

Start with roadmap issue #183, sizing contract #323, and ADR 0013, then trace the profile capability configuration and the shared observability contract. Check how deployment components and routes are controlled for slim and full, and identify where per-size footprint measurements are published. Done means the acceptance criteria are met, including no monitoring components or route when disabled.

Written by the indexing model from the issue text.

Description

priority: P0 roadmap track: observability

Milestone: v0.7-alpha — Observability and Data Quality
Roadmap sequence: #183 (revised 2026-10-05)

Context

Monitoring moved into the beta path on 2026-10-05. The stack (#21 metrics, #22 logs, #23 alerting, #210 Grafana SSO) is shared across stages and must stay optional: a slim evaluation should not pay for it.

Scope

  • A platform-level monitoring switch in the profile: on by default in full, off in slim.
  • Retention and volume sizes from the sizing contract (#323), so a large deployment keeps more history without new fields.
  • observability.* contract entries in shared, absent when disabled.
  • Measure and publish the monitoring footprint per size.

Acceptance criteria

  • slim deploys no monitoring component; full deploys #21 and #22.
  • Footprint per size is published.
  • A disabled capability exposes no route (ADR 0013).
Dominant language
Python
Stars
26
Forks
6
Avg merge
12h 26m
Merged PRs (30d)
162

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenLakeForge/openlakeforge

All issues in OpenLakeForge/openlakeforge

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.