ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend

Monitoring: Establish manual assessment process

Open
#1,112 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
18
Forks
10
Avg merge
2d 20h
Merged PRs (30d)
14

Description

Is your feature request related to a problem?
The team lacks a monitoring cadence for all instances (backend, guardrails, frontend) before automation can begin, which may lead to unresolved issues.

Describe the solution you'd like

  • Phase 1: Implement a manual monitoring pass every Wednesday morning to assess memory spikes and usage trend changes, creating a checklist during the process.
  • Phase 2: Plan for automation at a later stage.
  • Start a Kaapi-channel thread and draft the monitoring document.
Original issue

Context

The team needs a monitoring cadence across all instances (backend, guardrails, frontend) before automating.

Decision

  • Phase 1: manual pass every Wednesday morning over all instances (memory spikes, usage trend changes), building a checklist as they go.
  • Phase 2: automation, later.

Next steps

  • Start a Kaapi-channel thread and drafts the doc monitoring doc.

Contributor guide

Open the 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.

Research direction

No files or tests are named. Start by reviewing the Phase 1 scope and starting the Kaapi-channel thread; assess backend, guardrails, and frontend instances for memory spikes and usage-trend changes, and draft the monitoring document and checklist. Done means the Wednesday manual cadence is established and the documentation is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.