Logging in a very basic way
What to log
Why you should log at the client-side
In today’s world of complex code and deployment, people on the DevOps front line face challenges in monitoring, alerting, tracing distributed systems and log aggregation/analytics. Jointly, these are often called “observability” (reference: Twitter blog).
These are challenges faced by multiple groups like DevOps, core engineering teams and Web 2.0 developers. We see concerns in web applications and traditional enterprise applications. We foresee even more issues in emerging spaces like IoT, event-driven design and microservices.
And as is usual in most complexity-bound problems, there are a lot of ways to solve these challenges. These include the use of discrete tools and procedural methods. Such approaches often cause gaps and leave edges uncovered. After all, the matrix of product types and usage (use cases) are large and growing and the need and scale are also increasing.
So, what do you think about observability? Scalyr is hosting a short survey to find what the current state of observability is. The survey looks are several areas, including tools and related issues and we invite you to chime in with your thoughts. While the survey is the best place to express your views, feel free to leave us a comment on this topic.
Our Scalyr platform releases over the past month have focused on Kubernetes monitoring, query performance, and making improvements to usability.
We have added Kubernetes monitoring to our agent. We recommend running it as a DaemonSet on your cluster for efficiency and minimal disruption. Find the new Scalyr agent on Github, and don’t forget to download our Kubernetes monitoring best practices document.
Query Performance Hits New Benchmark – 1.5 TB/second
We have continued to optimize for performance, leading to a new throughput query performance benchmark. Our streamlined database architecture, combined with the brute force technique of applying every core in our cluster to every user query, helped us surpass the 1.5 TB/second benchmark – up from 1 TB/second late last year. Last month, we made a number of improvements, including how we load data from disk, manage concurrent queries, and map data to RAM cache pools.
User and Group APIs
We have added APIs to manage granular user and group permissions. These include adding, listing, editing, revoking access, and providing permissions to users, groups, and users within groups. Learn more in our API documentation.
Billing and Usage Page
We made a number of usability improvements last month, the most notable of which is our revamped billing and usage page, providing at-a-glance information for cost management. Learn more in our Billing and Usage page at the top right dropdown (email@example.com > Billing Plan).
We are developing Scalyr with the DevOps front line in mind, and with a focus on our three value pillars – fast, simple, and shareable. The next several releases will focus on the simple part of that equation and include such improvements as making export to Amazon S3 buckets easy and revamping our alerting capability.
Your product (or any) feedback is always welcome. Please reach out to us at firstname.lastname@example.org.
Chocolate or vanilla? Pancakes or waffles? Coke or Pepsi? We decide between similar choices every day. Some of us have preferences, and other times it’s just a feeling in the moment. A common decision in the IT world is the “build vs buy” decision. Sometimes this decision is not so cut and dry.
Can the decision to build or buy paralyze us with fear? Certainly. Do some have preferences? Definitely. However, all is not lost. There can be a logical system to decide whether to build or buy when it comes to software.
Today features another post about the nuts and bolts of logging. This time, I’ll be talking about the Apache error log in some detail.
Originally, I had a different plan and outline for this post. But then I started googling for good reference material. And what I found were way more questions than answers about the topic, many on various Stack Exchange sites. It seems that information about the Apache error log is so scarce that people can’t agree on where to ask questions, let alone get answers to them.
So let’s change that. I’m going to phrase this as a Q&A-based outline, hopefully answering all of the questions you might have come looking for—if you googled the term—while also providing a broad narrative for regular readers.
In this world of lightning-fast development cycles, MVPs, and DevOps, it may intuitively feel like security gets left behind. You might be thinking, “Aren’t the security guys the ones who want to stop everything and look at our code to tell us how broken it is right before we try to deliver it?” Many feel that DevOps security is a pipe dream.
Is it possible to be fast and secure? Lately, I’ve been drooling over a sports car—namely, the Alfa Romeo Giulia Quadrifoglio. Long name, fast car. It holds some impressive racing records and sports 505 horsepower but also is a Motor Trend Car of the Year and an IIHS Top Safety Pick. These awards are due to automatic braking technology, forward-collision warning, lane-keeping assistance, blind-spot monitoring, and rear cross-traffic alert. It is possible to be fast and safe.
The key to DevOps security is to move forward with development. Security teams need to understand why DevOps practices are so effective and learn to adopt them.
You probably don’t think of verbose logging as the stuff that hackathons and startups are made of. Nor would most programmers consider it an especially advanced technique. But it is important, and enough people ask about it that it’s worth covering.
Part of the reason that so many people inquire about the subject of verbose logging is that it’s kind of general in the same way that searching for “logging” is general. So let’s start by at least getting more specific with a definition.
Although starting a DevOps initiative is not an easy task, looking for people that have the necessary skills is even harder. It doesn’t matter what your background is; developer or sysadmin, you’ll need to improve or acquire some new skills and knowledge to succeed in your day-to-day job.