Operations | Monitoring | ITSM | DevOps | Cloud

Latest Posts

Code Instrumentation Practices to Improve Debugging Productivity

Code instrumentation is closely tied to debugging. Ask one of the experienced developers and they will swear by it for their day-to-day debugging needs. With modest beginnings in the form of print statements that label program execution checkpoints, present-day developers employ a host of advanced techniques for code instrumentation. When carried out in the right way, it improves developer productivity and also reduces the number of intermediate build/deployment cycles for every bug fix.

Code Instrumentation in Cloud Native Applications

Cloud native is the de facto standard approach to deploying software applications today. It is optimized for a cloud computing environment, fosters better structuring and management of software deployments. Unfortunately, the cloud native approach also poses additional challenges in code instrumentation that are detrimental to developer productivity.

Lightrun Bolsters Security Measures with Role-Based Access Control (RBAC)

Lightrun enhances its enterprise-grade platform with the addition of RBAC support to ensure that only authorized users have access to sensitive information and resources as they troubleshoot their live applications. By using Lightrun’s RBAC solution, organizations can create a centralized system for managing user permissions and access rights, making it easier to enforce security policies and prevent security breaches.

From Monolithic to Microservices: Code Instrumentation Trends

Software architectures are greatly influenced by the size and scale of the software applications. With growing size, the code base becomes complex. With scale, the deployment becomes challenging. The result: debugging becomes an increasingly time-consuming process for developers.

Lightrun Launches New .NET Production Troubleshooting Solution: Revolutionizing Runtime Debugging

Lightrun, the leading Developer Observability Platform for production environments, announced today that it has extended its support to include C# on its plugins for JetBrains Rider, VSCode, and VSCode.dev. With this new runtime support, .NET developers can troubleshoot their apps against.NET Framework 4.6.1+, .NET Core 2.0+, and.NET 5.0+ technologies.

Lightrun's Product Updates - Q1 2023

During the past quarter, Lightrun has been busy at work producing a wealth of developer productivity tools and enhancements, aiming for greater troubleshooting of distributed workload applications and cost efficiency. Read more below the main new features as well as the key product enhancements that were released in Q1 of 2023!

Debugging Serverless Functions with Lightrun

Developers are increasingly drawn to Functions-as-a-Service (FaaS) offerings provided by major cloud providers such as AWS Lambda, Azure Functions, and GCP Cloud Functions. The Cloud Native Computing Foundation (CNCF) has estimated that more than four million developers utilized FaaS offerings in 2020. Datadog has reported that over half of its customers have integrated FaaS products in cloud environments, indicating the growth and maturity of this ecosystem.

Reduce 60% of your Logging Volume, and Save 40% of your Logging Costs with Lightrun Log Optimizer

As organizations are adopting more of the FinOps foundation practices and trying to optimize their cloud-computing costs, engineering plays an imperative role in that maturity. Traditional troubleshooting of applications nowadays relies heavily on static logs and legacy telemetry that developers added either when first writing their applications, or whenever they run a troubleshooting session where they lack telemetry and need to add more logs in an ad-hoc fashion.

2023 is When More FinOps Practices will Shift Left and Cost Optimization around Logging will Get Central Stage

Effective troubleshooting and resolution of critical production issues require DevOps and R&D teams to utilize logging and observability. However, selecting the right logging solution can be challenging, given the wide range of available options and associated costs. Additionally, the strategy for logging usage should be tailored to the needs of different personas and use cases, such as DevOps engineers versus developers.