Generating events in excess of licensed event count

Abstract

In various implementations, a computer-implemented method for remotely managing settings of applications includes receiving a network communication from a managed device, the received network communication including a client-side hash value. The method further includes identifying settings for an application on the managed device in response to the receiving of the network communication, where the identified settings include configuration instructions for the application. Based on a comparison between the received client-side hash value and a server-side hash value that corresponds to the identified settings, at least some of the identified settings are transmitted to the managed device. The transmitting of the at least some of the identified settings can be based on the comparison indicating a mismatch between the received client-side hash value and the server-side hash value. The method may also include completing processing of the received network communication after the transmitting of the at least some of the identified settings.

What is claimed: 
     
         1 . A method implemented using a computing device, comprising:
 receiving raw data from one or more devices;   generating a plurality of time stamped events from the raw data;   determining a number of events of the plurality of time-stamped events that were generated during a specified time period and that are associated with a particular account or project;   comparing the number of events that were generated during the specified time period to an event count associated with the particular account or project;   in response to a determination that the number of events that were generated during the specified time period has reached the event count associated with the particular account or project, determining, based on a license associated with the particular account or project, that the particular account or project is permitted to exceed the event count without using an overflow storage location or increasing the event count; and   generating up to a threshold number of excess events from excess raw data received subsequent to the event count being reached.   
     
     
         2 . The method of  claim 1 , wherein the determining that the particular account or project is permitted to exceed the event count is further based on the particular account or project exceeding the event count less than a limited number of times. 
     
     
         3 . The method of  claim 1 , further comprising, in response to permitting the particular account or project to exceed the event count without using the overflow storage location or increasing the event count, associating a fee with the particular account or project for exceeding the event count. 
     
     
         4 . The method of  claim 1 , wherein the determining the number of events of the plurality of time-stamped events that were generated during the specified time period includes determining that the number of events are associated with the particular account, determined from a plurality of user accounts. 
     
     
         5 . The method of  claim 1 , wherein the determining the number of events of the plurality of time-stamped events that were generated during the specified time period includes determining that the number of events are associated with the particular project, determined from a plurality of projects. 
     
     
         6 . The method of  claim 1 , wherein the event count specifies a maximum number, or a maximum average number, of events generated during the specified time period. 
     
     
         7 . The method of  claim 1 , further comprising, in response to a determination that a second number of events generated during a second specified time period has reached a second event count for a second account or project, ceasing to accept raw data from the second account or project. 
     
     
         8 . The method of  claim 1 , further comprising, in response to a determination that a second number of events generated during a second specified time period has reached a second event count for a second account or project, continuing to accept excess raw data from the second account or project but ceasing to generate new events from the excess raw data raw data from the second account or project. 
     
     
         9 . The method of  claim 1 , further comprising, in response to a determination that a second number of events generated during a second specified time period has reached a second event count for a second account or project, automatically increasing the second event count for the second account or project. 
     
     
         10 . One or more non-transitory computer-readable storage media, storing instructions, which when executed by one or more processors cause the one or more processors to perform operations comprising:
 receiving raw data from one or more devices;   generating a plurality of time stamped events from the raw data;   determining a number of events of the plurality of time-stamped events that were generated during a specified time period and that are associated with a particular account or project;   comparing the number of events that were generated during the specified time period to an event count associated with the particular account or project;   in response to a determination that the number of events that were generated during the specified time period has reached the event count associated with the particular account or project, determining, based on a license associated with the particular account or project, that the particular account or project is permitted to exceed the event count without using an overflow storage location or increasing the event count; and   generating up to a threshold number of excess events from excess raw data received subsequent to the event count being reached.   
     
     
         11 . The one or more non-transitory computer-readable storage media of  claim 10 , wherein the determining that the particular account or project is permitted to exceed the event count is further based on the particular account or project exceeding the event count less than a limited number of times. 
     
     
         12 . The one or more non-transitory computer-readable storage media of  claim 10 , the operations further comprising, in response to permitting the particular account or project to exceed the event count without using the overflow storage location or increasing the event count, associating a fee with the particular account or project for exceeding the event count. 
     
     
         13 . The one or more non-transitory computer-readable storage media of  claim 10 , wherein the determining the number of events of the plurality of time-stamped events that were generated during the specified time period includes determining that the number of events are associated with the particular account, determined from a plurality of user accounts. 
     
     
         14 . The one or more non-transitory computer-readable storage media of  claim 10 , wherein the determining the number of events of the plurality of time-stamped events that were generated during the specified time period includes determining that the number of events are associated with the particular project, determined from a plurality of projects. 
     
     
         15 . The one or more non-transitory computer-readable storage media of  claim 10 , wherein the event count specifies a maximum number, or a maximum average number, of events generated during the specified time period. 
     
     
         16 . The one or more non-transitory computer-readable storage media of  claim 10 , the operations further comprising, in response to a determination that a second number of events generated during a second specified time period has reached a second event count for a second account or project, ceasing to accept raw data from the second account or project. 
     
     
         17 . The one or more non-transitory computer-readable storage media of  claim 10 , the operations further comprising, in response to a determination that a second number of events generated during a second specified time period has reached a second event count for a second account or project, continuing to accept excess raw data from the second account or project but ceasing to generate new events from the excess raw data raw data from the second account or project. 
     
     
         18 . The one or more non-transitory computer-readable storage media of  claim 10 , the operations further comprising, in response to a determination that a second number of events generated during a second specified time period has reached a second event count for a second account or project, automatically increasing the second event count for the second account or project. 
     
     
         19 . A system, comprising:
 one or more processors; and   one or more non-transitory computer-readable storage media storing instructions, which when executed by the one or more processors cause the one or more processors to perform operations comprising:
 receiving raw data from one or more devices; 
 generating a plurality of time stamped events from the raw data; 
 determining a number of events of the plurality of time-stamped events that were generated during a specified time period and that are associated with a particular account or project; 
 comparing the number of events that were generated during the specified time period to an event count associated with the particular account or project; 
 in response to a determination that the number of events that were generated during the specified time period has reached the event count associated with the particular account or project, determining, based on a license associated with the particular account or project, that the particular account or project is permitted to exceed the event count without using an overflow storage location or increasing the event count; and 
 generating up to a threshold number of excess events from excess raw data received subsequent to the event count being reached. 
   
     
     
         20 . The system of  claim 19 , wherein the determining that the particular account or project is permitted to exceed the event count is further based on the particular account or project exceeding the event count less than a limited number of times.