[Epic] MeshCore Phase 5 — DX monitoring (planning)

Open
#269 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
observability

Research direction

This is a planning epic with no files, tests or entry points named, so there is no code to start from. The first step is the spike ADR on whether DX-style detection applies to MeshCore flood routing, which would need maintainer input on scope. Child tickets are not yet written, so this is not a good first issue.

Written by the indexing model from the issue text.

Description

enhancement

Summary (future work)

Spike whether DX-style detection applies to MC flood routing; optional DxEvent.protocol + MC observation dual-FK; reuse detection rule families with MC-tuned thresholds.

Proposed breakdown

  1. Spike ADR: DX semantics on MC.
  2. Schema + detection hooks.
  3. Exploration queue (depends on Phase 3).

Milestone: MeshCore Support (planning epic; child tickets later)

Dominant language
Python
Stars
1
Forks
0
Avg merge
1d 20h
Merged PRs (30d)
5

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 pskillen/meshflow-api

All issues in pskillen/meshflow-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.