In the new cloud-native world, ephemeral services like containers make security a challenging task. As enterprises start adopting containers in production, they suffer from a great deal of variance in the software, configuration, and other static artifacts that exist across their organization’s container image set.
Infrastructure Monitoring refers to the constant tracking, collection and analysis of data about the infrastructure/server. Using this data, you can monitor the performance and the behavior of the hosts at the infrastructure level. You can also identify the issues that are of concern. For instance, you can periodically check and monitor the health of the hosts and if any slow downs occur, it’s easy to alert the users.
In the last couple of weeks StackStorm has published back-to-back releases. 2.10.2 is a traditional patch release from StackStorm, and you’ll find some of the highlights below. 2.10.3 and 2.9.3; however, are releases to address CVE-2019-9580. I want to thank Barak Tawily and Anna Tsibulskaya: the researchers who discovered and submitted a patch for the issue.
Site speed is critical to providing an optimal user experience and Google rankings. WordPress is an optimal platform for websites because of its flexibility. About 33% of all websites are built on it. Because of its popularity, there are a variety of technologies, frameworks and plugins available to site owners. While the flexibility is great, it also provides an overwhelming number of choices.
As Elasticsearch is gradually becoming the standard for textual data indexing (specifically log data) more companies struggle to scale their ELK stack. We decided to pick up the glove and create a series of posts to help you tackle the most common Elasticsearch performance and functional issues. This post will help you in understanding and solving one of the most frustrating Elasticsearch issues – Mapping exceptions.
