You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue when the AlertLogic object is instantiated and long periods of idleness between calls, results in timeout. The call below at the beginning of all Event generation is not complete because it is simply checking against the AlertLogic variable al_logged_in
The problem is that this adds an additional http call to every single event generated. It is also not thread safe to modify the AlertLogic.al_logged_in variable. Best resolution would be to create a custom threading object and add locks. But this also still needs a threadpool and possibly queuing, so...... maybe one day...
Another kudos to @TheRemover for identifying the timeout issue!
The text was updated successfully, but these errors were encountered:
Issue when the
AlertLogic
object is instantiated and long periods of idleness between calls, results in timeout. The call below at the beginning of allEvent
generation is not complete because it is simply checking against the AlertLogic variableal_logged_in
which is only set at login:
Solution to resolve this would be:
AlertLogic:
Event:
The problem is that this adds an additional http call to every single event generated. It is also not thread safe to modify the
AlertLogic.al_logged_in
variable. Best resolution would be to create a custom threading object and add locks. But this also still needs a threadpool and possibly queuing, so...... maybe one day...Another kudos to @TheRemover for identifying the timeout issue!
The text was updated successfully, but these errors were encountered: