In Python development, logging is not only good practice; it is vital. Logging is critical for understanding the execution flow of an application and helps in debugging potential issues. The importance of logging for developing reliable and maintainable Python applications cannot be overstated. Python provides capabilities for running concurrent operations—either in a threaded (single process) or multiple process environment. But what implications do these different approaches have on logging?

Whether you work in banking, education, or run a small business, your network’s security is essential. After all, an insecure network can result in data breaches, theft, unauthorized access, poor network performance, a tarnished reputation, and more. To better understand the state of your network and bolster your network’s defense against current and potential threats, consider using network vulnerability scanners or detection tools to quickly detect existing loopholes.

Docker’s power and versatility have cemented its place in developers’ and administrators’ toolkits. Along with this widespread adoption comes the critical need for effective logging in Docker containers. However, once you scale beyond a single container on a single machine, effectively capturing and working with logs from Docker presents a challenge. The native docker logs command quickly becomes inadequate, and you’ll need a more scalable solution.

Many modern software applications are built with a microservices architecture, and Node.js has become the runtime environment of choice for many developers building microservices. However, working with logs in microservices—especially as complex applications comprise dozens (or more) microservices—is a challenging and cumbersome endeavor. Logging is a crucial part of building and maintaining an application.

After the craziness of the last few years, it is understandable that IT, DevOps, and operations teams want more stability in their personal lives and professional roles. However, there appears to be a disconnect between their desire for stability and the vision from the top.

If you watched our recent SolarWinds Day: Secure by Design panel discussion, you know security is a critical need for all businesses today. Secure by Design is our guiding principle for how we built our security approach, adhering to government regulations and industry expectations.

Node.js logging, like any form of software instrumentation, isn’t an easy thing to get right. It takes time, effort, and a willingness to continue to iterate until a proper balance is struck. There are so many points to consider, including: Previously, here on the Loggly blog, I began exploring these questions in the context of three of the most popular web development languages: PHP, Python, and Ruby. But these aren’t the only popular languages in use today.

Application programming interfaces (APIs) have become a critical part of almost every business. APIs are responsible for transferring information between systems within a company or to external companies. For example, when you log in to a website like Google or Facebook, an API processes your login credentials to verify they are correct.