The latest articles on DEV Community by Swapnil Shitole (@swapnil_shitole_2fc46b932). https://dev.to/swapnil_shitole_2fc46b932 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3969485%2F4d47f9f6-fc7c-4d6c-b5c6-83975d49be32.jpg https://dev.to/swapnil_shitole_2fc46b932 en Swapnil Shitole Fri, 05 Jun 2026 08:31:55 +0000 https://dev.to/swapnil_shitole_2fc46b932/built-an-ai-powered-spring-boot-log-analyzer-using-rag-ollama-21d7 https://dev.to/swapnil_shitole_2fc46b932/built-an-ai-powered-spring-boot-log-analyzer-using-rag-ollama-21d7 <p>I've been working on a log analysis platform that helps debug Spring Boot applications by analyzing logs and stack traces using RAG.<br> <a href="https://loganalyzer.xyz/" rel="noopener noreferrer">https://loganalyzer.xyz/</a></p> <p>Tech stack:</p> <p>Spring Boot<br> Ollama (Qwen/Llama)<br> nomic-embed-text embeddings<br> PostgreSQL + pgvector</p> <p>It can parse logs, detect exceptions, retrieve similar incidents from a vector database, and explain potential root causes using an LLM.</p> <p>I'm looking for feedback on the architecture and approach. What would you improve for root-cause analysis of complex Java stack traces?</p> <p>Demo: <a href="https://loganalyzer.xyz/" rel="noopener noreferrer">https://loganalyzer.xyz/</a></p> ai rag showdev springboot