Parsing complex log entry types

1. A system for parsing complex log entry types, the system comprising:

one or more processors; and

a non-transitory computer readable medium storing a plurality of instructions, which when executed, cause the one or more processors to:

parse, by a computing system, fields in a log entry to identify a log code relating to a first log entry type and a second log entry type, the log entry corresponding to a system user event;

identify, by the computing system, a common schema for the first log entry type and the second log entry type;

identify, by the computing system, a schema identifier by applying the common schema to the log entry, the schema identifier corresponding to a schema in one of a container for the first log entry type and a container for the second log entry type, the first log entry type container comprising the common schema and a first schema specific to the first log entry type, the second log entry type container comprising the common schema and a second schema specific to the second log entry type;

identify, by the computing system, log data by using the corresponding schema to parse fields in the log entry; and

cause, by the computing system, the log data to be outputted.

2. The system of claim 1 , wherein the common schema comprises the log code, identifies a field containing payload data, and identifies a field used for identifying the corresponding schema.

3. The system of claim 1 , wherein the first schema and the second schema are based on corresponding subtype schemas in hierarchical formats.

4. The system of claim 1 , wherein the first schema identifies a first field name, a first field type, and a first field location, and the second schema identifies a second field name, a second field type, and a second field location.

5. The system of claim 1 , wherein at least one of the first schema, the second schema, the common schema, the container for the first log entry type, and the container for the second log entry type identify a release version of an application associated with the system user event.

6. The system of claim 1 , wherein the log data to be outputted corresponds to a log field approved for being accessed by an end user of a multi-tenant system, the end user being associated with a tenant of a plurality of tenants of the multi-tenant system.

7. The system of claim 1 , comprising further instructions, which when executed, cause the one or more processors to:

parse, by the computing system, fields in another log entry to identify another log code relating to a third log entry type, the other log code corresponding to another schema in a container for the third log entry type, the other log entry corresponding to another system user event;

identify, by the computing system, other log data by applying the other schema to the fields in the log entry; and

cause, by the computing system, the other log data to be outputted.

8. A computer program product comprising computer-readable program code to be executed by one or more processors when retrieved from a non-transitory computer-readable medium, the program code including instructions to:

parse, by a computing system, fields in a log entry to identify a log code relating to a first log entry type and a second log entry type, the log entry corresponding to a system user event;

identify, by the computing system, a common schema for the first log entry type and the second log entry type;

identify, by the computing system, a schema identifier by applying the common schema to the log entry, the schema identifier corresponding to a schema in one of a container for the first log entry type and a container for the second log entry type, the first log entry type container comprising the common schema and a first schema specific to the first log entry type, the second log entry type container comprising the common schema and a second schema specific to the second log entry type;

identify, by the computing system, log data by using the corresponding schema to parse fields in the log entry; and

cause, by the computing system, the log data to be outputted.

9. The computer program product of claim 8 , wherein the common schema comprises the log code, identifies a field containing payload data, and identifies a field used for identifying the corresponding schema.

10. The computer program product of claim 8 , wherein the first schema and the second schema are based on corresponding subtype schemas in hierarchical formats.

11. The computer program product of claim 8 , wherein the first schema identifies a first field name, a first field type, and a first field location, and the second schema identifies a second field name, a second field type, and a second field location.

12. The computer program product of claim 8 , wherein at least one of the first schema, the second schema, the common schema, the container for the first log entry type, and the container for the second log entry type identify a release version of an application associated with the system user event.

13. The computer program product of claim 8 , wherein the log data to be outputted corresponds to a log field approved for being accessed by an end user of a multi-tenant system, the end user being associated with a tenant of a plurality of tenants of the multi-tenant system.

14. The computer program product of claim 8 , wherein the program code comprises further instructions to:

parse, by the computing system, fields in another log entry to identify another log code relating to a third log entry type, the other log code corresponding to another schema in a container for the third log entry type, the other log entry corresponding to another system user event;

identify, by the computing system, other log data by applying the other schema to the fields in the log entry; and

cause, by the computing system, the other log data to be outputted.

15. A method comprising:

parsing, by a computing system, fields in a log entry to identify a log code relating to a first log entry type and a second log entry type, the log entry corresponding to a system user event;

identifying, by the computing system, a common schema for the first log entry type and the second log entry type;

identifying, by the computing system, a schema identifier by applying the common schema to the log entry, the schema identifier corresponding to a schema in one of a container for the first log entry type and a container for the second log entry type, the first log entry type container comprising the common schema and a first schema specific to the first log entry type, the second log entry type container comprising the common schema and a second schema specific to the second log entry type;

identifying, by the computing system, log data by using the corresponding schema to parse fields in the log entry; and

causing, by the computing system, the log data to be outputted.

16. The method of claim 15 , wherein the common schema comprises the log code, identifies a field containing payload data, and identifies a field used for identifying the corresponding schema.

17. The method of claim 15 , wherein the first schema and the second schema are based on corresponding subtype schemas in hierarchical formats, and wherein the first schema identifies a first field name, a first field type, and a first field location, and the second schema identifies a second field name, a second field type, and a second field location.

18. The method of claim 15 , wherein at least one of the first schema, the second schema, the common schema, the container for the first log entry type, and the container for the second log entry type identify a release version of an application associated with the system user event.

19. The method of claim 15 , wherein the log data to be outputted corresponds to a log field approved for being accessed by an end user of a multi-tenant system, the end user being associated with a tenant of a plurality of tenants of the multi-tenant system.

20. The method of claim 15 , wherein the method further comprises:

parsing, by the computing system, fields in another log entry to identify another log code relating to a third log entry type, the other log code corresponding to another schema in a container for the third log entry type, the other log entry corresponding to another system user event;

identifying, by the computing system, other log data by applying the other schema to the fields in the log entry; and

causing, by the computing system, the other log data to be outputted.