Operations | Monitoring | ITSM | DevOps | Cloud

Databases power all modern applications. They’re behind your Angry Birds mobile game as much as they’re behind the space shuttle. In the beginning, databases were hosted on a single physical machine. Basically, it was a computer running only one program: the database. Then we moved to running databases on virtual machines, where resources are shared among multiple operating systems and applications.

When your alerts cover systems owned by different teams, who should be on call? We get this question a lot when talking about SLOs. We believe that great SLOs measure things that are close to the user experience. However, it becomes difficult to set up alerting on that SLO, because in any sufficiently complex system, the SLO is going to measure the interaction between multiple services owned by different teams.

Disaster recovery (DR) plans are not one-size-fits-all. There’s no silver bullet, and without a clear understanding and some level of customization, a DR plan done wrong will have detrimental effects on an organization’s operations and business. And let’s not forget the wrecking ball a bad DR plan delivers to the VAR or MSP who designed and executed it. Loss of business aside, there’s guilt, reputation damage, and potential lawsuits. It’s not a good day.

From using energy-efficient equipment to helping customers choose the greenest network paths, we’re committing to doing our part to combat climate change.

Good stock management means having the right amount of stock in the right place at the right time. It is crucial to keep track of stock levels so that you know when to place a new order, how much to order and where to store it in order to avoid losses in the event of a stock-out. However, finding the perfect balance is not an easy task. A stockout occurs when a company is unable to meet a demand, which will have an impact on operations.

AWS is a cloud platform that is popular and widely used in many industries. They have many services such as EC2, S3, Lambda, and many more. Since AWS is so popular, being able to easily use it along with your other tools is a priority. We have an AWS integration set up with our tool so that our users have an optimal experience.

Logs often contain sensitive data, including personally identifiable information (PII) such as names, email addresses, and phone numbers. To maintain security and comply with data protection regulations, it’s crucial to mask this data before storing it in your log analytics tool. BindPlane OP streamlines this process with the Mask Sensitive Data processor, ensuring your logs are safe and compliant.

Deciding what metrics to measure leads to the next big issue: How to Measure. Often the problem is not so much in the measuring but in the comparison. Measuring the revenue is only useful if you can compare it to a baseline of revenue to know whether the result is good or not. Summarized, there are four basic techniques, each with advantages and disadvantages: Test and Control: Typically execute new pricing in some locations while using the legacy process in others.

The first person to coin the term “Artificial Intelligence” predicted that someday people would buy software as a utility. The year was 1961 and that person was Professor John McCarthy, a computer scientist at Stanford University. After Salesforce began selling software programs this way in the late-1990s, the good professor witnessed his prophecy come true for over 12 years before his passing in 2011. Yet this is only one aspect of computing in the cloud as we know it today.

We recently introduced the LogicMonitor Exporter which is now a part of OpenTelelemetry Collector Contrib distro. This allows you to bring your collector for streaming telemetry data from your environment to LM Envision, LogicMonitor’s hybrid and multi-cloud monitoring platform. LogicMonitor associates the exported logs and traces from a single OpenTelemetry collector to simplify your application’s operations and troubleshoot issues.