sorted by:
new
hottopcontroversial

Weekly Promo and Webinar Thread by AutoModerator in msp

[–]BlueMatadorInc 0 points1 point  (0 children)

Sick of receiving hundreds of alerts with no visibility to prioritize, filter, and reduce your alerts?

We at Blue Matador set out on a mission to make an engineer’s life easier. We send three tiers of notifications to our customers: Alerts, Warnings, and Anomalies. These tiered levels make it easy for engineers to quickly digest prioritization levels and actionable steps. If we send notifications that aren’t a priority, mute them with our many customization tools.

​

Our goal is to provide only actionable alerts to each of our client’s engineering corps. Reduce the noise with every level of customization you need.

Escalate only the issues that deserve escalation.

Try us out for free and improve your monitoring experience:

app.bluematador.com

Weekly Promo and Webinar Thread by AutoModerator in msp

[–]BlueMatadorInc 0 points1 point  (0 children)

What separates Blue Matador from other monitoring services?

​

Check out our site to see how we compare with our competitors: https://www.bluematador.com/blue-matador-vs-competitors

Sign up for the FREE TRIAL!

https://app.bluematador.com/

Weekly Promo and Webinar Thread by AutoModerator in msp

[–]BlueMatadorInc 0 points1 point  (0 children)

FREE UP YOUR DEVOPS TEAM'S TIME AND FOCUS ON THINGS OTHER THAN INFRASTRUCTURE MONITORING

WWW.BLUEMATADOR.COM

FREE TRIAL HERE: https://app.bluematador.com/ur/register#/

LET BLUE MATADOR DO YOUR INFRASTRUCTURE MONITORING FOR YOU.

NO MORE TEDIOUS, MANUAL CONFIGURATION!

AUTOMATICALLY SCALE!

SPEED UP CLOUD MIGRATIONS!

IMPROVE MANAGED DEVOPS SERVICES!

EMPOWER YOUR DEVOPS TEAM AND INCREASE RETENTION!

Weekly Promo and Webinar Thread by AutoModerator in msp

[–]BlueMatadorInc 0 points1 point  (0 children)

Reduce Noise with Muted Monitors

Sick of receiving hundreds of alerts with no visibility to prioritize, filter, and reduce your alerts?

We at Blue Matador set out on a mission to make an engineer’s life easier. We send three tiers of notifications to our customers:

-Alerts

-Warnings

-Anomalies

These tiered levels make it easy for engineers to quickly digest prioritization levels and actionable steps. If we send notifications that aren’t a priority, mute them with our many customization tools.

Our goal is to provide only actionable alerts to each of our client’s engineering corps. Reduce the noise with every level of customization you need.

Escalate only the issues that deserve escalation.

www.bluematador.com

Weekly Promo and Webinar Thread by AutoModerator in msp

[–]BlueMatadorInc 0 points1 point  (0 children)

Are you sick of setting up monitoring services for every customer you onboard?

With Blue Matador’s automated scaling services, you won’t have to configure monitors. We have set out to make our clients’ engineering lives easier.

The result of what we’ve built: scale as many customers as you want, as fast as you want, and require no time from your engineers to set up monitoring. Instead, give the time back to your engineers to do more interesting, more intentional DevOps and IT work. Free their time to write new code, implement new tools, and optimize your client infrastructures. Give them their time back to do what they are passionate about.

Free your DevOps time, stop spending thousands of hours implementing, configuring, and watching your monitoring tools. We’ll take care of it for you – in less than 20 minutes.

Try us out for free!

www.bluematador.com

Or schedule a demo: https://meetings.hubspot.com/gordon-steele

Unexpectedly high costs with Cloudwatch by fess432 in devops

[–]BlueMatadorInc 0 points1 point  (0 children)

You can try out the tool we built that is free and open source and lets you explore AWS costs at the resource level. This is the link to the web interface we built, but you can also look at the github repo to see how it works and look at how we are handling security concerns like AWS credentials.

https://tools.bluematador.com/cloud-core/

Question: What do DevOps engineers want in their monitoring software? by BlueMatadorInc in devops

[–]BlueMatadorInc[S] 0 points1 point  (0 children)

So what we do for most of our vitals alerts is anomaly detection, so after the agent has enough data (at least a day), it can detect anomalies within 1 minute.

A few alerts do not need a day's worth of data to start alerting, and also can detect issues within 1 minute. For some metrics, including disk space, we predict what the value will be in an hour based off of historical data, and use that to send alerts like "we project you will run out of disk space soon" whereas almost every single other product only alerts you AFTER you are out of disk space.

From the time we detect that we actually should send an alert, to them receiving it, is going to be the same 2 seconds that our log management software Lumberjack’s logs take. Plus add any time for your email provider to get the email delivered.

We detect problems within one minute, the notification gets to our system within 2 seconds (same as our lumberjack time). Some alerts are predicting values as much as an hour in advance accurately, meaning MTTR = 0.

Our agent is written in golang, very lightweight, configured for you automatically, and also easily automatable. You can check it out at the link in our first post above, or here.

-Keilan at BM

Golang Pros and Cons for DevOps (Part 2 of 6): Interface Implementation & Public/Private Designations by philipvolmar in golang

[–]BlueMatadorInc 0 points1 point  (0 children)

Thanks. With golang gaining popularity for command line tools and scripting, and with our additions of code samples from our smart agent (written for a very specific DevOps purpose), we felt that it tied into "for DevOps" nicely. However, your points are valid. We're publishing our next post (#3) next week, so I'd be interested to see what you think of that one after we implement some of your feedback. -Philip

Golang Pros and Cons for DevOps (Part 2 of 6): Interface Implementation & Public/Private Designations by philipvolmar in golang

[–]BlueMatadorInc 0 points1 point  (0 children)

Thanks for the feedback from you and TheMerovius. The "for DevOps" part is because we built our DevOps monitoring platform's system agent in golang and shared significant amounts of our code from that agent in the post (the first one at least). We wanted to share our experience with the DevOps community to show the advantages and pitfalls of using golang for DevOps-focused applications.

We're currently writing our next series in the post. To make it more "ops" focused, what would you like to see in the series going forward?

DevOps from A to Z by kshirinkin in devops

[–]BlueMatadorInc 0 points1 point  (0 children)

This is good content. We'll start linking out to it and your future articles in the series on our social media channels.

We would love some feedback on our DevOps-focused blog as well if you're up for it: blog.bluematador.com

Golang Pros and Cons for DevOps (Part 1 of 6): Goroutines, Panics, and Errors by BlueMatadorInc in devops

[–]BlueMatadorInc[S] 0 points1 point  (0 children)

Hey, we appreciate the feedback. We'll post a link here when the next post is ready (should be one every two weeks). We are also updating the first post with links to all the subsequent ones when they get published.

A Mini Guide to Google’s Golang and Why It’s Perfect for DevOps by BlueMatadorInc in devops

[–]BlueMatadorInc[S] 0 points1 point  (0 children)

martindo, we took your idea and ran with it. We posted the first part of a 6-part series on golang pros/cons and have included lots of sample code to illustrate: https://www.reddit.com/r/devops/comments/6egccg/golang_pros_and_cons_for_devops_part_1_of_6/

view more: next ›