What is our primary use case?
widdix marbot's main use case for our organization is AWS monitoring for Slack. Our team lives in Slack, where we all talk about things, and the fact that it dumps AWS health notifications right into our Slack where we can all immediately begin discussing them is better than sending them to some other channel such as SNS or text messages or emails. Usually, health issues need to be resolved in a very urgent manner, and one day I think we'll be on PagerDuty, but until that day, we just all respond immediately in Slack.
I prefer having those AWS health notifications in Slack over other channels like email or SMS because email chat is less real-time, and often when you see a health notification come through, you need to be talking in real-time. It needs to be as fast as you can type: "Hey, you just put out a change, didn't you? Oh, look at this. This is happening. Is this your change? Okay, let's hop on, let's roll back."
What is most valuable?
widdix marbot offers one main feature that is truly valuable: tightly syncing your AWS health to your Slack. I don't think it has lots of bells and whistles. It does one thing, and it does it well.
The tight syncing of AWS health to Slack is so valuable for my organization because of collaboration and speed. widdix marbot has positively impacted my organization as our systems almost never have downtime longer than two or three minutes.
What needs improvement?
widdix marbot doesn't need improvement; it's already perfect. I can't imagine anything, even a small detail, that could make my experience with widdix marbot even better, and there's nothing that would help as my team grows or as my needs change.
For how long have I used the solution?
I have been using widdix marbot for ten years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
widdix marbot's scalability is great.
How are customer service and support?
The customer support for widdix marbot is excellent. I would rate the customer support a ten on a scale of one to ten.
How was the initial setup?
It was easy to deploy widdix marbot in my environment. My experience with the configuration process was easy.
What was our ROI?
I haven't seen a return on investment, and I cannot share relevant metrics regarding fewer employees needed, money saved, or time saved.
What's my experience with pricing, setup cost, and licensing?
My thoughts about the metering and billing experience are that it's a little expensive, but I don't mind. My experience with pricing, setup cost, and licensing is that it was easy but a little high.
What other advice do I have?
I have no advice to give to others looking into using widdix marbot except to use it. I would rate this review a five on a scale of one to ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
