Admin Console

SRE Agent Admin

Manage SRE mappings on top of the shared Release Manager service catalog, keep local repo folders aligned, and expose the webhook endpoints used for incident intake.

Google Chat intake Azure Alert intake Shared repo catalog

Mapped services 1 SRE-ready mappings currently configured.

Shared catalog YAML Using local file-backed mappings.

Connections

Chat and alert settings

These remain lightweight and host-local, while service identity and repository metadata come from the shared catalog when configured.

Public Base URL Google Chat App Name Default Google Chat Webhook URL Azure Secure Webhook Object ID Allowed Google Chat Spaces Allowed Azure Subscriptions Azure Notes

Intake Endpoints

Connect external systems

Use these exact URLs when wiring Google Chat and Azure Monitor into the SRE investigation flow.

Google Chat App HTTP Endpoint

https://sreagent.disprz.com/ingest/google-chat/events

Point your Google Chat app event delivery here.

Azure Action Group Webhook

https://sreagent.disprz.com/ingest/azure/action-group

Use this endpoint from Azure Monitor action groups or secure webhook integrations.

Mapping Source

The app is currently running without the shared Release Manager database, so mappings are coming from the local registry file.

Service Mappings

Repository and local folder mappings

Each row represents an SRE mapping for one service/environment pair, with the local repository path used during evidence collection and code analysis.

Add Mapping

Service	Repository	Project	Environment	Local Folder	Status	Actions
checkout-api 1 resources · 1 databases	checkout-api	-	prod	`D:\repos\checkout-api`	Mapping enabled Shared service active	Edit