Forum Widgets
Latest Discussions
SRE Agent support multiple subscriptions
One of my Customer building 3 PoCs and they have few technical requirement that are unclear from the documents. It would be super helpful to get technical guidance and documentation supporting those requirements. Does one agent can access resources across all subscriptions connected to a Lighthouse tenant. Their current infrastructure setup, where a single Lighthouse tenant is used to manage multiple underlying tenants and their subscriptions. In this scenario if an SRE agent in one subscription could access resources across all these subscriptions. Is there an upper limit? Is there a upper limit for number of resource group an SRE agent can manage per subscription? Are there cost optimization best practices for scenarios like pre-recorded scripts or agent-level improvements for repetitive tasks in their case VM resizing? From billing standpoint does always-on agent connections incur charges even when no alerts are active? When handling multiple remediation tasks or queries, does the agent execute them sequentially or in parallel? Additionally, is there any control or configuration available for managing concurrency?
What are the recommended guardrails for...
Preventing the agent from making changes to any Azure resource? Companies who have heard stories about hallucinations, etc. believe that the agent is a threat their production systems potentially. From what I can tell, the agent can be given a managed identity that has limited rights to Azure resources. Read/list, etc. Without guardrails, adoption of this tech will be difficult in some environments. "But the hallucinations..." I'm not sure it's a great idea to let an agent make changes to a production system... or even suggest doing it "for" the benefit of the on-call. It's too easy to screw up. What is the guidance here? Managed identity with RBAC?
