[MeshCore P3] M6 - History / centrality API (node + routers)

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
neo4j, postgresql, python
Domain
analytics, api

Research direction

Start by reading the M4 graph work and the M2 decision on whether centrality is computed in Postgres or Neo4j, since this issue depends on both. The two endpoints are GET /api/meshcore/path-tracing/nodes/<id>/ and GET /api/meshcore/path-tracing/routers/, and both need time-window and constellation filters plus OpenAPI documentation. Done means both endpoints return passive path-weight data, unresolved hashes are labelled, and no wording implies traceroute success.

Written by the indexing model from the issue text.

Description

enhancement

Parent

Part of #267. Milestone M6.

Goal

Longer-term history and important-router analytics over bucketed passive edges.

Scope

  • GET /api/meshcore/path-tracing/nodes/<id>/ — node-centric path evidence.
  • GET /api/meshcore/path-tracing/routers/ — centrality summary, computed per the M2 Postgres-vs-Neo4j decision.
  • Document passive semantics (observed path weight, not traceroute success); unresolved hashes labelled as such.

Acceptance criteria

  • Endpoints documented in OpenAPI; time-window + constellation filters supported.
  • Wording never implies TR success/coverage.

Depends on

  • M4 (graph) and/or M2 decision on compute location.
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.