# About this documentation

LLMS index: [llms.txt](/llms.txt)

---

This is the official documentation site for **DNSServer.DebugLogParser**, a PowerShell module that transforms Windows DNS Server debug log files into structured, analyzable CSV data.

## About the module

DNSServer.DebugLogParser was born from a real-world need: Windows DNS Server debug logs are human-readable text, but not suitable for analytics or reporting. This module bridges that gap by converting raw log files into structured CSV format that integrates with common tools like Excel, Power BI, SQL databases, and SIEM systems.

Key design principles:

- **Performance first** — optimized for 100MB+ files using streaming I/O and string operations
- **Cross-edition compatibility** — supports PowerShell Desktop (5.1+) and Core (7.x)
- **Production-ready** — includes header validation, error handling, and optional compression
- **Pipeline-friendly** — integrates naturally with PowerShell's pipeline architecture

## What is here

| Section | Read it when |
|---|---|
| [Overview](01-overview/) | You want to know what the module does and whether it fits your problem |
| [Output Formats](02-output-formats/) | You need to know what the CSV columns mean before designing a pipeline |
| [Parameters and Options](03-parameters-and-options/) | You are deciding which switches your conversion needs |
| [Performance](04-performance/) | Your logs are large or your conversion is slower than expected |
| [Integration](05-integration/) | You are loading the results into Excel, Power BI, SQL, a SIEM, or Python |
| [Operational Best Practices](06-operational-best-practices/) | You are about to run this unattended in production |
| [Usage Examples](examples/) | You want a worked end-to-end scenario to adapt |
| [Troubleshooting](08-troubleshooting/) | Something does not behave as expected |
| [Command Reference](commands/) | You need the authoritative parameter list |

New to the module? Start with the [Overview](01-overview/).

## Resources

- **GitHub**: [https://github.com/AndiBellstedt/DNSServer.DebugLogParser](https://github.com/AndiBellstedt/DNSServer.DebugLogParser)
- **PowerShell Gallery**: [https://www.powershellgallery.com/packages/DNSServer.DebugLogParser](https://www.powershellgallery.com/packages/DNSServer.DebugLogParser)
- **Author blog**: [https://andibellstedt.com](https://andibellstedt.com)

## Contributing

Contributions are welcome. If you find issues, errors, or have suggestions for improvements, please open an issue or pull request on the [GitHub repository](https://github.com/AndiBellstedt/DNSServer.DebugLogParser).

---

Section pages:

- [Overview](/docs/01-overview/): What DNSServer.DebugLogParser does, what a Windows DNS debug log looks like, and when converting it to CSV is worth the effort.
- [Output Formats](/docs/02-output-formats/): The columns of the CSV data file, the two optional statistics files, and real sample outputs you can open before you run anything.
- [Parameters and Options](/docs/03-parameters-and-options/): What each option of Convert-DNSDebugLogFile actually changes, when you need it, and the traps that are easy to walk into.
- [Performance](/docs/04-performance/): How the parser handles 100 MB logs without eating your server's memory, and what you can do to keep conversions fast.
- [Integration with Analysis Tools](/docs/05-integration/): Getting the converted CSV into Excel, Power BI, SQL Server, a SIEM, or a Python notebook — including the delimiter and date settings that make it work on the first attempt.
- [Operational Best Practices](/docs/06-operational-best-practices/): What to get right before you let a DNS log conversion run unattended on production domain controllers.
- [Troubleshooting](/docs/08-troubleshooting/): Symptoms you are likely to hit when converting DNS debug logs, what causes them, and how to fix them.
- [Module commands reference](/docs/commands/)
- [Usage Examples](/docs/examples/)
