As most developers will agree, writing code is oftentimes, if not always, easier than debugging. As a simple definition, debugging is the process of understanding what is going on in your code. When speaking in terms of Python, it is a relatively simple process. Every developer has their own personal debugging method or tool they swear by. When it comes to Python, most developers use one (or more) of the following: print statements, traditional logging, a pdb debugger, or an IDE debugger.

When visiting a new website, it is quite normal to get carried away by the bells and whistles of the fancy UI and UX and not be able to appreciate all the lower level, back-end code that runs tirelessly to ensure a smooth and fast website experience. This is because your front-end HTML code has a visually rich browser page interface as a platform to showcase its output. Whereas your back-end, server-side code usually only has a console at its disposal.

There are two ways you can view the current mappings on your Logit ELK Stacks. One way is to use dev tools in Kibana. You can access Kibana from any of your dashboards by choosing from your dashboard Stack settings > Access Kibana. You can also search for a specific mapping of an Index name. For example if we wanted to see the mappings for the a Filebeat index name we can run the following to return only the desired mappings.

Welcome to the Bugfender summer newsletter! As we already announced, we achieved a major milestone recently by releasing the Web SDK, bringing the features you love using to a whole new platform. But as always we want to keep pushing to give you a better product, and we’ve introduced recently some more updates we want to share with you: We hope you find all these updates useful!

When something crashes in an app, fixing the bug is usually quite straightforward. But apps can also be blighted by bugs that don’t result in crashes, and this is where things start to get interesting. To find and fix these bugs, you will require as much information as possible and probably a combination of tools. Let me explain a process we know as ‘bug forensics’, based on a real bug that has impacted one of Bugfender’s customers.

When you’re building a website that needs to be updated in real-time, your first thought is probably to add WebSockets to your application. However Websockets is a low-level protocol and to use it, you’ll need to add another layer on top to manage the information you want to get. This is where MQTT is handy, as it’s a higher-level protocol that simplifies working with data streams.