-
Notifications
You must be signed in to change notification settings - Fork 0
Support
alonsalasi edited this page Aug 23, 2026
·
1 revision
| Channel | Use for |
|---|---|
| GitHub Issues — github.com/kubeopsai/k8s-telemetry-mcp/issues | Bug reports, feature requests, public questions |
| Email — kubeopsai@gmail.com | Billing questions, private issues, Enterprise support |
| Tier | First Response | Target Resolution |
|---|---|---|
| Standard ($29/mo) | 5 business days | Best effort |
| Professional ($99/mo) | 2 business days | 5 business days |
| Enterprise ($299/mo) | 1 business day | 3 business days |
Business hours are Monday–Friday, 09:00–18:00 CET (UTC+1 / UTC+2 during summer).
Response times apply to issues reported via email at kubeopsai@gmail.com. GitHub Issues are monitored on the same schedule but are not covered by the SLA.
Note: This is an independently operated product. SLA response times reflect a single-engineer team. Complex issues may take longer to resolve — you will always receive an acknowledgement within the stated first-response window and regular updates until the issue is closed.
- Installation and configuration assistance
- Bugs in the MCP server, tools, or Helm chart
- Unexpected tool errors or incorrect data returned
- AWS Marketplace billing and subscription questions
- Your Kubernetes cluster configuration or infrastructure
- Loki, Prometheus, Tempo, Datadog, or CloudWatch setup and administration
- Issues caused by unsupported Kubernetes versions (< 1.24)
- Custom modifications to the Helm chart or server code
When emailing or opening a GitHub issue, please include:
- Server version (
kubectl logs -n monitoring -l app.kubernetes.io/name=k8s-telemetry-mcp | head -5) - Which tool failed and what prompt triggered it
- The error message returned
- Your backend (Loki/Prometheus/Tempo, Datadog, or CloudWatch)
- Your subscription tier
Feature requests are welcome via GitHub Issues. Enterprise customers can email feature requests directly and they will be prioritised in the roadmap.