Deep Dive

Operations and observability

Use SQIP health, usage, logs, alerts, and audit history together

SQIP separates live operational signals from long-term accountability. Use the operational views to investigate current behavior and Audit Logs to understand who changed what.

Dashboard

The Dashboard is the fastest health check. It summarizes:

  • Tenants you can access.
  • Shared cluster associations.
  • Active operations.
  • Messages produced.
  • Recent cluster operations.

Use it to identify an active change or missing resource, then open the relevant detailed page.

Monitoring

Monitoring shows the health and broker count of accessible clusters. Authorized operators can open bounded runtime logs for:

  • Broker
  • BookKeeper
  • Proxy
  • ZooKeeper

You can choose a 15-minute, 1-hour, 6-hour, or 24-hour range, filter by severity or source, search message text, and enable 10-second auto-refresh.

Note

Runtime log access is itself recorded in Audit Logs. Logs are bounded and sensitive values are redacted.

Build logs and connector logs

Use the log view that matches the resource:

Log typeUse it for
Build logsTenant and shared-cluster preparation
Runtime logsCurrent cluster component behavior
Connector logsA single connector's installation, reconciliation, and runtime events

Usage Metering

Usage Metering displays recorded totals for:

  • Messages produced.
  • Messages consumed.
  • Data ingested.
  • Data delivered.

Select Refresh to load the latest recorded values. Usage Metering is operational visibility; it is not an invoice or usage allowance.

Notifications

Open Notification to configure alert delivery for a tenant. The available channels are controlled by the platform administrator.

ChannelDestination input
EmailOne or more comma-separated recipient addresses
SlackA dedicated incoming webhook URL
Microsoft TeamsA Teams workflow or incoming webhook URL

Destinations are not displayed again after saving. Leave the destination blank when saving to keep the current value. Use Clear destination when you intentionally want to remove it.

Tip

Enable at least one tested destination for production namespaces so quota and usage alerts reach the operating team.

See Notifications for destination validation, platform controls, delivery retries, and troubleshooting.

Audit Logs

Audit Logs provide a tenant-scoped history of privileged and operational actions. Each event includes:

  • Action.
  • Tenant.
  • Resource type and identifier.
  • Actor.
  • Integrity and retention information.
  • Recorded time.

Search by action, actor, resource, or metadata. If you have export permission, select Export CSV to download the filtered history.

Incident workflow

When data appears delayed or missing:

  1. Check the connector or cluster status.
  2. Review the relevant connector, build, or runtime logs.
  3. Check Usage Metering to see whether production or consumption changed.
  4. Check namespace quota and active alerts.
  5. Review Audit Logs for recent configuration, access, or lifecycle changes.
  6. Correct the external issue or configuration, then restart or reconcile only the affected resource.

Record any correlation reference shown in an error before contacting support. It helps the support team locate the safe server-side details without exposing sensitive information in the browser.