arshirazi commited on
Commit
e478a2c
·
verified ·
1 Parent(s): 4edf474

Update Readme

Browse files
Files changed (1) hide show
  1. README.md +60 -174
README.md CHANGED
@@ -2,207 +2,93 @@
2
  base_model: unsloth/qwen3-4b-unsloth-bnb-4bit
3
  library_name: peft
4
  pipeline_tag: text-generation
 
5
  tags:
6
  - base_model:adapter:unsloth/qwen3-4b-unsloth-bnb-4bit
7
  - lora
8
  - transformers
9
  - unsloth
 
 
10
  ---
11
 
12
- # Model Card for Model ID
13
 
14
- <!-- Provide a quick summary of what the model is/does. -->
 
 
 
15
 
 
 
 
16
 
 
17
 
18
- ## Model Details
 
19
 
20
- ### Model Description
 
 
21
 
22
- <!-- Provide a longer summary of what this model is. -->
23
 
 
 
24
 
 
 
 
 
 
25
 
26
- - **Developed by:** [More Information Needed]
27
- - **Funded by [optional]:** [More Information Needed]
28
- - **Shared by [optional]:** [More Information Needed]
29
- - **Model type:** [More Information Needed]
30
- - **Language(s) (NLP):** [More Information Needed]
31
- - **License:** [More Information Needed]
32
- - **Finetuned from model [optional]:** [More Information Needed]
33
 
34
- ### Model Sources [optional]
35
 
36
- <!-- Provide the basic links for the model. -->
 
 
37
 
38
- - **Repository:** [More Information Needed]
39
- - **Paper [optional]:** [More Information Needed]
40
- - **Demo [optional]:** [More Information Needed]
 
 
 
41
 
42
- ## Uses
 
 
 
43
 
44
- <!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
45
 
46
- ### Direct Use
 
 
 
 
47
 
48
- <!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
49
 
50
- [More Information Needed]
 
 
 
51
 
52
- ### Downstream Use [optional]
 
 
 
 
53
 
54
- <!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
55
 
56
- [More Information Needed]
57
-
58
- ### Out-of-Scope Use
59
-
60
- <!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
61
-
62
- [More Information Needed]
63
-
64
- ## Bias, Risks, and Limitations
65
-
66
- <!-- This section is meant to convey both technical and sociotechnical limitations. -->
67
-
68
- [More Information Needed]
69
-
70
- ### Recommendations
71
-
72
- <!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
73
-
74
- Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
75
-
76
- ## How to Get Started with the Model
77
-
78
- Use the code below to get started with the model.
79
-
80
- [More Information Needed]
81
-
82
- ## Training Details
83
-
84
- ### Training Data
85
-
86
- <!-- This should link to a Dataset Card, perhaps with a short stub of information on what the training data is all about as well as documentation related to data pre-processing or additional filtering. -->
87
-
88
- [More Information Needed]
89
-
90
- ### Training Procedure
91
-
92
- <!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
93
-
94
- #### Preprocessing [optional]
95
-
96
- [More Information Needed]
97
-
98
-
99
- #### Training Hyperparameters
100
-
101
- - **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
102
-
103
- #### Speeds, Sizes, Times [optional]
104
-
105
- <!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
106
-
107
- [More Information Needed]
108
-
109
- ## Evaluation
110
-
111
- <!-- This section describes the evaluation protocols and provides the results. -->
112
-
113
- ### Testing Data, Factors & Metrics
114
-
115
- #### Testing Data
116
-
117
- <!-- This should link to a Dataset Card if possible. -->
118
-
119
- [More Information Needed]
120
-
121
- #### Factors
122
-
123
- <!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
124
-
125
- [More Information Needed]
126
-
127
- #### Metrics
128
-
129
- <!-- These are the evaluation metrics being used, ideally with a description of why. -->
130
-
131
- [More Information Needed]
132
-
133
- ### Results
134
-
135
- [More Information Needed]
136
-
137
- #### Summary
138
-
139
-
140
-
141
- ## Model Examination [optional]
142
-
143
- <!-- Relevant interpretability work for the model goes here -->
144
-
145
- [More Information Needed]
146
-
147
- ## Environmental Impact
148
-
149
- <!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
150
-
151
- Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
152
-
153
- - **Hardware Type:** [More Information Needed]
154
- - **Hours used:** [More Information Needed]
155
- - **Cloud Provider:** [More Information Needed]
156
- - **Compute Region:** [More Information Needed]
157
- - **Carbon Emitted:** [More Information Needed]
158
-
159
- ## Technical Specifications [optional]
160
-
161
- ### Model Architecture and Objective
162
-
163
- [More Information Needed]
164
-
165
- ### Compute Infrastructure
166
-
167
- [More Information Needed]
168
-
169
- #### Hardware
170
-
171
- [More Information Needed]
172
-
173
- #### Software
174
-
175
- [More Information Needed]
176
-
177
- ## Citation [optional]
178
-
179
- <!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
180
-
181
- **BibTeX:**
182
-
183
- [More Information Needed]
184
-
185
- **APA:**
186
-
187
- [More Information Needed]
188
-
189
- ## Glossary [optional]
190
-
191
- <!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
192
-
193
- [More Information Needed]
194
-
195
- ## More Information [optional]
196
-
197
- [More Information Needed]
198
-
199
- ## Model Card Authors [optional]
200
-
201
- [More Information Needed]
202
-
203
- ## Model Card Contact
204
-
205
- [More Information Needed]
206
  ### Framework versions
