Cloady Docs
API ReferenceEndpointsApplications

List the values a service's filters can take

Returns, for each filter field of a Monitor view, the values seen in the service's data within the range, most frequent first: log levels and routes from its logs, routes, methods and status classes from its ingress access log or its OpenTelemetry spans, and pages, devices, browsers, systems and countries from browser monitoring. `serviceName` is a compose service.

GET
/api/workspaces/{workspaceSlug}/apps/{appSlug}/services/{serviceName}/filters

Authorization

cloady
AuthorizationBearer <token>

Personal API token (cldy_…)

In: header

Path Parameters

workspaceSlug*string
appSlug*string
serviceName*string

Query Parameters

env?string

Value in

  • "production"
  • "preview"
  • "development"
region?string
range?string

How far back to look; the answer has 30 to 96 points across it

Default"1h"

Value in

  • "15m"
  • "1h"
  • "6h"
  • "24h"
  • "7d"
view*string

The Monitor view whose filter fields to list: logs has level and route; routes, endpoints and traces have route, method and status; frontend and sessions have route, device, browser, os and country

Value in

  • "frontend"
  • "sessions"
  • "routes"
  • "endpoints"
  • "traces"
  • "logs"

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/api/workspaces/string/apps/string/services/string/filters?view=frontend"
{  "fields": {    "property1": [      {        "value": "string",        "count": 0      }    ],    "property2": [      {        "value": "string",        "count": 0      }    ]  }}

Search a service's log history GET

Searches the service's logs over the range, kept for seven days, and returns the newest 300 matching lines with their level, service, pod and any trace id they mention, how many lines of each level matched in each of 48 buckets, and the LogQL that ran. `filter` takes `level` (error, warn, info, debug) and `route` (the `route` or `http.route` field of JSON or logfmt lines). With `scope=app` it searches every service of the app together. `serviceName` is a compose service.

Read browser monitoring GET

Returns the app's public browser key, the script URL and the hosts allowed to send beacons, from which the snippet is built, when the newest beacon arrived and the settings its snippet carries, and LCP p75 and active sessions over the range once pages send beacons. Browser monitoring is on exactly while the app's pages carry the snippet, and its settings (replay share, masking, conversion goal) live in the snippet itself, so turning it off means removing the snippet.