Telemetry redundant measurement avoidance protocol
The present disclosure describes a telemetry redundant measurement avoidance protocol (TRMAP) that solves redundant data collection problems in telemetry systems. The TRMAP can operate in a non-supervised environment and/or in a distributed manner, and does not require a central controller to manage multiple collection agents in one or multiple telemetry systems. The TRMAP can also be an opt-in-based protocol that favors altruistic data sharing and reuse between collection agents. In these ways, the TRMAP provides freedom and collaboration among developers or other entities that desired telemetry data, while allowing non-compliant collection agents to coexist, if possible.
1 . An apparatus comprising:
memory circuitry;
instructions; and
at least one processor circuit to be programmed based on the instructions to:
cause a request to access shared telemetry data to be sent to a set of telemetry agents;
obtain respective telemetry configuration messages from corresponding telemetry agents in the set of telemetry agents, the respective telemetry configuration messages including data sharing parameters for data permitted to be shared by the corresponding telemetry agents; and
determine whether to utilize the data permitted to be shared by the corresponding telemetry agents based on the data sharing parameters included in the respective telemetry configuration messages.
2 . The apparatus of claim 1 , wherein, to cause the request to be sent, one or more of the at least one processor circuit is to at least one of:
cause the request to be broadcast to one or more of the telemetry agents in the set of telemetry agents; or
cause the request to be sent to ones of the telemetry agents in the set of telemetry agents that have opted-in to participate in a telemetry redundant measurement avoidance protocol.
3 . The apparatus of claim 1 , wherein the apparatus is associated with a requestor agent, and the request includes at least one of an indication that the requestor agent has opted-in to participate in a telemetry redundant measurement avoidance protocol, a set of metrics to be collected by the requestor agent, or a request for collection configurations of the set of telemetry agents.
4 . The apparatus of claim 1 , wherein, to cause the request to be sent, one or more of the at least one processor circuit is to at least one of:
cause the request to be sent on a periodic basis; or
cause the request to be sent based on a detected trigger condition.
5 . The apparatus of claim 1 , wherein the data sharing parameters included in the respective telemetry configuration messages include at least one or more of a set of data types collected by the corresponding telemetry agents, a data storage location in which collected data is stored by the corresponding telemetry agents, a set of data sources from which the data is collected by the corresponding telemetry agents, or a set of at least one of time periods or intervals at which the corresponding telemetry agents collects data.
6 . The apparatus of claim 1 , wherein, to determine whether to utilize the data permitted to be shared by the corresponding telemetry agents, one or more of the at least one processor circuit is to:
compare attributes of the data sharing parameters in the respective telemetry configuration messages with attributes of data collection parameters in a manifest.
7 . The apparatus of claim 6 , wherein one or more of the at least one processor circuit is to execute the instructions to:
determine to utilize the data shared by the corresponding telemetry agents based on the attributes of the data sharing parameters being within at least one of a predetermined range or a configured range of the attributes of the data collection parameters.
8 . The apparatus of claim 6 , wherein one or more of the at least one processor circuit is to:
determine to relinquish collection of one or more metrics specified by the manifest based on the attributes of the data sharing parameters conflicting with the attributes of the data collection parameters.
9 . The apparatus of claim 6 , wherein one or more of the at least one processor circuit is to:
determine to relinquish collection of one or more metrics based on an analysis of data access logs related to the one or more metrics.
10 . The apparatus of claim 6 , wherein the data collection parameters in the manifest include at least one of:
a set of data types to be collected,
a set of data sources from which data is to be collected,
sharing permissions for one or more of the data types of the set of data types to be collected,
a set of data storage locations to store collected data,
a set of at least one of time periods or intervals at which data collection is to occur,
a set of at least one of conditions or triggers to initiate one or more data collection processes, or
telemetry system information.
11 . The apparatus of claim 1 , wherein the telemetry agents are included in a compute node, and the compute node is at least one of a desktop computer, a laptop computer, a mobile device, a workstation, a network appliance, a server, an edge compute node, or a cloud compute node.
12 . The apparatus of claim 1 , wherein in at least one of a network or cluster of compute nodes, and the network or cluster of compute nodes includes any combination of two or more of a desktop computer, a laptop computer, a mobile device, a workstation, a network appliance, a server, an edge compute node, or a cloud compute node.
13 . One or more non-transitory computer-readable media comprising instructions to cause at least one processor circuit to at least:
cause a request to be sent to a set of collection agents, the request to be for metrics collected by the set of collection agents;
obtain, from at least one collection agent in the set of collection agents, metric sharing parameters for metrics permitted to be shared by the at least one collection agent;
access at least one of the metrics based on the metric sharing parameters; and
cause the at least one of the metrics to be sent to an analytics function.
14 . The one or more non-transitory computer-readable media of claim 13 , wherein the request includes at least one of an indication that a requestor agent associated with the request has opted-in to participate in metric sharing, a set of metrics to be collected by the requestor agent, or a request for collection configurations of the set of collection agents.
15 . The one or more non-transitory computer-readable media of claim 13 , wherein the instructions are to cause one or more of the at least one processor circuit to at least one of:
cause the request to be sent on a periodic basis; or
cause the request to be sent in response to a detected trigger condition.
16 . The one or more non-transitory computer-readable media of claim 13 , wherein the metric sharing parameters include at least one of a set of data types collected by the at least one collection agent, a data storage location in which data is stored by the at least one collection agent, a set of data sources from which the data is collected by the at least one collection agent, or a set of at least one of time periods or intervals at which the at least one collection agent collects data.
17 . The one or more non-transitory computer-readable media of claim 13 , wherein the instructions are to cause one or more of the at least one processor circuit to:
compare attributes of the metric sharing parameters with attributes of metric collection parameters in a manifest to determine to utilize the at least one metric.
18 . The one or more non-transitory computer-readable media of claim 17 , wherein the instructions are to cause one or more of the at least one processor circuit to:
determine to utilize the at least one metric shared by the at least one collection agent based on the attributes of the metric sharing parameters being within at least one of a predetermined range or a configured range of the attributes of the metric collection parameters.
19 . The one or more non-transitory computer-readable media of claim 17 , wherein the instructions are to cause one or more of the at least one processor circuit to:
determine to relinquish collection of one or more metrics specified by the manifest based on the attributes of the metric sharing parameters conflicting with the attributes of the metric collection parameters.
20 . The one or more non-transitory computer-readable media of claim 17 , wherein the instructions are to cause one or more of the at least one processor circuit to:
determine to relinquish collection of one or more metrics based on an analysis of data access logs related to the one or more metrics.
21 . The one or more non-transitory computer-readable media of claim 17 , wherein the metric collection parameters in the manifest include at least one of:
a set of metrics to be collected,
a set of data sources from which metrics are to be collected,
sharing permissions for one or more of the metrics of the set of metrics,
a set of storage locations to store collected metrics,
a set of at least one of time periods or intervals at which metric collection is to occur,
a set of at least one of conditions or triggers to initiate one or more metric collection processes, or
metrics collection system information.
22 . A method comprising:
obtaining, by a first telemetry agent, a request for shared telemetry data from a second telemetry agent in a set of telemetry agents deployed in a system;
generating, by the first telemetry agent, a telemetry configuration message including metric sharing parameters for data permitted to be shared by the first telemetry agent; and
sending, by the first telemetry agent, the telemetry configuration message to the second telemetry agent.
23 . The method of claim 22 , wherein the request includes at least one of an indication that the second telemetry agent has opted-in to participate in metric sharing, a set of metrics to be collected by the second telemetry agent, or a request for metric sharing parameters from the first telemetry agent.
24 . The method of claim 22 , wherein the generating includes:
determining, by the first telemetry agent based on a manifest, a set of metrics permitted to be shared by the first telemetry agent; and
including the set of metrics and a set of collection attributes associated with the set of metrics in the telemetry configuration message.
25 . The method of claim 24 , wherein the set of collection attributes include at least one of a manner in which a corresponding metric in the set of metrics is to be collected, a data source from which the corresponding metric is at least one of collected or measured, or a data storage location in which the corresponding metric is to be stored.