---
title: Timeseries
summary: The Observability Timeseries API allows users to retrieve observability data collected by Fastly for the Log Explorer & Insights product and for the Sustainability dashboard as time series.
url: https://www.fastly.com/documentation/reference/api/observability/timeseries
---

The Observability Timeseries API allows users to retrieve observability data collected by Fastly for the Log Explorer & Insights product and for the Sustainability dashboard as time series.

## Data model

| Field | Type | Description |
|-------|------|-------------|
| `dimensions` | object | An object containing each requested dimension and time as properties. |
| `values` | object | An object containing each requested series as a property. |

## Data model

| Field | Type | Description |
|-------|------|-------------|
| `from` | string | Start time for the query as supplied in the request. |
| `granularity` | string | The granularity of the time buckets in the response. |
| `limit` | string | Maximum number of results returned in the request. |
| `to` | string | End time for the query as supplied in the request. |

## API endpoints

### Retrieve observability data as a time series

**GET** `/observability/timeseries`

Retrieves observability data as a time series.

**Parameters:**

| Name | Type | In | Required | Description |
|------|------|----|---------|--------------|
| `dimensions` | string | query | No | Comma-separated list of grouping dimensions. Supported values are <code>source</code> specific. No grouping dimensions implies aggregation by time only. |
| `filter` | string | query | No | Filter parameters are query string components that let you narrow down API responses by including only records that match specific criteria. Filter parameters take the form <code>filter[&lt;field&gt;][&lt;op&gt;]=&lt;value&gt;</code> or <code>filter[&lt;field&gt;]=&lt;value&gt;</code>. For example, <code>filter[response_time][gte]=0.5</code> would filter for response time values greater than or equal to 0.5 seconds. Multiple filter expressions can be combined. The filters will be combined with a logical AND operator so that the logs returned match all supplied filters. Supported filter fields are <code>source</code> specific. Supported filter operators include <code>ends-with</code> (applicable to string values), <code>in</code> and <code>not_in</code> (applicable to lists of string and numeric values); as well as <code>gt</code>, <code>gte</code>, <code>lt</code>, and <code>lte</code> (applicable to numeric values). |
| `from` | string | query | Yes | Specifies the inclusive start time of the data to be queried. Must be in valid RFC 3339 format. |
| `granularity` | string | query | Yes | The duration of each interval in the time series. Supported values are <code>source</code> specific. |
| `series` | string | query | Yes | Comma-separated list of the data series to be computed for each time bucket and combination of dimensions. Series definitions take the form <code>&lt;function&gt;[&lt;field&gt;]</code>. Supported fields are <code>source</code> specific. For example, <code>series=avg[response_time]</code> will compute the average response time. At least one series is required. |
| `source` | string | query | Yes | The source of the data for the time series. |
| `to` | string | query | Yes | Specifies the exclusive end time of the data to be queried. Must be in valid RFC 3339 format. |