Monitoring & Logging

Monitoring and logging help customers and Reliable Insights understand platform activity, investigate issues, and review selected security-relevant events.

Reliable Insights records selected events to support traceability, operational review, and investigation of important platform activity. This can help administrators understand when key actions occurred, which workspace they related to, and which user or credential was involved.

Note:

Logging coverage, retention periods, customer-visible access, export options, and alerting capabilities may vary by deployment type, subscription, and customer requirements. Contact Reliable Insights for details specific to your environment.

Why monitoring and logging matters

Monitoring and logging are important for secure and reliable platform administration.

They help support questions such as:

• Was an API key created, rotated, revoked, or used?
• Was an API request accepted or rejected?
• Which workspace did an event relate to?
• Was a workspace-level permission or privilege changed?
• Was access attempted using an expired or revoked key?
• Did a datasource pull, feed update, or deployment run fail?
• Is an integration still active or no longer being used?

Having records for selected events makes platform activity easier to review, investigate, and support.

Security-relevant events

Reliable Insights records selected events that are important for platform security and access control.

These may include events related to:

• API key creation.
• API key rotation.
• API key revocation.
• Selected API key authentication events.
• Rejected use of expired or revoked API keys.
• Workspace privilege changes.
• Workspace-level access or permission activity where supported.

These records can help provide visibility into actions that may affect access to customer data, integrations, or workspace resources.

For more information about access controls, see RBAC & Permissions.

API key monitoring

API keys are a common source of operational and security risk because they allow programmatic access to platform resources.

Reliable Insights records selected API key lifecycle and authentication events to help support traceability.

For example, API key records may help identify:

• Which keys are actively being used.
• Whether selected authentication attempts have succeeded or failed.
• Whether an expired or revoked key has been used.
• When a key was created, rotated, or revoked.
• Whether an integration may still be using an old key.
• Whether unused keys should be revoked.

This information can help administrators review API key activity and decide when API keys should be rotated, revoked, or investigated.

Workspace activity and permissions

Workspace access controls protect resources such as datasets, experiments, datasources, feeds, deployments, API keys, and results.

Reliable Insights records selected workspace privilege events to help support traceability around workspace-level access and administrative activity.

This can help administrators understand changes that may affect who can access or manage workspace resources.

Customers should review workspace membership and administrative roles regularly, especially for production workspaces or workspaces containing sensitive operational data.

Operational monitoring

Monitoring is not only useful for security review. It also helps customers understand platform health and operational behaviour.

Operational monitoring may include reviewing:

• Datasource connection failures.
• Failed data pulls.
• Feed health and freshness.
• Pipeline alerts.
• Deployment failures.
• API authentication failures.
• Unexpected integration activity.
• Unused or stale API keys.
• Workspace access changes.

These signals can help customers identify issues early and respond before they affect production workflows.

Request context

Where available, security and operational event records may include request context such as:

• Timestamp.
• Workspace.
• User information.
• Event type.
• Request IP address.
• User agent.
• Success or failure status.
• Related API key or workspace privilege information.

The exact fields available may depend on the event type and product area.

Hosted platform monitoring

For the hosted Reliable Insights Platform, platform-level monitoring is primarily handled by Reliable Insights.

Customers using the hosted platform should focus on reviewing the product-level information available to them, such as workspace access, API key usage, datasource status, Pipeline alerts, deployment status, and integration activity.

Customers who require formal details about monitoring coverage, log retention, alerting, incident review, or operational reporting should contact Reliable Insights.

Customer responsibilities

Customers should regularly review access, integrations, and operational activity.

Recommended practices include:

• Review workspace members and roles regularly.
• Remove users who no longer require access.
• Use separate API keys for different integrations.
• Revoke API keys that are no longer needed.
• Rotate keys if they may have been exposed.
• Investigate unexpected API key activity.
• Review Datasource and Pipeline alerts.
• Monitor production deployments and integration health.
• Keep internal records of who owns each integration.
• Report suspicious or unexpected platform activity to Reliable Insights.

How this supports secure administration

Monitoring and logging help customers administer RI Platform securely and reliably by:

• Recording selected security-relevant events.
• Supporting review of API key lifecycle and usage activity.
• Helping trace workspace permission changes.
• Providing context for operational investigation.
• Making it easier to identify unused, expired, or revoked access.
• Supporting review of datasources, alerts, deployments, and integrations.
• Encouraging regular access review and credential hygiene.

These controls help make platform activity more visible, reviewable, and easier to investigate.