Abstract:
Described technologies generate a data structure corresponding to values sequenced based on a plurality of timestamps associated with the values. The data structure can include a first section identifying a first timestamp associated with the plurality of timestamps and a number representing how many timestamps are associated with the plurality of timestamps, and a second section including at least a value linked to the first timestamp, and an additional value representing an encoding type associated with the second section. The data structure can be stored in computer-implemented storage.
Abstract:
By obtaining metadata for transactions submitted by a service to a log-first distributed database of a provider network, a metrics manager may determine database replica performance for those transactions and notify clients of potential performance issues. When an instance of the service submits a write transaction to the log-first distributed database, the transaction may include a host name and a timestamp for the submission of the transaction. At a later point in time, a write applier may obtain the transaction and apply it to a local database replica, along with an additional timestamp for the application of the transaction to the replica. A metrics manager may obtain the transaction timestamps from the replica and calculate a latency metric for the propagation of the transaction from the particular service instance/instance host to the replica. The latency metric may be stored or transmitted to an endpoint (e.g., a client or administrator).
Abstract:
A computing resource service receives a request to retrieve data, wherein fulfillment of the request involves retrieval of representations of the data from a number of datastores maintained by the service. The service transmits requests to individual datastores to retrieve the representations of the data. Before all responses to these requests are received, the service evaluates any received responses to determine whether a quorum has been reached with regard to the representations of the data. If so, the service consolidates the representations of the data and provides the consolidated data to fulfill the request.
Abstract:
A computing resource monitoring service receives a request to store a measurement for a metric associated with a computing resource. The request includes the measurement itself and metadata for the measurement, which specifies attributes of the measurement. Based at least in part on the metadata, the computing resource monitoring service generates a fully qualified metric identifier and, using the identifier, selects a logical partition for placement of the measurement. From the logical partition, the computing resource monitoring service transmits the measurement to an aggregator sub-system comprising one or more in-memory datastores. The computing resource monitoring service stores the measurement in an in-memory datastore within the aggregator sub-system.
Abstract:
A query including a time range can be received. The query can be processed to determine data associated with the time range of the query. Cached data can be analyzed to identify a first block of data including metadata identifying a first timestamp associated with the time range of the query. A communication can be generated to include the first timestamp associated with the first block of data. Based on the communication, a second block of data can be received with metadata identifying a second timestamp associated with the time range of the query. A query result can be generated to include the first block of data and the second block of data.
Abstract:
A computing resource monitoring service receives a request to store metrics data. The request includes the metrics data and a fully qualified metric identifier generated based at least in part on metadata included in an earlier request to store other metrics data for the same metric. The service uses the fully qualified metric identifier to identify an aggregator datastore for storing the metrics data. Once the service has identified the aggregator datastore, the service accesses the aggregator datastore to store the metrics data such that the metrics data and the other metrics data can be obtained in response to a request to obtain data for the metric, where the request includes the metadata.
Abstract:
A computing resource monitoring service receives a request to store metrics data. The request includes the metrics data and a fully qualified metric identifier generated based at least in part on metadata included in an earlier request to store other metrics data for the same metric. The service uses the fully qualified metric identifier to identify an aggregator datastore for storing the metrics data. Once the service has identified the aggregator datastore, the service accesses the aggregator datastore to store the metrics data such that the metrics data and the other metrics data can be obtained in response to a request to obtain data for the metric, where the request includes the metadata.
Abstract:
A computing resource monitoring service receives a request to store a measurement for a metric associated with a computing resource. The request includes the measurement itself and metadata for the measurement, which specifies attributes of the measurement. Based at least in part on the metadata, the computing resource monitoring service generates a fully qualified metric identifier and, using the identifier, selects a logical partition for placement of the measurement. From the logical partition, the computing resource monitoring service transmits the measurement to an aggregator sub-system comprising one or more in-memory datastores. The computing resource monitoring service stores the measurement in an in-memory datastore within the aggregator sub-system.
Abstract:
A computing resource monitoring service receives a request to retrieve measurement data for a metric. The computing resource monitoring service determines, based at least in part on information included in the request, one or more in-memory datastores where the measurement data is stored. If the information indicates that the computing resource monitoring service is to provide an authoritative subset of the measurement data, the computing resource monitoring service limits the data provided in response to the request to the authoritative subset of the measurement data. Otherwise, if the information does not specify this indication, the computing resource monitoring service will provide the measurement data that is available.