Log Source Alarms

Overview

Use these API operations to manage drop-off alarms on log sources in Panther. These endpoints are designed for Terraform and other infrastructure-as-code workflows; see Managing Log Source Alarms with Terraform.

Only the SOURCE_NO_DATA alarm type is user-configurable and exposed via these endpoints. The other alarm types visible in the Panther Console (permissions checks, classification failures, log-processing errors, scanning errors) are system-managed.

Required permissions

  • For GET operations, your API token must have the View Log Sources permission.

  • For PUT and DELETE operations, your API token must have the Manage Log Sources permission.

Operations

get log source alarm

get

Get a specific alarm for a log source

Authorizations
X-API-KeystringRequired
Path parameters
sourceIdstring · uuidRequired

The ID of the log source

typestring · enumRequired

The alarm type. Only SOURCE_NO_DATA is exposed.

Possible values:
Responses
200

OK response.

application/json
minutesThresholdinteger · int32Optional

The no-data evaluation period in minutes.

statestring · enumOptional

The current CloudWatch state of the alarm

Possible values:
typestring · enumRequired

The alarm type

Possible values:
get
/log-source-alarms/{sourceId}/{type}

put log source alarm

put

Create or update the drop-off threshold for a log source. Only the SOURCE_NO_DATA alarm type is user-configurable. Not supported for cloud-security sources (returns 400).

Authorizations
X-API-KeystringRequired
Path parameters
sourceIdstring · uuidRequired

The ID of the log source

typestring · enumRequired

The alarm type. Only SOURCE_NO_DATA is supported on PUT.

Possible values:
Body
minutesThresholdinteger · int32Required

The no-data evaluation period in minutes. Minimum 15, maximum 43200 (30 days).

Responses
200

OK response.

application/json
minutesThresholdinteger · int32Required

The configured no-data evaluation period in minutes

typestring · enumRequired

The alarm type

Possible values:
put
/log-source-alarms/{sourceId}/{type}

delete log source alarm

delete

Delete the drop-off alarm for a log source. Idempotent: returns 204 even if no alarm exists.

Authorizations
X-API-KeystringRequired
Path parameters
sourceIdstring · uuidRequired

The ID of the log source

typestring · enumRequired

The alarm type. Only SOURCE_NO_DATA is supported on DELETE.

Possible values:
Responses
delete
/log-source-alarms/{sourceId}/{type}

No content

Last updated

Was this helpful?