Built-in WildEdge.dev connector
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
- backend-api-design, observability
Research direction
Read the existing Sentry connector and its SENTRY_MCP_TOOLS allowlist to understand how built-in connections and read-only tools are registered. Then trace how production-error-review consumes connector data and run it against a test app with one new failing event; done means the report names that event and links its run trace, with the requested token scope and query limits enforced.
Written by the indexing model from the issue text.
Description
Idea
Add WildEdge.dev as a built-in connection, next to the existing Sentry connector, using WildEdge's MCP server.
Problem
monitoring-coverage-review and production-error-review need events, run traces, alerts and dashboards for the apps they review. Today only Sentry covers this, so teams that use WildEdge.dev for observability have to set up a custom connection.
Proposed initial scope
- A WildEdge.dev connection with a scoped, read-only token, limited to one company and the chosen apps.
- Read tools only, as an allowlist like
SENTRY_MCP_TOOLS: list apps, list and get events, get a run trace, list and get notifications, get dashboard data, and SQL queries over the event schema. - No write tools (resolving notifications, creating apps, dashboards or keys, managing members).
- Query size and time-range limits, so a model can't pull unbounded data through SQL or event listing.
Validation
Run production-error-review against a test app that has one new failing event and confirm the report names it and links its run trace.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 322
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from piotrekno1/second-shift
-
code-review secondshift
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
piotrekno1/second-shift#419 ·
Maintainers usually reply within 1 day
-
area: deployment
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
piotrekno1/second-shift#310 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 46/100
piotrekno1/second-shift#421 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 56/100
piotrekno1/second-shift#420 ·
Maintainers usually reply within 1 day
-
Fix failed-delivery retries on PostgreSQLPossibly taken @piotrekno1 claimed this today. Opencode-review fix-approved secondshift
Difficulty 3/5 1-2 days Newbie friendliness 35/100
piotrekno1/second-shift#418 ·
Maintainers usually reply within 1 day
All issues in piotrekno1/second-shift
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day