Concurrent
A concurrent network traffic monitor, responsible for tracking all the data sent via the loginChannelTrafficMonitor, the js5ChannelTrafficMonitor and the gameChannelTrafficMonitor. In addition to those, it will track the number of connections established, as well as any login complete login blocks that reach the server, based on the respective InetAddress behind the login blocks. Latter can be used to link any abnormalities to specific individuals.
While this implementation is mostly atomic, it will shortly block during the resetTransient function call, while it assigns new instances to all the properties behind this implementation. This is only done to ensure consistency between the properties. As the blocking is extremely short-lived, it should not cause any issues.
Constructors
Properties
the channel traffic monitor for game connections, essentially after a login request is accepted.
the channel traffic monitor for JS5.
the channel traffic monitor for logins (and "handshakes", as they are commonly referred to).
Functions
Adds a new login block from the provided inetAddress.
Freezes any transient traffic monitoring for this monitor, across all three of the channel monitors. The freeze function does not stop active connection tracking, however, as that could cause bad data in the future (number of connections going negative). This will block majority of the monitoring that goes on, though. This function has no effect if the traffic was already frozen.
Increments connections established in total.
Resets any transient metrics and captures a full traffic snapshot of everything that happened prior to the resetting. This snapshot function will use a short-lived synchronization block to ensure consistency in the data captured.
Creates a full network traffic snapshot covering all three of the channel traffic monitors. This snapshot function will not use synchronization during creation, so it is possible for slight inconsistencies to occur due to the data being cloned at slightly different moments.