-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement request: Include the client's lockdown mode in uploaded events #1427
Comments
The Do you have a use case that requires you to distinguish |
The desire for that field stems from a set of reports that include things like "What applications are being run by devices in MONITOR mode? (Including Approved and Unapproved programs)". We can get it pretty close, but there are times when the server configured mode does not match the event upload timing perfectly, resulting in some incorrect data in reports. |
To be brief, it would be quite useful to know what mode (
lockdown
,monitor
) that a device was in when an event was recorded.In other words, we would like to add the
client_mode
field to the Event Object, to definitively indicate what mode the client was in when an event is generated.This would be very useful for reporting!
Q: Why don't you just mark it down on the sync server, when events are uploaded? The server is what sets the mode!
A: There's lots of caching going on, and timing. For example, the client might have more than one batch of events to upload, and the server does not know exactly when the client makes the switch from one mode to the other. While it would be possible for the server to make that determination, it would be complicated and inexact!
Thanks for your consideration!
The text was updated successfully, but these errors were encountered: