Methods and systems for processing a log file

• US 10,332,129 B2
• Filed: 10/31/2014
• Issued: 06/25/2019
• Est. Priority Date: 11/01/2013
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Torman, Adam, Warshavsky, Alex, Dabkoski, Derrill, D'Silva, Thomas William, Pradeep, Aakash, Woollen, Robert, Jain, Samarpan, Bandyopadhyay, Soumen
• Primary Examiner(s): Saeed, Usmaan
• Assistant Examiner(s): Weinrich, Brian E.
• Application Number:
  US14/529,674
• Publication Number:
  US 20150127670A1
• Time in Patent Office: 1,698 Days
• Field of Search: 707755
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06Q 30/0201 Market modelling; Market analysis; Collecting market data

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.

Claims

1. A system comprising:

a multi-tenant database system implemented using a server system comprising one or more hardware processors, the multi-tenant database system having a plurality of tenants, each tenant being a different business organization and comprising a different group of users having devices configured to access one or more on-demand database services provided by the multi-tenant database system, the multi-tenant database system configured to cause;

generating a log file comprising a plurality of log entries identifying a sequence of computing events performed for the tenants of the multi-tenant database system, the log entries comprising a plurality of data fields;

parsing the log file to;

identify a subset of the log entries as being of an approved one or more of a plurality of entry types, the approved one or more entry types being customized;

identify a first subset of the data fields of a first one or more of the log entries of the subset of log entries as;

being associated with a first customer identifier identifying a first one of the tenants of the multi-tenant database system, and

being of an approved one or more of a plurality of data field types, the approved one or more data field types being customized to identify fields to include in a customer-facing log file and identify fields to exclude from the customer-facing log file;

generating a first customer-facing log file to include only first log file data specific to the first tenant, the first log file data comprising the first subset of data fields of the first one or more log entries, the first customer-facing log file generated based at least in part on the first customer identifier being indicated by a client identifier data field in the first subset of data fields;

generating a second customer-facing log file to include only second log file data specific to a second one of the tenants of the multi-tenant database system, the second log file data comprising a second subset of the data fields of a second one or more of the log entries of the subset of log entries, the second customer-facing log file generated based at least in part on a second customer identifier identifying the second tenant being indicated by the client identifier data field in the second subset of data fields, the second customer-facing log file being different from the first customer-facing log file;

providing one or more security mechanisms configured to prevent a first group of users of the first tenant from accessing the second customer-facing log file and prevent a second group of users of the second tenant from accessing the first customer-facing log file; and

generating or updating a first reference and a second reference using data objects in a database, the first reference indicating a first location of the first customer-facing log file, the second reference indicating a second location of the second customer-facing log file.

2. The system of claim 1, the multi-tenant database system further configured to cause:

capturing a series of user events as at least a portion of the log entries in the log file.

3. The system of claim 1, wherein the approved one or more entry types and the approved one or more data field types are provided by a data file comprising attributions of entry types and data fields indicating the approved one or more entry types and the approved one or more data field types.

4. The system of claim 3, wherein the data file is an extensible markup language (XML) file.

5. The system of claim 1, the multi-tenant database system further configured to cause:

implementing the first reference and the second reference as pointers associated with the customer-facing log files, the pointers configured to be stored as data objects in the database.

6. The system of claim 5, wherein a user device is configured to access a customer-facing log file using an application programming interface (API) providing access to a pointer.

7. A computer implemented method associated with a multi-tenant database system implemented using a server system comprising one or more hardware processors, the multi-tenant database system having a plurality of tenants, each tenant being a different business organization and comprising a different group of users having devices configured to access one or more on-demand database services provided by the multi-tenant database system, the method comprising:

generating a log file comprising a plurality of log entries identifying a sequence of computing events performed for the tenants of the multi-tenant database system, the log entries comprising a plurality of data fields;

parsing the log file to;

identify a subset of the log entries as being of an approved one or more of a plurality of entry types, the approved one or more entry types being customized;

identify a first subset of the data fields of a first one or more of the log entries of the subset of log entries as;

being associated with a first customer identifier identifying a first one of the tenants of the multi-tenant database system, and

being of an approved one or more of a plurality of data field types, the approved one or more data field types being customized to identify fields to include in a customer-facing log file and identify fields to exclude from the customer-facing log file;

generating a first customer-facing log file to include only first log file data specific to the first tenant, the first log file data comprising the first subset of data fields of the first one or more log entries, the first customer-facing log file generated based at least in part on the first customer identifier being indicated by a client identifier data field in the first subset of data fields;

generating a second customer-facing log file to include only second log file data specific to a second one of the tenants of the multi-tenant database system, the second log file data comprising a second subset of the data fields of a second one or more of the log entries of the subset of log entries, the second customer-facing log file generated based at least in part on a second customer identifier identifying the second tenant being indicated by the client identifier data field in the second subset of data fields, the second customer-facing log file being different from the first customer-facing log file;

providing one or more security mechanisms configured to prevent a first group of users of the first tenant from accessing the second customer-facing log file and prevent a second group of users of the second tenant from accessing the first customer-facing log file; and

generating or updating a first reference and a second reference using data objects in a database, the first reference indicating a first location of the first customer-facing log file, the second reference indicating a second location of the second customer-facing log file.

8. The computer implemented method of claim 7, further comprising:

capturing a series of user events as at least a portion of the log entries in the log file.

