Skip to content
StratumStratum Docs

List flow logs in a project.

GET
/v1/projects/{projectId}/network/flow-logs
Code sample: Shell / cURL
curl --request GET \
  --url https://stratum.example.com/v1/projects/example/network/flow-logs \
  --header 'Authorization: Bearer <token>'

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
projectId
required
string
/^p-[a-z0-9-]+$/

Query Parameters

Section titled “Query Parameters”
vpcId
string
/^vpc-[a-z0-9-]+$/

Responses

Section titled “Responses”

200

Section titled “200”

Flow logs.

Media typeapplication/json
object
items
required
Array<object>
object
id
required
string
/^fl-[a-z0-9-]+$/
projectId
required
string
resourceType
required
string
Allowed values: vpc subnet networkInterface
resourceId
required
string
vpcId
required

Derived from the captured resource.

string
/^vpc-[a-z0-9-]+$/
trafficType
required

Which verdicts get captured.

string
Allowed values: reject accept all
logGroupId
required

Destination log group (must pre-exist in the project).

string
state
required
string
Allowed values: active deleted
tags

AWS-shape resource tags. Freeform UTF-8 keys (1-128 bytes, no leading/trailing whitespace) mapped to freeform UTF-8 values (0-256 bytes). Max 50 tags per resource. Reserved prefixes (stratum.dev/, stratum.platform_health., stratum:, aws:) return 400 RESERVED_NAMESPACE on customer input. PATCH replaces the whole map..

object
<= 50 properties
key
additional properties
string
<= 256 characters
createdAt
required
string format: date-time
updatedAt
required
string format: date-time
deletedAt
string format: date-time
createdBy
string
nextPageToken
string
isTruncated

True when the server had more rows than it returned. The response is a valid prefix of the result, not the whole of it.

Without this flag a client at the server’s row ceiling receives a full page and no nextPageToken, which means “this is the complete set” — so data it never saw would be indistinguishable from data that does not exist.

It does not imply a cursor exists. These queries do not all sort on a total order, so a resumable token cannot be minted for them yet. The remedy is to narrow the request (a filter, or a tighter scope), not to page.

boolean

Example 

{
  "items": [
    {
      "resourceType": "vpc",
      "trafficType": "reject",
      "state": "active"
    }
  ]
}