Temporal

the temporal https //temporal io/ integration gives resolve ai read only access to your workflows, activities, task queues, and schedules during alert investigations how it works resolve runs read only temporal cli https //docs temporal io/cli commands from the satellite against your temporal frontend over grpc no data leaves your environment except the command results returned to resolve, and only read operations are permitted resolve can list and describe workflows, task queues, schedules, and namespaces show workflow event history count workflows matching a query get a running workflow's stack trace write operations (such as terminate , cancel , signal , reset , and delete ) are currently not supported if you wish to allow resolve ai to take write actions on temporal, please contact help\@resolve ai mailto\ help\@resolve ai 1\ prerequisites before connecting, make sure you have the resolve satellite https //docs resolve ai/resolve satellite installed in the cluster (or network) that can reach your temporal frontend the temporal frontend grpc address , resolvable from inside the satellite (for example temporal frontend temporal svc cluster local 7233 ) the namespaces you want resolve to access no api token or key is required tls is managed by the satellite 2\ connect temporal add the integration to your satellite configuration integrations yaml integrations temporalintegration type temporal create true connection address \<temporal frontend grpc address> # e g temporal frontend temporal svc cluster local 7233 namespaces \ \<namespace> # the first entry is the default namespace \# \<another namespace> # add more namespaces as needed field required description address yes temporal frontend grpc address, resolvable from inside the satellite's kubernetes cluster namespaces yes (min 1) namespaces resolve may target the first entry is treated as the default apply the updated configuration and restart the resolve satellite to pick up the new integration 3\ verify the connection resolve runs a two step health check liveness – confirms the temporal cli is available on the satellite connectivity – confirms the satellite can reach the temporal frontend for the first configured namespace once both pass, the integration shows as healthy in the resolve ui troubleshooting symptom likely cause resolution health check fails at the liveness step temporal cli not available on the satellite ensure your satellite image includes the temporal cli health check fails at the connectivity step satellite cannot reach the temporal frontend verify address is correct and that network policies allow grpc traffic from the satellite "namespace not allowed" error a namespace was requested that isn't in your config add the namespace to the namespaces list and restart the satellite "only read only commands allowed" a write operation was attempted expected — the integration is read only by design