9. The computer implemented method of claim 7, wherein the approved one or more entry types and the approved one or more data field types are provided by a data file comprising attributions of entry types and data fields indicating the approved one or more entry types and the approved one or more data field types.

10. The computer implemented method of claim 9, wherein the data file is an extensible markup language (XML) file.

11. The computer implemented method of claim 7, further comprising:

implementing the first reference and the second reference as pointers associated with the customer-facing log files, the pointers configured to be stored as data objects in the database.

12. The computer implemented method of claim 11, wherein a user device is configured to access a customer-facing log file using an application programming interface (API) providing access to a pointer.

13. A system comprising:

database system software stored on a non-transitory data storage medium for execution by one or more processors associated with a multi-tenant database system implemented using a server system comprising one or more hardware processors, the multi-tenant database system having a plurality of tenants, each tenant being a different business organization and comprising a different group of users having devices configured to access one or more on-demand database services provided by the multi-tenant database system, the database system software configured to cause;

generating a log file comprising a plurality of log entries identifying a sequence of computing events performed for the tenants of the multi-tenant database system, the log entries comprising a plurality of data fields;

parsing the log file to;

identify a subset of the log entries as being of an approved one or more of a plurality of entry types, the approved one or more entry types being customized;

identify a first subset of the data fields of a first one or more of the log entries of the subset of log entries as;

being associated with a first customer identifier identifying a first one of the tenants of the multi-tenant database system, and

being of an approved one or more of a plurality of data field types, the approved one or more data field types being customized to identify fields to include in a customer-facing log file and identify fields to exclude from the customer-facing log file;

generating a first customer-facing log file to include only first log file data specific to the first tenant, the first log file data comprising the first subset of data fields of the first one or more log entries, the first customer-facing log file generated based at least in part on the first customer identifier being indicated by a client identifier data field in the first subset of data fields;

generating a second customer-facing log file to include only second log file data specific to a second one of the tenants of the multi-tenant database system, the second log file data comprising a second subset of the data fields of a second one or more of the log entries of the subset of log entries, the second customer-facing log file generated based at least in part on a second customer identifier identifying the second tenant being indicated by the client identifier data field in the second subset of data fields, the second customer-facing log file being different from the first customer-facing log file;

providing one or more security mechanisms configured to prevent a first group of users of the first tenant from accessing the second customer-facing log file and prevent a second group of users of the second tenant from accessing the first customer-facing log file; and

generating or updating a first reference and a second reference using data objects in a database, the first reference indicating a first location of the first customer-facing log file, the second reference indicating a second location of the second customer-facing log file.

14. The system of claim 13, the database system software further configured to cause:

capturing a series of user events as at least a portion of the log entries in the log file.

15. The system of claim 13, wherein the approved one or more entry types and the approved one or more data field types are provided by a data file comprising attributions of entry types and data fields indicating the approved one or more entry types and the approved one or more data field types.

16. The system of claim 15, wherein the data file is an extensible markup language (XML) file.

17. The system of claim 13, the database system software further configured to cause:

implementing the first reference and the second reference as pointers associated with the customer-facing log files, the pointers configured to be stored as data objects in the database.

18. A computer program product comprising program code to be executed by at least one processor when retrieved from a non-transitory computer-readable medium, the program code associated with a multi-tenant database system implemented using a server system comprising one or more hardware processors, the multi-tenant database system having a plurality of tenants, each tenant being a different business organization and comprising a different group of users having devices configured to access one or more on-demand database services provided by the multi-tenant database system, the program code comprising instructions configured to cause:

generating a log file comprising a plurality of log entries identifying a sequence of computing events performed for the tenants of the multi-tenant database system, the log entries comprising a plurality of data fields;

parsing the log file to;

identify a subset of the log entries as being of an approved one or more of a plurality of entry types, the approved one or more entry types being customized;

identify a first subset of the data fields of a first one or more of the log entries of the subset of log entries as;

being associated with a first customer identifier identifying a first one of the tenants of the multi-tenant database system, and

being of an approved one or more of a plurality of data field types, the approved one or more data field types being customized to identify fields to include in a customer-facing log file and identify fields to exclude from the customer-facing log file;

generating a first customer-facing log file to include only first log file data specific to the first tenant, the first log file data comprising the first subset of data fields of the first one or more log entries, the first customer-facing log file generated based at least in part on the first customer identifier being indicated by a client identifier data field in the first subset of data fields;

generating a second customer-facing log file to include only second log file data specific to a second one of the tenants of the multi-tenant database system, the second log file data comprising a second subset of the data fields of a second one or more of the log entries of the subset of log entries, the second customer-facing log file generated based at least in part on a second customer identifier identifying the second tenant being indicated by the client identifier data field in the second subset of data fields, the second customer-facing log file being different from the first customer-facing log file;

providing one or more security mechanisms configured to prevent a first group of users of the first tenant from accessing the second customer-facing log file and prevent a second group of users of the second tenant from accessing the first customer-facing log file; and

generating or updating a first reference and a second reference using data objects in a database, the first reference indicating a first location of the first customer-facing log file, the second reference indicating a second location of the second customer-facing log file.

19. The computer program product of claim 18, wherein the approved one or more entry types and the approved one or more data field types are provided by a data file comprising attributions of entry types and data fields indicating the approved one or more entry types and the approved one or more data field types.

20. The computer program product of claim 18, the instructions further configured to cause:

implementing the first reference and the second reference as pointers associated with the customer-facing log files, the pointers configured to be stored as data objects in the database.