Skip to content

feat: add structured logging, metrics collection, failure diagnostics… - #26

Open
mianaliabbas23-dotcom wants to merge 4 commits into
QuantumLogicsLabs:mainfrom
mianaliabbas23-dotcom:feat/structured-logging-and-monitoring
Open

feat: add structured logging, metrics collection, failure diagnostics…#26
mianaliabbas23-dotcom wants to merge 4 commits into
QuantumLogicsLabs:mainfrom
mianaliabbas23-dotcom:feat/structured-logging-and-monitoring

Conversation

@mianaliabbas23-dotcom

Copy link
Copy Markdown
Contributor

…, and monitoring documentation

Summary

Closes #


Type of Change

  • Bug fix
  • Agent improvement (planner, executor, memory)
  • New or updated tool (tools/)
  • Prompt update (prompts/)
  • API change (api/)
  • Configuration / settings
  • Refactor / code quality
  • Documentation
  • CI/CD
  • Other:

Changes

  • agent/
  • tools/
  • prompts/
  • api/
  • tests/
  • config/

Testing

pytest tests/ -v
  • All existing tests pass
  • New tests added for new behaviour
  • Linting passes: ruff check . && black --check .
  • Type checks pass: mypy .

For Agent / Planner Changes

  • Tested with at least one real POST /run job end-to-end
  • Plan output is sensible for the test instruction
  • MAX_PLAN_STEPS limit is respected

For Tool Changes

  • tests/test_tools.py updated
  • Tool tested against a real or mock GitHub repo (specify which)
  • GitHub API calls are mocked in unit tests (no real commits in CI)

For Prompt Changes

  • Before/after prompt outputs documented below
  • Tested against at least 2–3 representative instructions
Prompt output comparison (click to expand)

Before:

# paste old output

After:

# paste new output

For API Changes

  • tests/test_api.py updated
  • Swagger docs (/docs) still render correctly
  • Request/response schemas updated in api/schemas.py

Security Checklist

  • No API keys, tokens, or secrets introduced into tracked files
  • .env values only reference variables defined in config/.env.example
  • LLM-generated content is never passed to eval() or exec()
  • New API endpoints require appropriate auth (or explicitly document why not)
  • Docker image does not run as root (if Dockerfile modified)
  • No new dependency added without a pinned version in pyproject.toml

Breaking Changes

  • This PR introduces breaking changes to the API or agent behaviour

If yes, describe what breaks and the migration path:


Screenshots / Output (if applicable)

# Paste job output, diff summary, or PR URL from a test run

Reviewer Notes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant