Public Safety and Security Metrics

Use Public Safety and Security metrics to observe API traffic, service capacity signals, and active Oracle Radio WebSocket connections.

Public Safety and Security customer metrics use the oci_pss namespace. Use Metrics Explorer to query these metrics and use OCI Alarms to notify operators when a metric query meets a defined condition.

Metric Policy

Ask an IAM administrator to let your user group list and query Public Safety and Security metrics in the compartment containing the Public Safety and Security resource. This policy limits metric access to the oci_pss namespace:

Allow group <group-name> to read metrics in compartment <compartment-name> where target.metrics.namespace = 'oci_pss'

Replace the group and compartment names. This applies to Console, CLI, and API metric queries; it doesn't grant alarm creation or Public Safety and Security instance management. For the related grants, see the policy examples. For more information about user authorizations for monitoring, see IAM Policies. Administrators: For common policies that give groups access to metrics, see Metric Access for Groups.

Metric Groups

The following groups summarize the available metrics and the customer questions they help answer.

Group	Metrics	Customer question
API traffic	`ApiRequestCount`, `Latency`, `BytesSent`, and `BytesReceived`	How much traffic does Public Safety and Security receive, and what latency and payload volume does the service observe?
Capacity	`CPUsAllocated_max` and `StorageSpaceUsed_max`	What maximum CPU allocation and storage usage does the managed backend report?
Oracle Radio connections	`ActiveWebSocketConnections`	How many Oracle Radio WebSocket connections are currently established?

Metric Data Protection

Public Safety and Security metrics and dimensions don't include PII, CJIS or other justice data, 911 call content, dispatch details, incident or case IDs, evidence IDs, video content, radio communications, device IDs, request IDs, or request payload content.

Note

Customer metrics in oci_pss are different from billing meters and from internal infrastructure or Oracle Radio application telemetry.

Viewing Metrics

Use the Console, CLI, or API to view customer-facing metrics in the oci_pss namespace. All three methods require the metric policy.

Ensure that you have permission to read metrics in the compartment that contains the Public Safety and Security resource.

For ActiveWebSocketConnections, use Sum with a one-minute interval to total the current connection gauges from the Radio replicas. Don't use Rate or a multi-minute Sum for this metric.
1. In the OCI Console, open Metrics Explorer.
2. Select the compartment that contains the Public Safety and Security resources.
3. Select the Public Safety and Security metric namespace, oci_pss.
4. Select a metric name and the recommended statistic for that metric.
  Use the metric definitions later on this page to select the statistic, interval, and supported dimensions.
5. Apply the available resourceId, operation, resourceType, resourceName, databaseId, or deploymentName dimensions as appropriate for the metric.
6. Select the recommended interval for the metric and adjust the time range for the question that you want to investigate.
  API traffic and connection metrics use one-minute intervals, CPUsAllocated_max uses five minutes, and StorageSpaceUsed_max uses one hour.
The chart displays the metric data available for the selected interval, statistic, and dimensions.
Use the following command to list metrics in the oci_pss namespace. Supply additional query inputs as needed.
```
oci monitoring metric list --compartment-id <compartment-OCID> --namespace oci_pss [...]
```
Run the OCI Monitoring ListMetrics operation. Set the required compartmentId to the compartment OCID and set namespace to oci_pss.

Metrics Reference

Review the customer-facing Public Safety and Security metrics in the oci_pss namespace.

Common Details

Public Safety and Security publishes Radio request metrics when a classified request completes, connection gauges at aligned one-minute boundaries, and API Gateway or managed-database source observations at their native intervals. Use the dimensions available for each metric to scope a query to the relevant Public Safety and Security resource and customer-visible HTTP operation.

Dimension	Meaning
`resourceId`	The identifier of the Public Safety and Security service resource represented by the metric.
`resourceName`	The display name of the Public Safety and Security resource for capacity metrics.
`operation`	The HTTP operation: `GET`, `POST`, `PUT`, `PATCH`, or `DELETE`. Generated `HEAD` traffic is included with `GET`.
`resourceType`	The Public Safety and Security service domain represented by the metric. Radio API and connection metrics use `radio`.
`databaseId`	The managed database resource associated with a Public Safety and Security capacity metric.
`deploymentName`	The Public Safety and Security deployment that publishes an active-connection gauge.

Metric Definitions

The following table describes each metric, its dimensions, statistic, reporting interval, and unit.

Metric and display name	Dimensions	Statistic and interval	Unit	Description
`ApiRequestCount` API Request Count	`resourceId`, `operation`, `resourceType`	`Sum`, 1 minute	Count	Number of incoming client API requests received by Public Safety and Security.
`Latency` Latency	`resourceId`, `operation`, `resourceType`	`Mean`, `P95`, or `P99`; 1 minute	Milliseconds	Service-observed time from request receipt to response completion.
`BytesSent` Bytes Sent	`resourceId`, `operation`, `resourceType`	`Sum`, 1 minute	Bytes	Response bytes reported by OCI API Gateway for the Radio REST route and HTTP operation.
`BytesReceived` Bytes Received	`resourceId`, `operation`, `resourceType`	`Sum`, 1 minute	Bytes	Request bytes reported by OCI API Gateway for the Radio REST route and HTTP operation.
`CPUsAllocated_max` Max CPUs Allocated	`resourceId`, `resourceName`, `databaseId`	`Max`, 5 minutes	Count	Latest valid maximum CPU allocation reported by the managed database for a closed five-minute source window.
`StorageSpaceUsed_max` Max Storage Space Used	`resourceId`, `resourceName`, `databaseId`	`Max`, 1 hour	GB	Latest valid storage usage reported by the managed database's hourly source metric.
`ActiveWebSocketConnections` Active WebSocket Connections	`resourceId`, `resourceType`, `deploymentName`	`Sum`, 1 minute	Count	Current number of established Oracle Radio WebSocket connections. Each Radio replica publishes its current gauge, and a one-minute Sum displays the total across replicas.

Aggregation Guidance

Multiple publishers can report the same managed database sample. Use Max for CPUsAllocated_max and StorageSpaceUsed_max so duplicate samples don't change the displayed value.

The API Gateway and managed-database metrics preserve the selected source timestamp. If a closed source window contains no valid observation, Public Safety and Security doesn't publish a zero or reuse an older observation with a new timestamp.

ActiveWebSocketConnections is a current-count gauge, not a cumulative connection counter. Use a one-minute Sum to combine Radio replica gauges. Don't use Rate or a multi-minute Sum.

Oracle Cloud Infrastructure Documentation