Skip to main content
IBM Quantum Platform

Activity tracking events for Qiskit Runtime

IBM Cloud® services, such as Qiskit Runtime, generate activity tracking events.

Activity tracking events report on activities that change the state of a service in IBM Cloud. You can use the events to investigate abnormal activity and critical actions and to comply with regulatory audit requirements.

You can use IBM Cloud Activity Tracker Event Routing, a platform service, to route auditing events in your account to destinations of your choice by configuring targets and routes that define where activity tracking events are sent. For more information, see About IBM Cloud Activity Tracker Events Routing.

You can use IBM Cloud Logs to visualize and alert on events that are generated in your account and routed by IBM Cloud Activity Tracker Event Routing to an IBM Cloud Logs instance.


Locations where activity tracking events are generated

Qiskit Runtime sends activity tracking events in the following regions:

  • Washington ("us-east")
  • Frankfurt ("eu-de")

Viewing activity tracking events for Qiskit Runtime

You can use IBM Cloud Logs to visualize and alert on events that are generated in your account and routed by IBM Cloud Activity Tracker Event Routing to an IBM Cloud Logs instance.

Launching IBM Cloud Logs from the Observability page

For information on launching the IBM Cloud Logs UI, see the Launching the UI in the IBM Cloud Logs documentation.

ActionTriggered by
quantum-computing.account-analytics-filters.readGet analytics filters (GET /v1/analytics/filters)
quantum-computing.account-analytics-usage.readGet usage analytics (GET /v1/analytics/usage)
quantum-computing.account-analytics-usage.readGet usage analytics grouped (GET /v1/analytics/usage_grouped)
quantum-computing.account-analytics-usage.readGet usage analytics grouped by date (GET /v1/analytics/usage_grouped_by_date)
quantum-computing.account-configuration.readGet account configuration (GET /v1/accounts/{id})
quantum-computing.device.readGet backend configuration (GET /v1/backends/{id}/configuration)
quantum-computing.device.readGet backend default settings (GET /v1/backends/{id}/defaults)
quantum-computing.device.readGet backend properties (GET /v1/backends/{id}/properties)
quantum-computing.device.readGet backend status (GET /v1/backends/{id}/status)
quantum-computing.device.readList your backends (GET /v1/backends)
quantum-computing.instance-usage.readGet instance usage (GET /v1/instances/usage)
quantum-computing.instance.configuration.readGet instance configuration (GET /v1/instances/configuration)
quantum-computing.instance.readGet current instance details (GET /v1/instance)
quantum-computing.job.cancelCancel a job (POST /v1/jobs/{id}/cancel)
quantum-computing.job.createRun a job (POST /v1/jobs)
quantum-computing.job.deleteDelete a job (DELETE /v1/jobs/{id})
quantum-computing.job.readGet job metrics (GET /v1/jobs/{id}/metrics)
quantum-computing.job.readGet job transpiled circuits (GET /v1/jobs/{id}/transpiled_circuits)
quantum-computing.job.readList job details (GET /v1/jobs/{id})
quantum-computing.job.readList job interim results (GET /v1/jobs/{id}/interim_results)
quantum-computing.job.readList job logs (GET /v1/jobs/{id}/logs)
quantum-computing.job.readList job results (GET /v1/jobs/{id}/results)
quantum-computing.job.readList jobs (GET /v1/jobs)
quantum-computing.job.readList tags (GET /v1/tags)
quantum-computing.session.createCreate a session (POST /v1/sessions)
quantum-computing.session.readGet a session (GET /v1/sessions/{id})
quantum-computing.session.updateClose job session (DELETE /v1/sessions/{id}/close)
quantum-computing.session.updateUpdate a session (PATCH /v1/sessions/{id})
quantum-computing.workload.listList user instance workloads (GET /v1/workloads)
Was this page helpful?
Report a bug or request content on GitHub.