If you are anything like us here at Sematext, you are likely always trying to automate any tedious, repetitive tasks. Repetitio est mater… boringdorum. Setting up monitoring falls in that category. You either do it manually every time you provision a new piece of infrastructure or service, or you automate it. Note that by “service” I mean either an instance of your own application or something like Nginx or Elasticsearch or MySQL or …
Amazon Elastic Block Store (EBS) provides block storage for applications that are running in the cloud. However, not every company is getting the most out of the EBS volumes they are using. Some companies can pay too much for EBS volumes without utilizing the allocated storage and IOPS. Other organizations may pay high prices because they are using the wrong disk type for their needs. This article explains five techniques you can use to optimize the performance of your EBS workloads.
When it started to really get traction as a concept, almost 10 years ago, DevOps was primarily used to push rapid changes to web environments with minimal impact for the users. That might still be true today but DevOps as a concept evolved. A lot. We now rely on DevOps models to move at high velocity, adapting and developing at speeds that are light years away from anything we’ve seen before. It’s the way we deliver, test, monitor, and release functionalities.
TL;DR note: if you want the bzip2 -9 version of this post, scroll down to the very last section for some quick pointers. If you want to learn a bit about Linux system logs, please continue, as we’ll talk about all these and more.
No matter which path of the stack you work on, it’s crucial you make sure your website or API is up and running. We wanted to create a tool that can give you superpowers. Enter, Sematext Synthetics! You can monitor the availability of APIs and websites as well as their performance, and user journeys. This means 24×7 monitoring from multiple locations around the globe with alerts when things go wrong!
Apache Solr was always ready to be extended. What was only needed is a binary with the code and the modification of the Solr configuration file, the solrconfig.xml and we were ready. It was even simpler with the Solr APIs that allowed us to create various configuration elements – for example, request handlers. What’s more, the default Solr distribution came with a few plugins already – for example, the Data Import Handler or Learning to Rank.
If you’re using Linux, I’m sure you bumped into journald: it’s what most distros use by default for system logging. Most applications running as a service will also log to the journal. So how do you make use of these logs to: In this post, we’ll answer all the above and more. We will dive into the following topics: There are lots of other options to centralize journal entries, and lots of tools to help.
What is the most important feature an Express.js application can have? Maybe using sockets for real-time chats or GraphQL instead of REST APIs? Come on, tell me. What’s the most amazing, sexy, and hyped feature you have in your Express.js application? Want to guess what mine is? Optimal performance with minimal downtime. If your users can’t use your application, what’s the point of fancy features?
Where are Docker container logs stored? There’s a short answer, and a long answer. The short answer, that will satisfy your needs in the vast majority of cases, is: From here you need to ship logs to a central location, and enable log rotation for your Docker containers. Let me elaborate on why with the long answer below.
