🐞 Bug Summary

The LLM-Guard plugin has minor performance issues that contribute to overall latency. These are lower priority than #1960 but should be addressed for optimal performance.

🧩 Affected Component

• mcpgateway - API
• mcpgateway - UI (admin panel)
• mcpgateway.wrapper - stdio wrapper
• Federation or Transports
• CLI, Makefiles, or shell scripts
• Container setup (Docker/Podman/Compose)
• Other: plugins/llm-guard

🔍 Performance Issues Identified

📋 Tasks

• Lazy scanner initialization

  • Initialize scanners on first use, not plugin load
  • Implement scanner pool for reuse
  • Add initialization timing metrics

• Reduce logging overhead

  • Use lazy log formatting
  • Add log level guards
  • Batch debug logs where possible

• Optimize vault retrieval

  • Cache vault lookups
  • Batch vault queries
  • Add vault cache invalidation on updates

• Improve error handling specificity

  • Add specific exception types
  • Include context in error messages
  • Add error categorization for metrics

• Add comprehensive metrics

  • Scanner initialization time
  • Per-scanner execution time
  • Error rates by type
  • Vault operation latency

🎯 Success Criteria

• Plugin startup time reduced by 30%
• Logging overhead < 1ms per request
• Vault cache hit rate > 90%
• All errors have actionable messages
• Metrics available in Prometheus format

🔗 Related Issues

• Related: [BUG][PERFORMANCE]: Fix high-impact performance issues in llm-guard plugin #1960 (High-impact performance issues in llm-guard)
• Consider merging with [BUG][PERFORMANCE]: Fix high-impact performance issues in llm-guard plugin #1960 if implementing together