Sold by: SAQTEK US CORP
Deployed on AWS
PodWatcher automatically identifies non-running objects within your cluster, instantly surfacing the relevant error codes and actionable troubleshooting commands. By providing rapid diagnostics and cross-cloud compatibility, PodWatcher reduces Mean Time to Recovery (MTTR) and simplifies management across diverse EKS and self-managed Kubernetes environments. This product is a buyer-deployed container image, giving you full control within your own VPC.
Overview
Optimized for Channel Partners and Managed Service Providers (MSPs) seeking to automate Level 1 support diagnostics across multi-tenant environments.
PodWatcher is a lightweight, high-efficiency Kubernetes monitoring agent designed to eliminate the manual "toil" of debugging failed workloads. While traditional observability platforms tell you that something is wrong, PodWatcher immediately tells you why it failed and how to fix it. By bridging the gap between raw cluster events and actionable SRE intelligence, PodWatcher empowers teams to maintain high-availability standards without the overhead of complex, resource-heavy monitoring suites.
KEY FEATURES & SRE BENEFITS
Instant Error Mapping: Using a sophisticated internal exit-code mapping engine (covering OOMKilled, SegFaults, SIGTERMs, and more), PodWatcher translates cryptic Kubernetes states into human-readable descriptions and pre-formatted kubectl troubleshooting commands.
Reduced MTTR (Mean Time to Recovery): By surfacing the exact cause of failure and the last 15 lines of logs directly in Slack or Microsoft Teams, PodWatcher removes the need for manual context-switching, cutting recovery times from minutes to seconds.
SLA & SLO Protection: Maintain your Service Level Agreements (SLAs) by catching "Unhealthy" states before they impact end-users. PodWatcher tracks restarts and waiting states in real-time to help you defend your Error Budgets.
Minimal Operational Cost: Unlike "sidecar" heavy solutions, PodWatcher is a low-overhead, single-deployment agent. It features advanced namespace filtering and pattern-recognition to prevent "alert fatigue" and minimize compute costs.
TECHNICAL INTEGRATION
Native Compatibility: Built for modern Kubernetes environments including Amazon EKS, self-managed clusters, and hybrid-cloud deployments.
Notification Channels: Native Webhook support for instant alerts in Slack and Microsoft Teams.
Observability: Includes built-in health probes (/healthz) and Prometheus-ready logging for seamless cluster integration.
Zero-Trust Security: Runs as a buyer-managed container within your own VPC. Your diagnostic data and logs never leave your security boundary.
Highlights
- Instant Root Cause Analysis automatically maps cryptic Kubernetes exit codes (like OOMKilled, SegFault, or SIGTERM) to human-readable descriptions. It provides the exact kubectl troubleshooting commands needed to resolve the issue. Predictable, flat-rate pricing: One license covers your entire cluster, whether you are running 10 nodes or 1,000. No per-node fees, no hidden scaling costs.
- Direct SRE Notification Integration Reduces MTTR by surfacing failed pod states and the last 15 lines of relevant error logs (if available) directly into Slack or Microsoft Teams, eliminating the need for manual log diving and context switching.
- Privacy-First, Buyer-Managed Deployment Engineered as a lightweight container that runs entirely within your own VPC or EKS cluster; your diagnostic data and logs never leave your security boundary, ensuring zero data leakage and minimal compute overhead.
Details
Sold by
Categories
Delivery method
Supported services
Delivery option
PodWatcher Standard Agent
PodWatcher Standard Deployment
Latest version
Operating system
Linux
Deployed on AWS
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Description | Cost/month |
|---|---|---|
PodWatcher Standard Cluster License | A flat-rate, "fire and forget" license for one (1) Kubernetes cluster. This license covers all worker nodes and pods within the specified cluster, regardless of scale. Includes automated diagnostic mapping for exit codes (OOMKilled, SegFault, etc.), SRE-centric troubleshooting commands, and direct notification integration with Slack and Microsoft Teams. No per-node fees or hidden scaling costs. | $199.00 |
Vendor refund policy
Refunds are at the seller's discretion. For technical support or refund requests, contact support@saqtek.com . For purchases made through Channel Partners, please include your Partner Reference ID to expedite the review process with our distribution team.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
PodWatcher Standard Agent
Supported services: Learn more
- Amazon EKS Anywhere
- Amazon EKS
Helm chart
Helm charts are Kubernetes YAML manifests combined into a single package that can be installed on Kubernetes clusters. The containerized application is deployed on a cluster by running a single Helm install command to install the seller-provided Helm chart.
Version release notes
Initial release of PodWatcher (v1.0.2). Features automated exit-code mapping, Slack/Teams integration, and namespace filtering.
Additional details
Usage instructions
PODWATCHER USAGE INSTRUCTIONS
- PRODUCT OVERVIEW & PREREQUISITES
PodWatcher is a stateless monitoring agent designed to run within your Kubernetes cluster. It observes pod events and streams notifications to designated communication channels to reduce MTTR and alert fatigue.
Infrastructure:
- An active Kubernetes cluster (EKS or self-managed).
Required Tools:
- AWS CLI: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-quickstart.html
- Helm (v3.8.0+): https://helm.sh/docs/intro/install/
- kubectl: Configured with cluster-admin access.
Notification Setup:
- MS Teams: https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook
- Slack: https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/
- DEPLOYMENT INSTRUCTIONS
Step 1: Authenticate with the AWS Marketplace Registry Run the following command to authenticate your Helm client:
aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 709825985650.dkr.ecr.us-east-1.amazonaws.com
Step 2: Update Kubernetes Context - Ensure your kubectl context is pointing to the correct cluster:
aws eks update-kubeconfig --region <YOUR_REGION> --name <YOUR_CLUSTER_NAME>
Step 3: Install the PodWatcher Agent Deploy using Helm. Replace placeholders with your configuration values.
helm upgrade --install podwatcher oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/saqtek-us/podwatcher
--version 1.0.2
--namespace podwatcher --create-namespace
--set clusterName="<YOUR_CLUSTER_NAME>"
--set monitoring.watchNamespaces="default,test"
--set webhooks.teams="<YOUR_TEAMS_WEBHOOK_URL>"
--set webhooks.slack="<YOUR_SLACK_WEBHOOK_URL>"
--atomic
Note: To monitor all namespaces, leave 'monitoring.watchNamespaces' blank.
- HEALTH MONITORING & VERIFICATION
Confirm the service is running: kubectl get pods -n podwatcher
Inspect the monitoring logs: kubectl logs -f deployment/podwatcher -n podwatcher
End-to-End Test: Delete a non-critical pod in a monitored namespace: kubectl delete pod <pod-name> -n <namespace> Verify notification receipt in Slack/Teams within seconds.
- DATA SECURITY & ENCRYPTION
- Data Isolation: Runs entirely within your VPC; data only leaves via encrypted notification payloads.
- Encryption: All communication uses TLS 1.2+.
- Stateless: No persistent data storage; events are processed in-memory and purged immediately.
- Sensitive Info: Webhook URLs and keys are stored as Kubernetes Secrets under your control.
- RBAC, The Helm chart deploys a dedicated ServiceAccount and ClusterRole.
- Least Privilege: PodWatcher requests only read-only permissions (get, list, watch) for pods, logs, events, and deployments.
- RESOURCE QUOTAS & SERVICE LIMITS
- Memory Limit: 512Mi
- CPU Limit: 400m (0.4 vCPU)
To update your configuration, modify your values and re-run: helm upgrade --install podwatcher
UNINSTALLATION -To remove the agent and all associated RBAC permissions: helm uninstall podwatcher -n podwatcher kubectl delete namespace podwatcher
Support
Vendor support
As a buyer-deployed product, the customer or managing partner is responsible for the health of the underlying AWS infrastructure (VPC, EKS, IAM) and associated compute costs.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Customer reviews
No customer reviews yet
Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.