Ingestion and processing of both cloud-based and non-cloud-based data by a data intake and query system

1. A computer-implemented method comprising:

acquiring a first data model for use by a data intake and query system, the first data model including a first search constraint;

ingesting first data, by a first software module, into the data intake and query system, at least a portion of the first data being cloud data, the first software module including a first event type definition that specifies a type of data to be ingested by the first software module, the first software module further including a first tag that associates ingested data of the first event type with the first data model and a second tag that designates ingested data of the first event type as cloud data;

storing the ingested first data in a data repository in association with the first tag and the second tag;

executing a search query that includes the first tag and the second tag against the data repository, to identify ingested cloud data that satisfies the search query and the first search constraint included in the first data model; and

causing a display device to display a visualization based on the identified ingested cloud data that satisfies the search query.

2. The computer-implemented method of claim 1 , wherein the search constraint specified in the first data model is not expressly set forth in the search query.

3. The computer-implemented method of claim 1 , wherein executing the search query comprises:

ascertaining that the search query is to apply the first data model based on a presence of the first tag in the search query; and

ascertaining that the search query is to retrieve cloud data based on a presence of the second tag in the search query.

4. The computer-implemented method of claim 1 , wherein the first software module includes a first configuration file that includes the first event type definition and at least one additional event type definition.

5. The computer-implemented method of claim 1 , wherein:

the first software module includes a first configuration file that includes the first event type definition and at least one additional event type definition; and

the first software module further includes a second configuration file that associates the first tag and the second tag with the first event type definition.

6. The computer-implemented method of claim 1 , wherein:

the first software module includes a first configuration file that includes the first event type definition and at least one additional event type definition;

the first software module further includes a second configuration file that associates the first tag and the second tag with the first event type definition; and

the first configuration file further includes a second event type definition, and wherein the second configuration file further includes the second tag in association with the second event type definition.

7. The computer-implemented method of claim 1 , wherein the first event type definition specifies a first set of parameters for identifying data to be ingested into the data intake and query system by the first software module.

8. The computer-implemented method of claim 1 , wherein the first data model specifies a first dataset, including the first search constraint and a first set of fields associated with the first dataset.

9. The computer-implemented method of claim 1 , wherein the first data represents a first plurality of events from a first data source of a first source type, and wherein the first software module is customized to ingest only data from sources of the first source type into the data intake and query system.

10. The computer-implemented method of claim 1 , wherein the first data represents a first plurality of events from a first data source, the first data source being of a first source type, and wherein the first software module is customized to ingest only data from sources of the first source type into the data intake and query system;

the method further comprising:

ingesting second data, by a second software module, into the data intake and query system, at least a portion of the second data being cloud data, the second software module including a second event type definition that specifies a type of data to be ingested by the second software module, the second software module further including the second tag to designate ingested data of the second event type as cloud data and a third tag to associate ingested data of the second event type with a second data model.

11. The computer-implemented method of claim 1 , wherein the first data comprises a plurality of different fields, and wherein said ingesting first data comprises:

ingesting data from a plurality of different source types, wherein a first field of the plurality of fields has different field names for at least two of the plurality of different source types; and

normalizing the different field names of the first field across the plurality of different source types.

12. The computer-implemented method of claim 1 , wherein the first data comprises a plurality of different fields, and wherein said ingesting first data comprises:

ingesting data from a plurality of different source types, wherein a first field of the plurality of fields has different field names for at least two of the plurality of different source types; and

normalizing the different field names of the first field across the plurality of different source types, by accessing a configuration file of the first software module, the configuration file containing a list of aliases of the first field name.

13. The computer-implemented method of claim 1 , wherein the first data model specifies a first dataset, including a first set of fields associated with the first dataset;

the method further comprising:

receiving user input defining a plurality of aliases for a first field name of a first field of the first set of fields; and

in response to the user input defining the plurality of aliases, storing the plurality of aliases in a configuration file of the first software module, for use by the first software module in normalizing the first field name across different data source types.

14. A computing device comprising:

a processor;

a memory, accessible to the processor, storing a first software module; and

a non-transitory computer-readable medium, accessible to the processor, having stored thereon instructions, execution of which by the processor causes the computing device to perform operations including:

acquiring a first data model for use by a data intake and query system, the first data model including a first search constraint;

ingesting first data, by a first software module, into the data intake and query system, at least a portion of the first data being cloud data, the first software module including a first event type definition that specifies a type of data to be ingested by the first software module, the first software module further including a first tag that associates ingested data of the first event type with the first data model and a second tag that designates ingested data of the first event type as cloud data;

storing the ingested first data in a data repository in association with the first tag and the second tag;

executing a search query that includes the first tag and the second tag against the data repository, to identify ingested cloud data that satisfies the search query and the first search constraint included in the first data model; and

causing a display device to display a visualization based on the identified ingested cloud data that satisfies the search query.

15. The computing device of claim 14 , wherein executing the search query comprises:

ascertaining that the search query is to apply the first data model based on a presence of the first tag in the search query; and

ascertaining that the search query is to retrieve cloud data based on a presence of the second tag in the search query.

16. The computing device of claim 14 , wherein:

the first software module includes a first configuration file that includes the first event type definition and at least one additional event type definition;

the first software module further includes a second configuration file that associates the first tag and the second tag with the first event type definition; and

the first configuration file further includes a second event type definition, and wherein the second configuration file further includes the second tag in association with the second event type definition.

17. The computing device of claim 14 , wherein the first data represents a first plurality of events from a first data source, the first data source being of a first source type, and wherein the first software module is customized to ingest only data from sources of the first source type into the data intake and query system;

said operations further including:

ingesting second data, by a second software module, into the data intake and query system, at least a portion of the second data being cloud data, the second software module including a second event type definition that specifies a type of data to be ingested by the second software module, the second software module further including the second tag to designate ingested data of the second event type as cloud data and a third tag to associate ingested data of the second event type with a second data model.

18. A non-transitory computer-readable medium having stored thereon instructions, execution of which by one or more processors in a data intake and query system causes the data intake and query system to perform operations including:

acquiring a first data model for use by the data intake and query system, the first data model including a first search constraint;

ingesting first data, by a first software module, into the data intake and query system, at least a portion of the first data being cloud data, the first software module including a first event type definition that specifies a type of data to be ingested by the first software module, the first software module further including a first tag that associates ingested data of the first event type with the first data model and a second tag that designates ingested data of the first event type as cloud data;

storing the ingested first data in a data repository in association with the first tag and the second tag;

executing a search query that includes the first tag and the second tag against the data repository, to identify ingested cloud data that satisfies the search query and the first search constraint included in the first data model; and

causing a display device to display a visualization based on the identified ingested cloud data that satisfies the search query.

19. The non-transitory computer-readable medium of claim 18 , wherein executing the search query comprises:

ascertaining that the search query is to apply the first data model based on a presence of the first tag in the search query; and

ascertaining that the search query is to retrieve cloud data based on a presence of the second tag in the search query.

20. The non-transitory computer-readable medium of claim 18 , such that:

the first software module includes a first configuration file that includes the first event type definition and at least one additional event type definition;

the first software module further includes a second configuration file that associates the first tag and the second tag with the first event type definition; and

the first configuration file further includes a second event type definition, and wherein the second configuration file further includes the second tag in association with the second event type definition.