We’re excited to launch this space for collaboration around the SRE Agent, a key tool in our mission to improve service reliability and operational excellence.
- 🐛 Report bugs encountered while using the SRE Agent
- 💡 Request features that would improve usability or functionality
- ❓ Share challenges or feedback related to using the product
- 🤝 Engage with the team and community to help shape the future of the SRE Agent
Note
This repo is not intended for integration-related issues. For those, please use the appropriate internal or partner support channels.
To help us keep things organized and productive, please follow these simple rules:
- Be descriptive: Include steps to reproduce, logs, screenshots, and thread ID where applicable.
- Use labels: Tag your issue appropriately (bug, feature-request, usability, etc.) to help with triage.
- Avoid duplicates: Search existing issues before creating a new one.
- Stay constructive: We welcome feedback, but please keep it respectful and focused.
- No personal data: Please do not include any personally identifiable information (PII) in your issue.
Your direct chat interaction or incident is tracked as a thread in SRE Agent. Including the Thread ID in your GitHub issue helps us investigate quickly and accurately. A thread ID is a hex string like 50f7521d-dfee-487e-9188-5abdc8adde91.
Get thread ID for threads under "Activities" view
Get thread ID for threads under Incident Management view
step 1:
When creating a new issue, please use the following format:
Issue Description Briefly describe the problem or request.
Agent Name name of Agent
Subscription ID subscription in which agent is deployed
Region Region where agent is deployed
Resource group For Agent deployment related issues, provide the resource group in which it was created
Thread ID Paste the thread ID from the SRE Agent portal (e.g., 50f7521d-dfee-487e-9188-5abdc8adde91)
Steps to Reproduce
- Describe the action you took
- Mention the resource or Azure service (if involved)
- Describe what you expected vs. what happened
- include error messages experienced by you in Incident or chat threads or ARM deployment error details or HTTP status codes
Expected Behavior What should happen?
Actual Behavior What actually happened