207
 
208
  - PEFT 0.20.0
 
2
  base_model: unsloth/qwen3-4b-unsloth-bnb-4bit
3
  library_name: peft
4
  pipeline_tag: text-generation
5
+ license: apache-2.0
6
  tags:
7
  - base_model:adapter:unsloth/qwen3-4b-unsloth-bnb-4bit
8
  - lora
9
  - transformers
10
  - unsloth
11
+ - log-parsing
12
+ - structured-output
13
  ---
14
 
15
+ # tiny-log-parser
16
 
17
+ LoRA adapter for Qwen3-4B that normalizes log lines from six wire formats into a
18
+ canonical 7-field JSON record. Paired with a deterministic epoch pre-pass it
19
+ reaches **100% exact match vs 83.5%** for `gemini-3.1-pro-preview` on a
20
+ 200-example held-out test set.
21
 
22
+ - **Code, eval harness, writeup:** https://github.com/arshirazi97/tiny-log-parser
23
+ - **Runnable demo:** [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/arshirazi97/tiny-log-parser/blob/main/demo.ipynb)
24
+ - **Base model:** `unsloth/qwen3-4b-unsloth-bnb-4bit`
25
 
26
+ ## What it does
27
 
28
+ Takes a log line in syslog RFC3164, nginx combined, logfmt, Java/log4j,
29
+ container JSON, or a bracketed application format, and emits:
30
 
31
+ `timestamp` (ISO8601 UTC, second precision) · `level` (one of CRITICAL, ERROR,
32
+ WARNING, INFO, DEBUG) · `service` · `trace_id` · `status_code` · `latency_ms`
33
+ (integer) · `message`
34
 
35
+ ## Results
36
 
37
+ 200-example held-out test set, same spec given to both systems, same exact-match
38
+ verifier, all seven fields must match.
39
 
40
+ | | Exact match | 95% CI | Latency p50 |
41
+ |---|---|---|---|
42
+ | gemini-3.1-pro-preview (3-shot) | 83.5% | 78.5 – 88.5% | 11,713 ms |
43
+ | this adapter alone (zero-shot) | 73.0% | 66.5 – 79.0% | 4,197 ms |
44
+ | **this adapter + epoch pre-pass** | **100%** | 100 – 100% | 4,197 ms |
45
 
46
+ The adapter alone loses. Every one of its 54 misses is a bare-epoch timestamp —
47
+ integer division into calendar arithmetic the model cannot do reliably. Scaling
48
+ training data 5k 20k moved that 0.5 points, so the conversion is routed to
49
+ `datetime.fromtimestamp()` instead of learned. It fires on 41 of 200 inputs.
 
 
 
50
 
51
+ ## Usage
52
 
53
+ ```python
54
+ from transformers import AutoTokenizer, AutoModelForCausalLM
55
+ from peft import PeftModel
56
 
57
+ BASE = "unsloth/qwen3-4b-unsloth-bnb-4bit"
58
+ tok = AutoTokenizer.from_pretrained(BASE)
59
+ model = PeftModel.from_pretrained(
60
+ AutoModelForCausalLM.from_pretrained(BASE, device_map="auto"),
61
+ "arshirazi/tiny-log-parser").eval()
62
+ ```
63
 
64
+ Requires a CUDA GPU — the base is 4-bit bitsandbytes, which does not run on
65
+ Apple Silicon or CPU. The adapter expects the exact prompt spec in `eval.py`
66
+ (`build_prompt(line, [])`) zero-shot; a different prompt format degrades output.
67
+ The epoch pre-pass lives in `score_hybrid.py`.
68
 
69
+ ## Training
70
 
71
+ 4-bit QLoRA, r=16, 2 epochs, response-masked so loss lands on the JSON only.
72
+ 20,000 synthetic examples generated canonical-record-first — the label exists
73
+ before the input, so every example is correct by construction. Train and test
74
+ draw from disjoint time windows (Jan–May vs Jun–Jul). Single RTX 2000 Ada
75
+ (16 GB), ~2.5 hours.
76
 
77
+ ## Limitations
78
 
79
+ The test set is synthetic, drawn from the same six renderers as training.
80
+ Disjoint time windows prevent timestamp memorization but not format
81
+ memorization. Read the 100% as "solved within its stated distribution," not as a
82
+ claim about production logs.
83
 
84
+ Real logs are harder: multiline stack traces, truncated lines, vendor quirks,
85
+ and formats outside these six are absent. Hand-written lines outside the
86
+ generator's parameter range surfaced two gaps the test set did not catch —
87
+ syslog severity 5/6 mapping, and a placeholder service name invented on a
88
+ truncated line.
89
 
90
+ Compared against one baseline, scored once, at temperature 0.
91
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
92
  ### Framework versions
93
 
94
  - PEFT 0.20.0