Per funzionalità simili a Amazon Timestream for, prendi in considerazione Amazon Timestream LiveAnalytics per InfluxDB. Offre un'acquisizione semplificata dei dati e tempi di risposta alle query di una sola cifra di millisecondi per analisi in tempo reale. [Scopri](https://docs.aws.amazon.com//timestream/latest/developerguide/timestream-for-influxdb.html) di più qui.

Le traduzioni sono generate tramite traduzione automatica. In caso di conflitto tra il contenuto di una traduzione e la versione originale in Inglese, quest'ultima prevarrà.

# Interrogazioni con funzioni di serie temporali
<a name="sample-queries.devops-scenarios"></a>

**Topics**
+ [Set di dati e interrogazioni di esempio](#sample-queries.devops-scenarios.example)

## Set di dati e interrogazioni di esempio
<a name="sample-queries.devops-scenarios.example"></a>

È possibile utilizzare Timestream per LiveAnalytics comprendere e migliorare le prestazioni e la disponibilità dei servizi e delle applicazioni. Di seguito è riportato un esempio di tabella e delle query di esempio eseguite su tale tabella. 

La tabella `ec2_metrics` memorizza i dati di telemetria, come l'utilizzo della CPU e altre metriche delle istanze EC2. È possibile visualizzare la tabella riportata di seguito.


| Orario | region | az | Hostname (Nome host) | measure\$1name | measure\$1value::double | measure\$1value::bigint | 
| --- | --- | --- | --- | --- | --- | --- | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  cpu\$1utilization  |  35.1  |  null  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  memory\$1utilization  |  5.3  |  null  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  network\$1bytes\$1in  |  null  |  1.500  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  network\$1bytes\$1out  |  null  |  6.700  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  cpu\$1utilization  |  38,5  |  null  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  memory\$1utilization  |  58,4  |  null  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  network\$1bytes\$1in  |  null  |  23.000  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  network\$1bytes\$1out  |  null  |  12.000  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  cpu\$1utilization  |  45.0  |  null  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  memory\$1utilization  |  65,8  |  null  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  network\$1bytes\$1in  |  null  |  15.000  | 
|  2019-12-04 19:00:00.000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  network\$1bytes\$1out  |  null  |  836.000  | 
|  2019-12-04 19:00:05.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  cpu\$1utilization  |  55.2  |  null  | 
|  2019-12-04 19:00:05.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  memory\$1utilization  |  75.0  |  null  | 
|  2019-12-04 19:00:05.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  network\$1bytes\$1in  |  null  |  1.245  | 
|  2019-12-04 19:00:05.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  network\$1bytes\$1out  |  null  |  68.432  | 
|  2019-12-04 19:00:08000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  cpu\$1utilization  |  65,6  |  null  | 
|  2019-12-04 19:00:08000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  memory\$1utilization  |  85,3  |  null  | 
|  2019-12-04 19:00:08000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  network\$1bytes\$1in  |  null  |  1.245  | 
|  2019-12-04 19:00:08000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  network\$1bytes\$1out  |  null  |  68.432  | 
|  2019-12-04 19:00:20000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  cpu\$1utilization  |  12.1  |  null  | 
|  2019-12-04 19:00:20000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  memory\$1utilization  |  32,0  |  null  | 
|  2019-12-04 19:00:20000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  network\$1bytes\$1in  |  null  |  1.400  | 
|  2019-12-04 19:00:20000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  network\$1bytes\$1out  |  null  |  345  | 
|  2019-12-04 19:00:10.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  cpu\$1utilization  |  15.3  |  null  | 
|  2019-12-04 19:00:10.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  memory\$1utilization  |  35,4  |  null  | 
|  2019-12-04 19:00:10.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  network\$1bytes\$1in  |  null  |  23  | 
|  2019-12-04 19:00:10.000 000000  |  us-east-1  |  us-east-1a  |  front-end 01  |  network\$1bytes\$1out  |  null  |  0  | 
|  2019-12-04 19:00:16.000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  cpu\$1utilization  |  44.0  |  null  | 
|  2019-12-04 19:00:16.000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  memory\$1utilization  |  64.2  |  null  | 
|  2019-12-04 19:00:16000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  network\$1bytes\$1in  |  null  |  1.450  | 
|  2019-12-04 19:00:16000 000000  |  us-east-1  |  us-east-1b  |  front-end 02  |  network\$1bytes\$1out  |  null  |  200  | 
|  2019-12-04 19:00:40.000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  cpu\$1utilization  |  6.4  |  null  | 
|  2019-12-04 19:00:40,000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  memory\$1utilization  |  86,3  |  null  | 
|  2019-12-04 19:00:40,000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  network\$1bytes\$1in  |  null  |  300  | 
|  2019-12-04 19:00:40.000 000000  |  us-east-1  |  us-east-1c  |  front-end 03  |  network\$1bytes\$1out  |  null  |  423  | 

Trova l'utilizzo medio della CPU p90, p95 e p99 per uno specifico host EC2 nelle ultime 2 ore:

```
SELECT region, az, hostname, BIN(time, 15s) AS binned_timestamp,
    ROUND(AVG(measure_value::double), 2) AS avg_cpu_utilization,
    ROUND(APPROX_PERCENTILE(measure_value::double, 0.9), 2) AS p90_cpu_utilization,
    ROUND(APPROX_PERCENTILE(measure_value::double, 0.95), 2) AS p95_cpu_utilization,
    ROUND(APPROX_PERCENTILE(measure_value::double, 0.99), 2) AS p99_cpu_utilization
FROM "sampleDB".DevOps
WHERE measure_name = 'cpu_utilization'
    AND hostname = 'host-Hovjv'
    AND time > ago(2h)
GROUP BY region, hostname, az, BIN(time, 15s)
ORDER BY binned_timestamp ASC
```

Identifica gli host EC2 con un utilizzo della CPU superiore del 10% o più rispetto all'utilizzo medio della CPU dell'intera flotta nelle ultime 2 ore:

```
WITH avg_fleet_utilization AS (
    SELECT COUNT(DISTINCT hostname) AS total_host_count, AVG(measure_value::double) AS fleet_avg_cpu_utilization
    FROM "sampleDB".DevOps
    WHERE measure_name = 'cpu_utilization'
        AND time > ago(2h)
), avg_per_host_cpu AS (
    SELECT region, az, hostname, AVG(measure_value::double) AS avg_cpu_utilization
    FROM "sampleDB".DevOps
    WHERE measure_name = 'cpu_utilization'
        AND time > ago(2h)
    GROUP BY region, az, hostname
)
SELECT region, az, hostname, avg_cpu_utilization, fleet_avg_cpu_utilization
FROM avg_fleet_utilization, avg_per_host_cpu
WHERE avg_cpu_utilization > 1.1 * fleet_avg_cpu_utilization
ORDER BY avg_cpu_utilization DESC
```

Trova l'utilizzo medio della CPU suddiviso a intervalli di 30 secondi per uno specifico host EC2 nelle ultime 2 ore:

```
SELECT BIN(time, 30s) AS binned_timestamp, ROUND(AVG(measure_value::double), 2) AS avg_cpu_utilization
FROM "sampleDB".DevOps
WHERE measure_name = 'cpu_utilization'
    AND hostname = 'host-Hovjv'
    AND time > ago(2h)
GROUP BY hostname, BIN(time, 30s)
ORDER BY binned_timestamp ASC
```

Trova l'utilizzo medio della CPU eseguito a intervalli di 30 secondi per uno specifico host EC2 nelle ultime 2 ore, inserendo i valori mancanti utilizzando l'interpolazione lineare:

```
WITH binned_timeseries AS (
    SELECT hostname, BIN(time, 30s) AS binned_timestamp, ROUND(AVG(measure_value::double), 2) AS avg_cpu_utilization
    FROM "sampleDB".DevOps
    WHERE measure_name = 'cpu_utilization'
        AND hostname = 'host-Hovjv'
        AND time > ago(2h)
    GROUP BY hostname, BIN(time, 30s)
), interpolated_timeseries AS (
    SELECT hostname,
        INTERPOLATE_LINEAR(
            CREATE_TIME_SERIES(binned_timestamp, avg_cpu_utilization),
                SEQUENCE(min(binned_timestamp), max(binned_timestamp), 15s)) AS interpolated_avg_cpu_utilization
    FROM binned_timeseries
    GROUP BY hostname
)
SELECT time, ROUND(value, 2) AS interpolated_cpu
FROM interpolated_timeseries
CROSS JOIN UNNEST(interpolated_avg_cpu_utilization)
```

Trova l'utilizzo medio della CPU eseguito a intervalli di 30 secondi per uno specifico host EC2 nelle ultime 2 ore, inserendo i valori mancanti utilizzando l'interpolazione basata sull'ultima osservazione riportata:

```
WITH binned_timeseries AS (
    SELECT hostname, BIN(time, 30s) AS binned_timestamp, ROUND(AVG(measure_value::double), 2) AS avg_cpu_utilization
    FROM "sampleDB".DevOps
    WHERE measure_name = 'cpu_utilization'
        AND hostname = 'host-Hovjv'
        AND time > ago(2h)
    GROUP BY hostname, BIN(time, 30s)
), interpolated_timeseries AS (
    SELECT hostname,
        INTERPOLATE_LOCF(
            CREATE_TIME_SERIES(binned_timestamp, avg_cpu_utilization),
                SEQUENCE(min(binned_timestamp), max(binned_timestamp), 15s)) AS interpolated_avg_cpu_utilization
    FROM binned_timeseries
    GROUP BY hostname
)
SELECT time, ROUND(value, 2) AS interpolated_cpu
FROM interpolated_timeseries
CROSS JOIN UNNEST(interpolated_avg_cpu_utilization)
```