SecureWatch Bug Tracker

Overview

This document tracks all known bugs, issues, and their resolution status for the SecureWatch SIEM platform.

Bug Status Legend

  • 🔴 Critical: System crashes, data loss, security vulnerabilities

  • 🟡 High: Major functionality broken, significant performance issues

  • 🟢 Medium: Minor functionality issues, UI problems

  • 🔵 Low: Cosmetic issues, enhancement requests

Current Bug Summary

  • Total Bugs: 5

  • Open: 3

  • In Progress: 1

  • Fixed: 1

  • Critical: 1

  • High: 2

  • Medium: 2

Bug List

BUG-001: TypeError Failed to fetch in log-search component 🔴 FIXED

  • Status: Fixed ✅

  • Priority: Critical

  • Component: frontend/components/log-search.tsx

  • Description: Unhandled TypeError when search API is unavailable

  • Steps to Reproduce:

    1. Start frontend without search API running

    2. Navigate to log search page

    3. Click search button

  • Expected Result: Graceful error handling with user message

  • Actual Result: Unhandled TypeError: Failed to fetch

  • Environment: Next.js 15, macOS, Chrome

  • Assigned To: Claude Code

  • Date Reported: 2025-06-03

  • Date Resolved: 2025-06-03

  • Fix Details:

    • Added environment variable for API URL

    • Implemented graceful error handling

    • Added user-friendly alert messages

BUG-002: KQL Engine build failures due to TypeScript errors 🟡 IN PROGRESS

  • Status: In Progress 🔄

  • Priority: High

  • Component: packages/kql-engine

  • Description: TypeScript compilation errors preventing package build

  • Steps to Reproduce:

    1. Run pnpm run build in packages/kql-engine

    2. Observe DTS generation failures

  • Expected Result: Clean build with type definitions

  • Actual Result: Build fails with TypeScript errors

  • Environment: Node.js 24.1.0, TypeScript 5.x, tsup 8.5.0

  • Assigned To: Development Team

  • Date Reported: 2025-06-03

  • Date Resolved: Partial (DTS disabled temporarily)

  • Workaround: Disabled DTS generation in tsup.config.ts

  • Next Steps: Fix TypeScript errors in parser/parser.ts

BUG-003: Redis authentication failures in search API 🟡 OPEN

  • Status: Open 🔴

  • Priority: High

  • Component: apps/search-api

  • Description: Search API cannot connect to Redis due to missing password

  • Steps to Reproduce:

    1. Start search API service

    2. Observe Redis NOAUTH errors in logs

  • Expected Result: Successful Redis connection

  • Actual Result: Repeated “NOAUTH Authentication required” errors

  • Environment: Redis 7.x in Docker, ioredis client

  • Assigned To: DevOps Team

  • Date Reported: 2025-06-03

  • Date Resolved: N/A

  • Fix Applied: Added Redis password to .env.local (needs restart)

BUG-004: Microservices missing source files and dependencies 🟢 OPEN

  • Status: Open 🔴

  • Priority: Medium

  • Component: apps/* (multiple services)

  • Description: Several microservices lack implementation files

  • Steps to Reproduce:

    1. Run pnpm run dev from project root

    2. Observe services failing due to missing src/index.ts

  • Expected Result: All services start successfully

  • Actual Result: Multiple service startup failures

  • Environment: Turbo monorepo, Node.js 24.1.0

  • Assigned To: Architecture Team

  • Date Reported: 2025-06-03

  • Services Affected:

    • analytics-engine (missing src/index.ts)

    • Multiple package builds failing

  • Next Steps: Create minimal service implementations

BUG-005: Supabase client configuration with placeholder values 🔵 OPEN

  • Status: Open 🔴

  • Priority: Low

  • Component: frontend/lib/supabase/client.ts

  • Description: Supabase client configured with placeholder URLs

  • Steps to Reproduce:

    1. Check .env.local for Supabase configuration

    2. Note placeholder values

  • Expected Result: Valid Supabase configuration or graceful fallback

  • Actual Result: Placeholder configuration that could cause issues

  • Environment: Next.js 15, Supabase client

  • Assigned To: Frontend Team

  • Date Reported: 2025-06-03

  • Status: Mitigated with null client handling

  • Next Steps: Decide on authentication strategy (Supabase vs custom auth)

Bug Report Template

### BUG-XXX: [Title] [Priority Icon]
- **Status**: [Open/In Progress/Fixed/Closed] [Icon]
- **Priority**: [Critical/High/Medium/Low]
- **Component**: [affected component/file]
- **Description**: [Brief description of the issue]
- **Steps to Reproduce**:
  1. [Step 1]
  2. [Step 2]
  3. [Step 3]
- **Expected Result**: [What should happen]
- **Actual Result**: [What actually happens]
- **Environment**: [OS, browser, versions, etc.]
- **Assigned To**: [Team/Person]
- **Date Reported**: [YYYY-MM-DD]
- **Date Resolved**: [YYYY-MM-DD or N/A]
- **Fix Details**: [Description of the fix applied]

Bug Management Workflow

  1. Discovery: Bug identified during development/testing

  2. Triage: Priority and severity assigned

  3. Assignment: Bug assigned to appropriate team/person

  4. Investigation: Root cause analysis performed

  5. Fix: Solution implemented and tested

  6. Verification: Fix verified in target environment

  7. Closure: Bug marked as resolved and documented

Integration Notes

This bug tracker is designed to work with Claude Code for:

  • Automatic bug discovery during development

  • Status updates as fixes are applied

  • Integration with todo management

  • Code reference linking

Maintenance

  • Review weekly for status updates

  • Archive resolved bugs older than 30 days

  • Generate monthly bug reports

  • Update priority based on business impact