The Stack Infra team at Elastic uses many services to provide downloads for projects like Elasticsearch and Kibana to our users. One of these services is Fastly, which helps us optimize delivery to regions around the world. Keeping an eye on the performance and behavior of our CDN is important to ensure we're operating at the level we expect.

As we all know, the on-demand capacity mode of DynamoDB is great but can be cost-prohibitive in some cases (up to seven times more expensive than the Provisioned Capacity mode). The Provisioned mode, on the other hand, shifts to the development team the burden of predicting what level of capacity will be required by the application. And it’s not quite as straightforward to achieve the same level of scalability in the Provisioned mode as we enjoy in the On-demand one.

Logs are valuable. Logs generated by a major backend resource that provides clients with access to crucial data are more than just valuable; knowing where they are and being able to manage and understand the information that they contain can mean the difference between smooth, secure operation and degraded performance or even catastrophic failure for your application. MySQL Server produces a handful of basic logs.

There are instructions to get started with IPHost Network Monitor, covering most typical situations. However, using the defaults (for both monitors parameters and for network discovery) when looking for hosts and/or monitors can result in rather slow setup. In most cases, it is simpler to create "draft", lightweight monitors just to make sure the service exists and accepts connections, and add actual protocol-specific checks as required.

Energy storage and sustainability are big issues in Hawaii, where oil tankers are shipped in everyday, just to keep the lights on. Resiliency in the energy grid, due to threat of natural disaster, is critical. Energy storage is needed to manage how much solar energy is coming into the market or into the grid. Properly managing the power entering the grid is vital for grid stability since Hawaii has intermittent energy that floods the grid.

In the following example, we will be creating a histogram in Grafana. Our datasource is Prometheus’s cumulative histogram. I have captured the metrics using micrometer’s distribution summary.

This tip is for those who are using Prometheus federation to monitor multiple clusters. How should alertmanager be configured for multiple clusters? Let us say that if there’s an issue for Cluster A it only needs to send an alert for cluster A? In such cases, every alert should be routed to proper team based on labels (if there is problem with application A on cluster B - team responsible should be notified). In the above case, two alerts are triggered by the same rule.

Creating security policies for the devices connected to your network is critical to ensuring that company data is safe. This is especially true as companies adopt a bring-your-own-device model and allow more personal phones, tablets, and laptops to connect to internal services. These devices, or endpoints, introduce unique vulnerabilities that can expose sensitive data if they are not monitored.