Engineering time is a precious resource. We often have to balance many tasks and often conflicting priorities. In this article, we’ll look at ten activities for which allocating more time can be beneficial. Let’s learn from the mistakes of others.
We are pleased to announce our newly launched dashboard design which we have created to assist cross team collaboration for users that prefer to use multiple Stacks per account. We understand that Cybersecurity specialists, Sysadmins, Product owners, developers and CTOs may all have different requirements for using our platform for logs and metrics analysis.
Developers of any skill set find it frustrating when we don’t have access to the information we need. We want easy and complete access to application logs so that we can troubleshoot application problems. Quickly resolving issues requires a complete picture of what’s going on. Using the wrong tools limits our ability to determine what’s wrong, slowing the repair process.
Generating and collecting logs is one thing. Generating and collecting actionable logs can be quite another. That's a problem because logs that are not actionable – meaning they can be easily used to derive valuable insights or resolve issues – are not very valuable. If you don't generate actionable logs, you might as well not log at all. Fortunately, ensuring that you generate useful logs is not tricky. Keep reading for seven tips on making your logs actionable and valuable.
Developers must have access to the information that they need. Accessing this information, however, can be time-consuming. With the wrong tools or workflow, it’s frustrating and challenging to filter logs by source. Tags are an easy solution from LogDNA that helps developers get a more granular view of what’s going on in our services.
Many organizations are moving from monolithic to microservices-based architectures. Microservices allow them to improve their agility and provide features more quickly. Although developing a single microservice is simpler, the complexity of the overall system is much greater. Here, we’ll review how to add distributed tracing to C++ with the OpenTelemetry collector and send to Logz.io. One of the biggest challenges is finding efficient tools to quickly debug and solve production problems.
See how the Logit.io platform helped give Youredi a more streamlined reporting and data visualisation alternative to using Microsoft’s Power BI in our latest customer case study. Outside of its BI capabilities, the Logit.io platform is used throughout Youredi by everyone from their technical teams through to their customer support and professional services department.
We are excited to announce support for Google Compute Engine (GCE) N2 general purpose virtual machine (VM) types, and additional hardware configuration options powered by N2 custom machine types. N2 VMs leverage Intel 2nd Generation Xeon Scalable processors and provide a balance of compute, memory, and storage. N2 machine types also offer more than a 20% improvement in price-performance over the first-generation N1 machines.
We are excited to announce that Logit.io has recently taken home three awards from Appvizer’s selection ranking the best log management and data analytics tools on their platform. In addition to this, we’ve also been named as one of their certified partners for 2021.
