Salesforce Com, Inc.

Siebel Systems, Inc.

Other

Salesforce, Inc.

Alex S Warshavsky

Adam Torman

Samarpan Jain

Aakash Pradeep

Bulent Cinarkaya

Soumen Bandyopadhyay

Irandi Upeka Bulumulla

Steven Tamm

David Brooks

Jayesh Sureshchandra

Kenneth Douglas Scott

Benjamin Fry

Vinod Mehra

Peter Dapkus

Abhishek Bangalore Sreenivasa

Thomas William D'Silva

Nate Horne

Lawrence Eugenio McAlpin

Choapet Oravivattanakul

Ryan Guest

Jeffrey Fischer

Aaron Fiske

Chandrakant Ramkrishna Bhavsar

Brian St Clair

Doug Bitting

Alexis Viripaeff

Brian Zotter

Jimmy Hua

Carol Franger

Yurika Sebata-Dempster

Lexi Viripaeff

Tripti Sheth

Derrill Dabkoski

Bhumi Damania

Dan Li

Ivan Daya Weiss

Robert C Woollen

John Arlan Brock

Eli Levine

Jan Asita Fernando

Hal Scott Hildebrand

Alexey Syomichev

Yingwu Zhao

Herman Kwong

Bobby Ng

Matthew Philip Grumbach

Igor Pesenson

Ashwin Kashyap

Patrick Lu

Rita Chang

Wenzhi Lai

Peklui Cheng

Somesh Sasalatti

Adam Tarman

A method for failure event notification in an event recordation and distribution system. The method including monitoring each stage of processing of an event by an event publisher manager, detecting a failure of the event to publish in the event recordation and distribution system, and publishing an error event notification to a status stream in response to detecting the failure.

Error notification mechanism for streaming events

A method of per subscription event filtering is provided for an event recordation and distribution system. The method includes receiving an event from the event recordation and distribution system, determining that an event consumer that is a subscriber of an event stream of the event has specified filter logic for the event stream, and forwarding the event to an event consumer in response to the event meeting requirements of the specified filter logic.

Streaming event content based filtering

A method and system for event consumers management are described. A batch of events that is stored in an event recordation system according to an aggregate topic is received based on the aggregate topic. Each event from the batch of events is associated with an initial topic to be used by a respective instance of an event consumer from a set of event consumers to consume events. A first initial topic associated with one or more events from the batch of events is determined. Based on the first initial topic, a state of a first event consumer is updated to a running state. The updated state of the first event consumer causes execution of a first instance of the first event consumer on a server of a cluster of servers for consuming events from the event recordation system based on the first initial topic.

Method and system for event consumer management in an aggregated event platform

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.

System having in-memory buffer service, temporary events file storage system and events file uploader service

In accordance with embodiments, there are provided mechanisms and methods for publicly providing web content of a tenant using a multi-tenant on-demand database service. These mechanisms and methods for publicly providing web content of a tenant using a multi-tenant on-demand database service can allow the web content to be published by a tenant using the multi-tenant on-demand database service for use by non-tenants of the multi-tenant on-demand database service.

Publicly providing web content of a tenant using a multi-tenant on-demand database service

A processor can cause a first communication, to a user device, of a first item based on an eventing system being in a first mode, a configuration to cause the eventing system to cause, without a request from the user device, a communication of an item to the user device in response to an entry of the item into a memory. After the first communication, the processor can cause the eventing system to be in a second mode, a configuration to cause the eventing system to refrain from communications of items to the user device. The processor can receive, from the user device, a signal to cause the eventing system to switch from the second mode to the first mode. After receiving the signal, a second item can be entered into the information memory. The processor can cause a second communication, to the user device, of the second item.

Hybrid eventing system

A method and system for event delivery are described. A batch of events for a first topic with replay identifiers is received. Responsive to determining that there is an active replay identifier discontinuity information for the first topic, a determination is performed of whether the first batch of events includes a second set of events that fills the discontinuity identified in the replay identifier discontinuity information. Upon determining that the first batch of events includes a second subset of events with second respective replay identifiers that start from the last replay identifier and do not include a discontinuity the second subset of events is transmitted to an event consumer, and the replay identifier discontinuity information for the first topic is updated based on the second subset of events transmitted.

Method and system for detection and handling of discontinuities in event delivery systems

A database system may determine that a database is unavailable to generate an identifier for an event or that events may not be written to the database. As a result, the database system may write the event to a low-latency, supplementary file system. The database system may determine that the database is available at a later time, and read the event from the supplementary file system, store the event in a memory component, and then delete the event from the supplementary file system. The database system may then access the database to generate an identifier for the event, write the event to the database, and then delete the event from the memory component.

Reliable generation of a unique key in a distributed system

A system derives a first schema that is specific to a first log entry type associated with a log code, a second schema that is specific to a second log entry type associated with the log code, and a common schema for the first log entry type and the second log entry type. The system stores the first schema and the common schema in a container for the first log entry type, and the second schema and the common schema in a container for the second log entry type. The system identifies a schema identifier in a log entry corresponding to a system user event. The schema identifier corresponds to a schema in the container for the first log entry type or the container for the second log entry type. The system identifies log data by applying the corresponding schema to the log entry, and outputs the log data.

Complex log entry type schemas

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.

Processing log files using a database system

System parses fields in a log entry, corresponding to a system user event, to identify a log code for a first and second log entry types. System identifies a common schema for the first and second log entry types. System identifies a schema identifier by applying the common schema to the log entry. The schema identifier corresponds to a schema in a container for the first log entry type or a container for the second log entry type. The container for the first log entry type includes the common schema and a first schema that is specific to the first log entry type. The container for the second log entry type includes the common schema and a second schema that is specific to the second log entry type. System identifies log data by using the corresponding schema to parse fields in the log entry, and outputs the log data.

Parsing complex log entry types

Disclosed are examples of systems, apparatus, methods and computer program products for creating custom platform objects for a multi-tenant non-relational database environment. A database system maintains a multi-tenant non-relational database associated with multiple enterprises and a number of records for each of the enterprises. The system also maintains a dynamic virtual table associated with a number of records. A request is received from one of the enterprises to define a custom data object within the database system, uniquely associated with an enterprise. The request is processed, and a custom object is generated based on the request. The custom object defines database columns corresponding to the data object and the enterprise. The virtual table is updated to include virtual columns corresponding to the database column definitions, and existing columns of a shared table in the non-relational database are updated to match the virtual columns. Access to the existing columns is then restricted for enterprises not uniquely associated with the custom data object.

Custom multi-tenant non-relational platform objects

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 log file having a release version. The log file includes data entries identifying system events corresponding to user activity. The server generates or updates, based on the release version of the log file, a metadata file indicating approved entry types and approved data. The server also generates or updates, based on the log file and the metadata file, customer-facing log files. Each customer-facing log file is associated with a corresponding customer entity capable of being serviced by the database system. Each customer-facing log file includes a subset of the entries and a subset of the data items of at least one of the entries.

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.

Methods and systems for processing a log file

Growing community of inventors

Walnut Creek, CA, United States of America

Alex S Warshavsky