Abstract:
A database system captures custom information of a header section associated with a logged interaction of a user. The database system may receive a hypertext transfer protocol (http) message including the header section and determine whether the header section includes a predetermined data pattern associated with the custom information added by a second application that is different than a first application which initiated the http message. The database system may extract the custom information from the header section in response to determining that the header section includes the predetermined data pattern. The custom information and event data extracted from the logged interaction of the user may be stored on the database system as a storage element.
Abstract:
A capture service running on an application server receives events from a client application running on an application server to be stored in a data store and stores the events in an in-memory bounded buffer on the application server, the in-memory bounded buffer comprising a plurality of single-threaded segments, the capture service to write events to each segment in parallel. The in-memory bounded buffer provides a notification to a buffer flush regulator when a number of events stored in the in-memory bounded buffer reaches a predefined limit. The in-memory bounded buffer receive a request to flush the events in the in-memory bounded buffer from a consumer executor service. The consumer executor service consumes the events in the in-memory bounded buffer using a dynamically sized thread pool of consumer threads to read the segments of the bounded buffer in parallel, wherein consuming the events comprises writing the events directly to the data store.
Abstract:
Disclosed are methods, apparatus, systems, and computer program products for provisioning log file data. A server may parse through log files by selecting particular log entries and data fields. Customer-facing log files may be generated based on the selected log entries and data fields.
Abstract:
Disclosed are some implementations of systems, apparatus, methods and computer program products for facilitating policy-based file deletion. Policy-based file deletion is implemented via a tiered system that includes a master computing system and a plurality of slave computing systems. The master computing system distributes policies among the slave computing systems, which each applies assigned policies to cause deletion of files that satisfy those policies.
Abstract:
Disclosed are some examples of database systems, methods, and computer program products for processing log files. In some implementations, a server of a database system accesses a metadata file indicating algorithms that can be applied to data of log files. The server generates customer-facing log files using the log file and metadata file. The customer-facing log files include new data derived from using the algorithms and the data of the log files.
Abstract:
Computer-implemented methods and systems are provided for writing events to a data store. An application server generates events, the data store that stores the events, and a temporary events file storage system (TEFSS) temporarily stores groups of events as events files. When events are unable to be written directly to the data store, an indirect events writer is invoked that includes event capture threads each being configured to generate a particular events file, and write it to the TEFSS. Each events file includes a plurality of events flushed from an in-memory buffer service. An events file uploader service reads the events file(s) from the TEFSS, and then writes the events from each of the events files to the data store.
Abstract:
Disclosed are methods, apparatus, systems, and computer program products for provisioning log file data. To provision the log file data, a server can parse through log files by identifying particular log entries and data fields. Customer-facing log files can be generated based on the identified log entries and data fields. A customer-facing log file has log file data specific to a particular customer, which can be a tenant of a multi-tenant database system. A security mechanism can be configured to prevent one tenant from accessing the customer-facing log file of another tenant of the multi-tenant database system.
Abstract:
Disclosed are some implementations of systems, apparatus, methods and computer program products for facilitating policy-based file deletion. Policy-based file deletion is implemented via a tiered system that includes a master computing system and a plurality of slave computing systems. The master computing system distributes policies among the slave computing systems, which each applies assigned policies to cause deletion of files that satisfy those policies.
Abstract:
Computer-implemented methods and systems are provided for writing events to a data store. An application server generates events, the data store that stores the events, and a temporary events file storage system (TEFSS) temporarily stores groups of events as events files. When events are unable to be written directly to the data store, an indirect events writer is invoked that includes event capture threads each being configured to generate a particular events file, and write it to the TEFSS. Each events file includes a plurality of events flushed from an in-memory buffer service. An events file uploader service reads the events file(s) from the TEFSS, and then writes the events from each of the events files to the data store.
Abstract:
Computer-implemented methods and systems are provided. The system includes a data store that is configured to store events in an event table, a temporary events file storage system (TEFSS), and a cluster of application servers. The cluster includes a first application server that generates events, and a second application server that includes an events file uploader service. When the first application server is unable to directly write events to the data store, an indirect events writer generates events file(s), and writes the events file(s) to the TEFSS. Each events file includes a plurality of events flushed from an in-memory buffer service at the first application server. When the events file uploader service determines that the first application server is inactive, it reads the events file(s) from the TEFSS, and writes the events from each of the events files to the data store.