A system that can quickly detect GLR problems

I would like to see a system that can quickly detect problems, such as detecting malfunctions in the GLR.

Also, if a problem with the GLR is discovered, I would like to see a system put in place that allows users and F5 to quickly determine the cause.

I also want the system when a problem occurs in GLR, it will be possible to investigate the cause (expanding the log output function, etc.)


Previously, there was an issue where logs could not be sent from GLR for a certain period of time.

It wasn't a system problem on the F5 side, but I was late in realizing that the logs were not delayed, and I did not know the cause.

At the time, it seems the queue was stuck, but the cause was never discovered.

Therefore, I would like them to create a mechanism to immediately detect if there is a problem with GLR (for example, an alert would be sent if logs cannot be sent for a certain period of time).

I also hope that when a problem occurs in GLR, a mechanism will be established that will enable investigation into the cause, even if it is not noticed until later.


Since security logs were not being transferred, it would have a significant impact on the situation that if XC was be attacked but not be able to see the logs.

I would like this system to be implemented as soon as possible.

  • Yui Iida
  • Jul 14 2025
  • Attach files