Blue Matador eliminates the need to manually configure alerts by instantly discovering all of your resources, automatically creating hundreds of alerts out-of-the-box and proactively notifying you of critical production issues
For time-strapped, agile tech teams, monitoring tools are too manual. Understanding baselines, fine-tuning thresholds, and examining visualizations for defects requires significant time and toil. But unlike all the other monitoring tools on the market, Blue Matador eliminates the need to manually configure alerts. Blue Matador instantly discovers all of your resources, automatically creates hundreds of alerts out-of-the-box and proactively notifies you of critical production issues...saving you considerable time and helping you deploy your application with confidence.
In less than 30 minutes of onboarding, Blue Matador automatically monitors and sets up dynamic alerts for your AWS services, including:
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.
You pay based on the number of billable compute resources that Blue Matador monitors, measured in host hours (HostHrs). Usage scales with how many hosts you run. A host counts as one virtual machine or physical server, or a group of 10 smaller resources such as functions, container tasks, state machines, shards, or pods. Where virtual machines and containers overlap, Blue Matador deduplicates and counts them once. As you add or scale resources, your billable host count rises, so your charges track actual monitored capacity over time.
Top-of-mind questions for buyers
How is a host counted for serverless functions, container tasks, and pods?
For serverless functions, 10 functions count as one host, so 40 functions equal 4 hosts. For container tasks, 10 tasks count as one host. For pods, 10 pods count as one host. Each virtual machine or physical server counts as one host on its own.
Does my bill change if I scale up resources or run non-production environments?
Your billable host count rises as you add or scale monitored resources, so charges track running capacity. You can monitor test, stage, and development environments from the same account. All monitored environments and resources add to your host count and appear on the same usage bill.
Are overlapping virtual machines and containers counted twice?
No. Where virtual machines and containers overlap, Blue Matador deduplicates and charges you once for that resource. This prevents the same underlying infrastructure from inflating your host count. Billing reflects distinct monitored resources rather than every layer running on the same machine.
www.bluematador.com
Helpful?
Vendor refund policy
All fees are non-cancellable and non-refundable except as required by law.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
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.
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.