Regenerate integrations docs (#22290)
Co-authored-by: thiagoftsm <49162938+thiagoftsm@users.noreply.github.com>
Netdata bot committed
Apr 30, 2026 at 09:45 UTC
af5468276433ed9b4d3616d79e7bdcf32aa6e858
2 files changed
+59
-2
src/collectors/windows.plugin/integrations/memory_statistics_win.md
+10
-1
@@ -123,8 +123,17 @@ Metrics:
123
| Metric | Dimensions | Unit |
124
|:------|:----------|:----|
125
| mem.swap_iops | read, write | operations/s |
126
-| mem.swap_pages_io | read, write | pages/s |
126
+| mem.swapio | in, out | KiB/s |
127
| mem.system_pool_size | paged, non-paged | bytes |
128
+| mem.system_pool_paged | resident | bytes |
129
+| mem.system_pool_allocs | paged, non-paged | allocations/s |
130
| mem.system_page_table_entries | free | pages |
131
+| mem.committed | committed, limit | bytes |
132
+| mem.system_cache | cache, peak, resident | bytes |
133
+| mem.page_lists | free, modified, standby_core, standby_normal, standby_reserve | bytes |
134
+| mem.system_code | resident, total | bytes |
135
+| mem.system_drivers | resident, total | bytes |
136
+| mem.page_faults_breakdown | cache, demand_zero, transition, write_copies | faults/s |
137
+| mem.transition_repurposed | repurposed | pages/s |
138
139
src/go/plugin/go.d/collector/weblog/integrations/web_server_log_files.md
+49
-1
@@ -135,7 +135,7 @@ Notes:
135
<a id="option-customization-url-patterns"></a>
136
##### url_patterns
137
138
-"URL pattern" scope metrics will be collected for each URL pattern.
138
+"URL pattern" scope metrics will be collected for each URL pattern.
139
140
Option syntax:
141
@@ -450,4 +450,52 @@ If your Netdata runs in a Docker container named "netdata" (replace if different
450
docker logs netdata 2>&1 | grep web_log
451
```
452
453
+### High percentage of unparsed log lines (web_log_1m_unmatched alert)
454
+
455
+This alert indicates that more than 1% of log lines could not be parsed by the web_log collector over the last minute.
456
+
457
+**Common causes:**
458
+- Custom log format not matching any of the predefined formats
459
+- Log format has changed on the web server
460
+- Using a non-standard log format without proper configuration
461
+
462
+**Diagnostic steps:**
463
+
464
+1. Run the collector in debug mode to see unparsed lines:
465
+ ```bash
466
+ cd /usr/libexec/netdata/plugins.d/
467
+ sudo -u netdata -s
468
+ ./go.d.plugin -d -m web_log
469
+ ```
470
+
471
+2. Check the debug output for lines marked as unmatched to understand what format they have.
472
+
473
+**Resolution:**
474
+
475
+- If using a custom log format, configure `log_type` and the appropriate parser config:
476
+ - For CSV formats: set `log_type: csv` and configure `csv_config.format` to match your log format
477
+ - For custom patterns: set `log_type: regexp` and configure `regexp_config.pattern` with a regex containing named groups matching the known fields
478
+ - For JSON logs: set `log_type: json` and configure `json_config.mapping`
479
+ - For LTSV logs: set `log_type: ltsv` and configure `ltsv_config.mapping`
480
+
481
+
482
+### Unmatched lines due to non-standard log fields or extra columns
483
+
484
+Persistent unmatched entries appear even with auto-detection enabled.
485
+
486
+**Cause:**
487
+The log format includes fields not in the known-fields list (for example, custom headers, upstream timing, or unique IDs), preventing CSV auto-detection from matching any predefined format.
488
+
489
+**Resolution:**
490
+Set `log_type: csv` explicitly and specify `csv_config.format` using the known field variables that match the log's column order. Alternatively, use `log_type: regexp` with a `regexp_config.pattern` that captures only the known fields and ignores extras.
491
+
492
+
493
+### Suppressing the alert for known benign unmatched lines
494
+
495
+The web_log_1m_unmatched alert fires continuously but the unmatched lines are intentional (for example, health check logs in a different format).
496
+
497
+**Resolution:**
498
+Customize the alert threshold in `health.d/web_log.conf` by copying the web_log_1m_unmatched template and adjusting the warn condition, or silence notifications via Netdata Cloud alert configuration.
499
+
500
+
501