Abstract: A system provides for tail-based sampling of span data at the trace level. The system may include a circuitry, such as one or more servers, that execute applications, agents, and a trace manager. The agents generate span data of operations performed by the applications. The trace manager receives the span data from the agents, and groups the operations defined by the span data into traces. The trace manager determines a selected subset of the traces for span data sampling and an unselected subset of the traces excluded from the span data sampling by comparing one or more trace characteristics of the traces with one or more trace criteria. The trace manager discards unselected span data of the unselected subset of the traces and provide selected span data of the selected subset of the traces to a monitoring system via a network.

Abstract: A system provides for tail-based sampling of span data at the trace level. The system may include a circuitry, such as one or more servers, that execute applications, agents, and a trace manager. The agents generate span data of operations performed by the applications. The trace manager receives the span data from the agents, and groups the operations defined by the span data into traces. The trace manager determines a selected subset of the traces for span data sampling and an unselected subset of the traces excluded from the span data sampling by comparing one or more trace characteristics of the traces with one or more trace criteria. The trace manager discards unselected span data of the unselected subset of the traces and provide selected span data of the selected subset of the traces to a monitoring system via a network.

Abstract: A monitoring system receives information from agents that monitors (e.g., unprivileged) containers, or applications in containers, executing across hosts to generate aggregated state information on a per-host basis. The system receives state information for each container, boot identifiers associated with the hosts of the container, and container identifiers. State information includes data describing the state of a container, or an application executing in the container. The boot identifier includes an identifier for a boot session of the host. The container identifier uniquely identifies each container. The monitoring system compares boot identifiers to determine containers that are co-located. If containers share a boot identifier, the monitoring system determines that the containers are co-located on the host that generated the boot identifier.

Abstract: A monitoring system receives information from agents that monitors (e.g., unprivileged) containers, or applications in containers, executing across hosts to generate aggregated state information on a per-host basis. The system receives state information for each container, boot identifiers associated with the hosts of the container, and container identifiers. State information includes data describing the state of a container, or an application executing in the container. The boot identifier includes an identifier for a boot session of the host. The container identifier uniquely identifies each container. The monitoring system compares boot identifiers to determine containers that are co-located. If containers share a boot identifier, the monitoring system determines that the containers are co-located on the host that generated the boot identifier.