Skip to content
DiagDebug

The DiagDebug network

A Fortinet community, run by the people who run the stack.

An independent, practitioner-led network of local chapters for Fortinet engineers. One set of trust rules, one bar for recognition, and a room in your metro that answers to its members, not to a quota.

The name is diag debug, the first command you type when something is on fire. If you know, you know. If you don't, welcome anyway.

What this is

A practitioner community for people who run Fortinet.

Peer knowledge sharing

The configs, the gotchas, the upgrade that went sideways at 2 a.m. Real deployments from the people who run them, and the fixes you only hear from someone who already hit the bug.

Access to Fortinet product teams

Where chapters want it, a direct line to Fortinet product and engineering: roadmap context, early looks at what's coming, and a channel to send feedback that reaches the people building the product.

Practitioner-run agenda

A steering committee of practitioners picks the topics and the speakers at every chapter. Sessions are technical, not sales pitches. The agenda answers to the members. Who runs it →

Who it's for

Practitioners.

If you touch a FortiGate, a FortiAnalyzer, or a support ticket about one, you're in the right place.

  • Network engineersRunning FortiGate at the edge, in the data center, or across a sprawl of branch sites.
  • Security architectsDesigning segmentation, SD-WAN, and Fabric integrations that have to survive an audit.
  • MSP and MSSP engineersManaging dozens of tenants and every firmware version that ever shipped.
  • Cert candidatesWorking the NSE and Fortinet Certified tracks, looking for study partners who have done the labs.
  • IT directors and managersRunning Fortinet environments and the teams that keep them up. Here for roadmap, staffing, and what is coming next.

Chapters

Find your metro.

Puget Sound is active. Spokane, Portland, Boise, and Salt Lake City are forming now.

View the full directory →

DiagDebug is an independent, practitioner-led community and is not affiliated with, sponsored by, or endorsed by Fortinet, Inc. Fortinet and FortiGate are trademarks of Fortinet, Inc., used here only to describe the community's shared area of practice.

No chapter in your metro yet?

If you run Fortinet and you would show up, you are probably the person to start one. Here is how.

Start a chapter