Troubleshooting iRules - Take Two!
summary
Recommends using VS Code with F5 extensions to edit, merge and set explicit iRule priorities (default 500) and warns to treat iRules as objects when saving. Advises log everything behind a static debug variable and try/catch, but avoid disk logging in prod; sample logs instead. Use command-line tools—curl, HTTPie, OpenSSL—and the tickle shell to validate Tcl syntax; timing shows simple math loop at ~1.59µs/iteration. Use source control, short idle TCP/UDP profiles to avoid stale connections, and run the rule profiler + Campfire or tstcl tests for performance.
AI-written summary · about
chapters (10)
- 0:00Intro
- 3:17Live Share
- 8:05Log Everything
- 8:49Troubleshooting Eyerolls
- 9:50Logging
- 16:11tcp reset
- 17:12curl openssl
- 24:28source control
- 27:06performance
- 33:44outro
related talks
15mAutomation Strategies: Real-World Experiences from F5 and
29mSwitchLog: A Logic Programming Language for Network Switches
43mFeature Toggles: The Good, The Bad and The Ugly
28mMy Favourite Errors
31mDebugging the Routing Tier
39mHow to Use Common Investigation Practices in Troubleshooting
39mTrust teams but verify: compliance as code done right
26mDouble, Double, Toil and Trouble!