Forum Discussion

AlexBCT's avatar
AlexBCT
Icon for Cumulonimbus rankCumulonimbus
Oct 18, 2023
Solved

Timing/CPU info for BigIP DNS WideIP iRules

I just realized yesterday (or put better, one of my students pointed it out to me...) that BigIP DNS doesn't seem to hold timing information on the execution of iRules. For LTM, this ("show ltm rule <irule name>") is a great way of seeing roughly how much CPU power is required per iRule, and if there's any optimization that can be done, (https://clouddocs.f5.com/api/irules/timing.html). 

For BigIP DNS iRules though, and specifically the iRules under the Wide IP configuration, this doesn't seem to be recorded. "show gtm rule <irule name>" show the number of executions, but not the timing info. I've tried to lookup any information about this, or a clear statement that this does not NOT happen, but no luck so far. 

So, does anyone know if this information is available and I'm just looking in the wrong place, or if there's any reason why this isn't recorded? And if not, is there another way in which this information can be obtained? 

Thanks! 

  • Hi AlexBCT that information isn't available to the iRules applied to a wideIP because that happens in gtmd. The listener-based iRules are TMM and have that additional diagnostic data. The tracing data is also only TMM-based iRules.

5 Replies

    • Patrik_Jonsson's avatar
      Patrik_Jonsson
      Icon for MVP rankMVP

      Sorry, it does a lot, but not this particular thing. Sounds strange that it's left out though...

  • Hi AlexBCT that information isn't available to the iRules applied to a wideIP because that happens in gtmd. The listener-based iRules are TMM and have that additional diagnostic data. The tracing data is also only TMM-based iRules.

    • AlexBCT's avatar
      AlexBCT
      Icon for Cumulonimbus rankCumulonimbus

      I was afraid that it would be something like that, but was hoping there was something I missed! 🙂 

      Either way, thanks for the clarification, that makes sense - and good to know about the tracing data too!