It’s been another brutal week. The coronavirus a.k.a. “Rona” as my teenage daughter and her friends call it, is just making things miserable for everyone. There have been significant impacts on the tech sector, along with oil and gas, finance, travel, hospitality, and many other industries. But there’s always a silver lining when disaster strikes. So let’s start on a positive note: many of us in information worker roles can work from home.

Automation is a powerful tool that can make processes more efficient and less expensive. You may think that automation tools are only accessible by large companies with significant resources. There are some cases when outsourcing complex tasks to professional consultants is the best options, such as website migration by cms2cms.com. However, other tasks can easily and effectively be achieved in-house with the help of automated tools.

So you’re using InfluxDB and Telegraf. Perhaps you’re writing over a million metrics points per second. Perhaps you’ve used Flux to do some data exploration. However, you now find yourself in a little bit of a pickle. You need to process and analyze this large amount of data, and you’d prefer to do that work in your favorite language with your go-to libraries.

Until now, standard search solution pricing has been based on models that are difficult to understand, expensive to scale, and/or beneficial to only the search vendor. At Elastic, we’re taking a different approach based on the principles of transparency, fairness, and scalability, and have introduced resource-based pricing for our products running on Elastic Cloud. And we believe that this pricing approach will revolutionize Enterprise Search buying and ownership.

Many companies are moving their infrastructure and web applications to the cloud. Along with moving to the cloud, organizations are finding new ways to remain agile and nimble, especially when it comes to software. By utilizing Amazon AWS and Amazon ECS, companies are decoupling their monolithic applications and taking advantage of microservice architecture.

For any business to succeed, it’s important for it to reach users effectively. Almost every business today is online and therefore reaches users through applications. If you run an online business, or if you are a part of such a business, it’s important for you to know what impact your application has on your users. One of the best ways for you to know what impact your application has on the user is through end user monitoring.

I often smirk when I hear or read about other companies pitching a digital experience management platform for IT support. To outsiders this claim may sound innocuous but after 30 years in IT I know most cannot even come close to understanding, let alone managing, the full Digital Employee Experience (DEX). Why? It’s best to define some terms before I draw any lines in the sand.

“Servcies&Systems” category subscriptions provide a highly flexible way of routing alerts to specific user groups. This can for instance be used to route alerts based on responsibilities or skills. But other scenarios are possible too as the category subscription mechanism is extremely powerful. SIGNL4 currently provides two fundamental ways of routing alerts. The first layer is the routing of alerts based on the “on duty” status.

As more and more businesses move their servers to the cloud, it makes it more difficult to monitor the status of networks and other such events typically tracked and monitored in traditional in-house server environments. In recent years, companies have turned to a wide array of hybrid multi-cloud monitoring tools.

Stackery is pleased to announce its addition of support for the new AWS HTTP APIs service which is being introduced today alongside the existing API Gateway tooling. Our addition of such support, in parallel with the GA announcement of HTTP APIs, is an example of how we partner with AWS to accelerate serverless application development and delivery for customers.