Analysis of tokenized HTTP event collector
A data intake and query systems processes events received via the hypertext transfer protocol (HTTP). The HTTP events are associated with tokens. The received events are received by event collectors and distributed for storage. The data intake and query system receives requests to provide analyses and visualizations regarding the stored HTTP events. These requests can be customized based on selected tokens and selected data storage components. The visualizations are generated in response to the requests, and transmitted to the requesting device.
1. A computer-implemented method, comprising:
receiving, at a data intake and query system, a request to analyze a set of data associated with the data intake and query system;
identifying a token identifier of a plurality of token identifiers based on the request, wherein the token identifier corresponds to a token received as part of an internet protocol (IP) message, and wherein the token is indicative of a data source associated with the IP message;
identifying a plurality of events associated with the token and stored by the data intake and query system, wherein each event comprises a portion of raw machine data associated with a timestamp;
determining a graphical visualization based on the request and the plurality of events;
identifying, based on the request, one or more components of the data intake and query system that are associated with the plurality of events; and
generating visualization data for the graphical visualization based on the token and the identified one or more components.
2. The computer-implemented method of claim 1 , wherein the one or more components comprise a plurality of event collectors, wherein the plurality of event collectors are configured to receive the plurality of events and manage storage of the plurality of events.
3. The computer-implemented method of claim 1 , wherein the one or more components comprise a plurality of indexers, wherein the plurality of indexers are configured to store the plurality of events.
4. The computer-implemented method of claim 1 , wherein the one or more components comprise a plurality of forwarders, wherein the plurality of forwarders are configured to receive the plurality of events and forward the plurality of events for storage.
5. The computer-implemented method of claim 1 , further comprising identifying a performance metric based on the request, wherein the performance metric relates to an operation of the one or more components, and wherein the visualization data corresponds to the performance metric.
6. The computer-implemented method of claim 1 , wherein the visualization data relates to a percentage of the plurality of events that were successfully acknowledged for the one or more components.
7. The computer-implemented method of claim 1 , wherein the visualization data relates to a percentage of the plurality of events that were successfully acknowledged for the token.
8. The computer implemented method of claim 1 , further comprising identifying a performance metric based on the request, wherein the performance metric relates to an operation of the one or more components, wherein the visualization data corresponds to the performance metric, and wherein the performance metric comprises at least one of CPU-related performance metrics, disk-related performance metrics, memory-related performance metrics, network-related performance metrics, energy-usage statistics, data-traffic-related performance metrics, overall system availability performance metrics, cluster-related performance metrics, or virtual machine performance statistics.
9. The computer-implemented method of claim 1 , further comprising:
calculating values associated with the visualization data;
comparing the calculated values to a threshold; and
invoking a process based on the comparing.
10. The computer-implemented method of claim 1 , wherein the request comprises an identification of a plurality of data sources, wherein each of the plurality of data sources provides events to the components, and wherein the visualization data is related to the identified data sources.
11. The computer-implemented method of claim 1 , wherein the identified visualization comprises a bar chart, scatter plot, area chart, line chart, pie chart, radial gauge, marker gauge, or filler gauge.
12. The computer-implemented method of claim 1 , wherein the token provides metadata for the associated plurality of events.
13. The computer-implemented method of claim 1 , wherein the visualization data is based on per-token metrics and system-wide metrics.
14. A non-transitory computer-readable storage medium comprising instructions stored thereon, which when executed by one or more processors, cause the one or more processors to perform operations comprising:
receiving, at a data intake and query system, a request to analyze a set of data associated with the data intake and query system;
identifying a token identifier of a plurality of token identifiers based on the request, wherein the token identifier corresponds to a token received as part of an internet protocol (IP) message, and wherein the token is indicative of a data source associated with the IP message;
identifying a plurality of events associated with the token and stored by the data intake and query system, wherein each event comprises a portion of raw machine data associated with a timestamp;
determining a graphical visualization based on the request and the plurality of events;
identifying, based on the request, one or more components of the data intake and query system that are associated with the plurality of events; and
generating visualization data for the graphical visualization based on the token and the identified one or more components.
15. A system, comprising:
a communication interface;
at least one memory having instructions stored thereon; and
at least one processor configured to execute the instructions, wherein the at least one processor is configured to:
receive, at a data intake and query system, a request to analyze a set of data associated with the data intake and query system;
identify a token identifier of a plurality of token identifiers based on the request, wherein the token identifier corresponds to a token received as part of an internet protocol (IP) message, and wherein the token is indicative of a data source associated with the IP message;
identify a plurality of events associated with the token and stored by the data intake and query system, wherein each event comprises a portion of raw machine data associated with a timestamp;
determining a graphical visualization based on the request and the plurality of events;
identify, based on the request, one or more components of the data intake and query system that are associated with the plurality of events; and
generate visualization data for the graphical visualization based on the token and the identified one or more components.