Operations | Monitoring | ITSM | DevOps | Cloud

Applications built on the Node.js platform, an event-driven I/O server-side JavaScript environment based on Google Chrome’s V8 engine, are known as Node.js applications. Since both the server-side and the client-side are written in JavaScript, Node.js facilitates easier and faster implementation of codes, and processes requests quickly and simultaneously; this is greatly beneficial for building real-time applications, especially chat and streaming applications.

With a special thanks to Aleksandar and Unai, we’re happy to announce AppSignal for Elixir 1.13.0, which includes our all-new LiveView instrumentation helpers and updated typespecs. If you’re not an AppSignal user yet, make sure to check out the product tour and see how errors, performance, host metrics and triggers all come together in one tool.

Configuration has long been a hot topic in the Elixir community, and luckily, in the recent months, there has been a great deal of thoughtful work put into making this problem an easier one to solve. Today, we’re going to show you how to migrate from an Elixir application that has been configured with the widely used config/*.exs files at compile-time, to an application that instead uses environment variables for configuration and is configured at runtime.

You’ve created the perfect design for your indices and they are happily churning along. However, in the future, you may need to reconsider your initial design and update the Elasticsearch index settings. This might be to improve performance, change sharding settings, adjust for growth and manage ELK costs. Whatever the reason, Elasticsearch is flexible and allows you to change index settings. Let’s learn how to do that!

Businesses around the world have been forced to adopt remote working policies in response to the COVID-19 outbreak. In just two months, a vast number of employees around the world shifted to a work-from-home environment. Although some businesses already had many of their IT operations available on the cloud before the pandemic—with the help of cloud-hosted email and collaboration suites such as Office 365—no one expected such a sudden and widespread transition into teleworking.

In the past two months, companies everywhere have shifted their workforces from office cubicles and conference rooms to home offices and dining room tables. The coronavirus pandemic’s thunderous impact – bolstered by government mandates to maintain social distancing protocols and shut down non-essential workplaces – has forced companies to pivot hard and fast to a new reality, whether they’re ready for it or not.

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.

Grafana v7.0 is coming next month! Here’s a sneak peek of one of its features: a brand-new table panel. The current (old) table panel has accumulated a ton of feature requests over the years, and we are excited to finally close many of them in 7.0 with this new table panel. Among the many new things this panel can do is to include other visualizations inside cells. For example, you can configure a cell style (per column) to render the value as a bar gauge.

So, you are considering moving to the cloud. Or, likely, have already transitioned your services. If you are wondering what the next steps are, you have many options on how to move towards cloud infrastructure. This blog will cover what to consider when using public clouds. Specifically, we will focus on monitoring a hybrid cloud set up using the big 3 cloud providers, Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP).

Editor's note: This blog is part two of our series on launching an app to AWS. For the first installment, "How to deploy an app to AWS: Getting started," click here. So, your application is ready for production. You’ve taken an inventory of your applications, dependencies, and configuration. Now, you’re ready to create a new AWS account and start launching resources.