It’s 2am. You receive a notification from your monitoring tool. A host server ran out of space and your system is down. Now you need to get out of bed and clear the log files of whatever service has filled up your available disk space. Ugh. Now, imagine that an automated action is triggered, the log files are cleared, and your system is up and running again without requiring a single thing from you. Sounds cool, right?
Looking through our company Slack channels, we use GIFs to respond to each other a lot. We use the Giphy Slack app to quickly add a witty or sarcastic response to someone (we like each other really). And we also know that a lot of our customers use our Slack integration to receive alerts, because who wants emails. Then one morning, this conversation happened – where else – but on Slack.
You know what they say: “Nothing lasts forever.” That’s especially true of technology. And as much as you might have loved that flip phone, 486-based tower, or perhaps that original iPad, all good things must come to an end. Whether an unfortunate tumble destroys a once-shiny-and-new device, a system stops responding as snappily as it used to, or a support agreement ends, there are many reasons to move on from older tech.
Get a decent source code management system like Github, Gitlab or Bitbucket etc. Every one uses the same code and keeps upto date with base line. this reduces the merge conflict issues. Don’t put every thing in SCM but everything you need to do a build should be in there including: test scripts, properties files, database schema, install scripts, and third party libraries
It is 2 am in the morning and you get woken up by a phone call from the helpdesk team. The helpdesk is receiving a flood of calls from application users. A business-critical partner application, powered by Java, is reported to be slow and sluggish. Users are complaining that the browser keeps spinning and eventually all they see is a ‘white page’.
Building your monitoring landscape can be a hard task. The main reason for this is the sheer amount of available solutions. Even though, each of them has their own reason for existence. One challenge during the discovery phase is to find out if the tools you selected can work together. If they have integrations for each other or if they can use the same storage backend. OpenAPM aims to help you find out which parts can work together and how you may use them in combination.
Back in 2016, we added support for monitoring wildcard DNS records. Wildcard DNS records are used to serve requests for otherwise non-existent domain names. Today we’re pleased to announce that we’ve extended our support for using wildcards in DNS records monitoring. DNS Check now allows you to specify a wildcard (*) in place of some DNS record values, such as an A record’s IP address to indicate that any value is acceptable, but the record must exist.
August is flying by, but hopefully there’ll still be time to enjoy a few more summer evenings. This week we’re sharing the video demoing the new Explore UI in Grafana from last week’s PromCon, monitoring VMWare’s VKE with Prometheus, hosting a blog on a budget and more.
As you may be aware, we recently rolled out some exciting new features to your off-site status page. In the coming weeks, I’ll be highlighting some of these and taking a closer look at how each may be used to enhance your experience with StatusKeeper and hopefully make your job a little easier.
We live in exciting and worrying times. In serverless and containers, we have two amazing technologies that provide productive, machine-agnostic abstractions for engineers to work with. And yet, there seems to be an unbridgeable chasm between the two camps. If you have read anything I wrote in the last two years, you know that I am firmly in the serverless camp. But I was also an early adopter of containers.
