LogSage is a QLoRA fine-tuned adapter for structured log analysis and incident triage.
It takes raw logs or incident context and generates a structured diagnosis with:
issue
root_cause
severity
fix
confidence
This is not a general-purpose chatbot. It is a focused applied LLM experiment for DevOps, backend debugging, SRE workflows, and incident-response style reasoning.
Model Details
Field
Value
Model name
LogSage-Qwen2.5-7B-QLoRA-v0
Repository
auro-rirum/LogSage-Qwen2.5-7B-QLoRA-v0
Model type
PEFT / QLoRA adapter
Base model
unsloth/Qwen2.5-7B-Instruct-bnb-4bit
Task
Log analysis and incident triage
Output style
Structured JSON-style diagnosis
Training stack
Unsloth, Transformers, TRL, PEFT
License
Apache-2.0
Status
v0 applied fine-tuning prototype
Why This Model Exists
Production systems fail in patterns:
timeouts
deployment regressions
database saturation
queue backlogs
memory pressure
bad configuration changes
dependency failures
rate-limit cascades
During an incident, the first few minutes are often spent converting noisy logs into a useful hypothesis.
LogSage is designed to produce a first-pass structured diagnosis from logs so a human engineer can inspect, verify, and act faster.
The goal is not to replace an SRE. The goal is to compress the initial investigation loop.
Intended Use
Use this model for:
local log triage experiments
backend incident-analysis demos
SRE assistant prototypes
structured root-cause hypothesis generation
learning QLoRA fine-tuning workflows
building RAG + incident investigation systems
Do not use this model as the only decision-maker for production incidents. It can hallucinate, miss context, or overstate confidence.
1{2"issue":"Checkout requests are timing out in production.",3"root_cause":"Database connection pool exhaustion after a recent deploy changed pool settings.",4"severity":"high",5"fix":"Rollback the deploy or restore the previous database pool configuration. Then inspect database saturation and checkout-api connection usage.",6"confidence":"high"7}
Loading the Adapter Locally
This repository contains a PEFT adapter, not a fully merged standalone model.
You need to load the base model and then attach this adapter.
The v0 adapter was trained on a supervised instruction dataset for log diagnosis.
Each example follows this shape:
json
1{2"instruction":"Analyze the logs and return structured diagnosis.",3"input":"Raw logs and incident context...",4"output":{5"issue":"...",6"root_cause":"...",7"severity":"...",8"fix":"...",9"confidence":"..."10}11}
Approximate dataset size: 1.1k examples.
The dataset is intentionally small and focused. This model should be treated as a domain fine-tuning prototype, not a broad production incident-intelligence foundation model.
Training Method
This model was trained using QLoRA, a parameter-efficient fine-tuning method.
In this setup:
the base model remains quantized
most original weights remain frozen
small low-rank adapter weights are trained
the resulting adapter is much smaller than a full model checkpoint
This makes the experiment cheaper and easier to reproduce than full fine-tuning.
Evaluation Status
Current status: v0 prototype.
A full benchmark report is not included yet. Recommended evaluation areas:
Evaluation Area
What to Measure
JSON validity
Whether outputs follow the expected schema
Schema adherence
Whether required fields are always present
Severity quality
Whether severity labels are reasonable
Root-cause quality
Whether the model identifies the correct failure pattern
Fix usefulness
Whether the suggested fix is operationally realistic
Hallucination rate
Whether the model invents services, metrics, or deploys
Latency
Local inference time per sample
Planned evaluation table:
Metric
Result
JSON validity
TBD
Schema adherence
TBD
Severity accuracy
TBD
Root-cause match score
TBD
Average latency
TBD
Limitations
LogSage may:
hallucinate root causes when evidence is weak
overfit to common incident patterns
produce confident answers for incomplete logs
miss multi-service causal chains
fail on unseen log formats
require strict prompting to preserve JSON structure
produce fixes that need human verification
This model should be used as an assistant, not an authority.
Safety Notes
Do not paste secrets, credentials, private keys, access tokens, or sensitive production data into the model.
Before using this with real operational logs, add:
secret redaction
PII filtering
source citation
confidence scoring
human review
audit logging
Recommended Prompt Format
text
1You are LogSage, an incident triage assistant.
23Given logs and incident context, return only structured JSON with:
4issue, root_cause, severity, fix, confidence.
56Incident context:
7{context}
89Logs:
10{logs}
Roadmap
Add public evaluation report
Add held-out benchmark set
Add JSON validity metrics
Add latency benchmarks
Add local FastAPI server
Add Gradio demo
Add merged-model option
Add model comparison against base Qwen2.5
Add RAG integration for incident context
Add confidence calibration
Suggested Local Serving API
A simple local server can wrap the adapter behind an API like: