log analyzer quarkus
Diagnose Quarkus application errors, CDI injection failures, and SmallRye configuration issues from JVM or Native logs.
$1
Works with the AI Agents you already use
log analyzer quarkus
Example session with this skill installed
Analyze this Quarkus log: 2023-10-27 10:15:03,142 ERROR [io.qua.run.Application] (main) Failed to start application: io.quarkus.runtime.configuration.ConfigDiagnosticException: SRCFG00014: property db.password is required.
- Read your context and instructions
- Compiled the log analyzer quarkus
I have analyzed the log provided. It indicates a critical configuration failure during the Quarkus bootstrap process.
REPORTE DE ANÁLISIS DE LOG — QUARKUS
| Sección | Detalle |
|---|---|
| Tecnología | Quarkus / JVM |
| Entorno | No declarado (Posible DEV/Local) |
| Componente | io.quarkus.runtime.configuration |
| Total eventos | 1 Crítico |
| Diagnóstico | La aplicación falló al iniciar debido a una propiedad de configuración obligatoria faltante. |
🔴 HALLAZGOS CRÍTICOS
- #1 Severidad: CRITICAL
- Ubicación:
io.qua.run.Application(main thread) - Mensaje:
SRCFG00014: property db.password is required
Causa raíz: SmallRye Config detectó que db.password no está definida en application.properties, variables de entorno, ni en el System Store.
- Acción sugerida: Definir
db.passworden el perfil activo o usar un valor por defecto si es permitido.
⚠️ DATOS SENSIBLES
- Tipo: Credencial (Password)
- Ubicación: Mensaje de error / Config
- Valor:
<span style="color:red;font-weight:bold">db.password</span> - Riesgo: Alta visibilidad de la clave de configuración requerida.
❓ PREGUNTAS ABIERTAS
- ¿El entorno es DEV, QA o PROD?
- ¿Tienes acceso al archivo
application.propertiesactual para verificar los perfiles (%prod,%dev)?
Next steps
- Check if the environment variable
DB_PASSWORDis exported in your shell or CI/CD pipeline. - Verify that the property is not commented out in
src/main/resources/application.properties. - Provide the full log if there are subsequent
Caused by:traces related to the data source.
Connects securely to your tools. The creator never sees your data.
About this skill
Troubleshooting Quarkus logs in production or dev mode often leads to a rabbit hole of CDI resolution errors and SmallRye configuration codes. This skill parses JVM and GraalVM native logs to identify the root cause of failures in io.quarkus applications.
What it does
- Standardized Log Parsing processes Quarkus-specific formats including category packages and thread names.
- Error Pattern Matching identifies specific codes like SRCFG configuration failures and UnsatisfiedResolutionException CDI issues.
- Sensitive Data Detection flags PII, JWT tokens, and database credentials that must be redacted or secured.
- Native vs JVM Analysis adjusts diagnostic logic for compressed GraalVM stack traces versus verbose JVM outputs.
- Structured Reporting generates a professional executive summary with severity levels and root cause hypotheses.
How it works
- Initial Screening identifies missing context such as environment (PROD/DEV) or truncated stack traces.
- Chain Tracing follows the
Caused by:sequence to find the originating component. - Pattern Correlation matches log events against known Quarkus failure modes like JDBC connection pools or SmallRye health checks.
- Diagnostic Output produces a formatted report with critical findings, warnings, and clear next steps.
Frameworks & tools
Specifically built for Quarkus, GraalVM, SmallRye Config, ArC (CDI), Netty, and JAX-RS (RESTEasy).
Why this beats prompting it yourself
Generic LLMs often miss the specific meaning of SmallRye error codes or fail to notice when a GraalVM native stack trace is misleading. This skill uses a strict diagnostic guide to avoid reporting cascade errors as primary causes.
Use cases
- Debugging
UnsatisfiedResolutionExceptionduring complex CDI bean injections. - Identifying specific missing properties signaled by
SRCFG00014orSRCFG00040codes. - Auditing logs for leaked secrets like Bearer tokens or internal hostnames.
- Root cause analysis for
JDBCConnectionExceptionin high-load environments.
Known limitations
Cannot fix code directly. Requires manual input of application.properties for configuration-related root cause verification. Limited accuracy with heavily truncated logs using ...X more.
Requires manual input of application.properties for config verification. Limited accuracy with logs using ...X more truncation. Cannot resolve issues without environment context.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 28 days ago
Permissions
No special permissions declared or detected