If you have any experience with comparing open source data visualisation tools then it is very likely you will have encountered both Kibana and Grafana during your research and discovery phase. As two of the most popular solutions for logs and metrics analysis, it can be difficult to distinguish between the two and make the choice to use either Grafana or Kibana depending on the analysis task at hand.
There are two types of Ruby Begin and End blocks. A simple Google search of “Ruby begin end blocks” will lead you to either of these two kinds of articles – the ones in all caps (BEGIN and END) and the ones usually separated by a slash (begin/end). Both of these are different things but confused with the same name. In this post, we will dive into both. Here’s an outline of what we’ll be covering so you can easily navigate or skip ahead in the guide –
The rise of game engines has sparked new innovations across industries. Amazon Lumberyard — the Amazon game engine — has recently transitioned to open source. Open 3D Engine (O3DE) may be new on the scene. But as companies continue to move to the cloud, many are looking at this new Amazon game engine to transform their pipeline.
Through FMEAs, product development teams are able to determine potential failures within a project and improve them to mitigate risk. The most efficient way to conduct a failure mode and effects analysis is through an automated tool. This blog will provide an overview of FMEAs and highlight the many benefits they can have on your product.
“As a gamer, I wish for it. But as a developer, I wouldn’t want to be working on backward compatibility. It’s soul-crushing maintenance work, man!” – A developer on our team who shall remain unnamed! Let’s call her Dev-I for now. Last week, I was talking to internal Appian developers on backward compatibility (BC) when one of them shared this quote.
It is incredibly helpful to quickly detect when a customer encounters an error and where the error originated from in your source code. Thankfully, this is where many interpreted languages shine. They always include a complete backtrace — the path where the call was made, which caused the error to be raised (or thrown). In AppSignal, any error alert will bring you to an incident detail page that shows you that backtrace.
In any business, in any industry that relies on purchases of their products or services, one of the most important rules is to retain its loyal customers. The Pareto Principle (80% of the results comes from 20% of the input) proves how important customer retention really is. Research shows that often, 80% of the sales come from around 20% of customers. Apply this method to your sales, and you’ll see!
The issue of memory bloat in Ruby applications is a topic of frequent discussion. In this post, we will look at how Ruby memory management can go wrong, and what you can do to prevent your Ruby application from blowing up. First, we need to understand what bloat means in the context of an application’s memory. Let’s dive in!
It can be a real headache to test contact forms or other outgoing emails from your website or application locally. To permit mail, you ought to configure your nearby web server and waste plenty of time expecting the mail to reach for your inbox, if it does at all. Furthermore, if you test with your personal email account as the sender, you risk damaging your email address. So, what should you do? You can use tools like MailHog and others, which are great for sending transactional emails.
