To complement distributed tracing, runtime metrics, log analytics, synthetic testing, and real user monitoring, we’ve made another addition to the application developer’s toolkit to make troubleshooting performance issues even faster and simpler. Today, we’re excited to introduce Profiling—an always-on, production profiler that enables you to continuously analyze code-level performance across your entire environment, with minimal overhead.
Does one or more of the following personas describe you? If you fit one of those personas, you are in luck because I’m happy to tell you about some new Splunk integrations with Visual Studio Code in this blog.
You’ve been staring at your screen for hours, trying to check why a certain bug is occurring only for end-users in your production environment. You’ve tried a multitude of approaches: adding log lines in all kinds of indicative places, logging potentially relevant variables to get an indication of the state in which the bug occurs, and the list just goes on. Sounds familiar?
In a modern organization, the dependency on constant data flow doesn’t skip a single role -- already encompassing every function in R&D, Sales, Marketing, BI, and Product. Essentially every position is going through a fusion process with data-science. “Data is the new oil.” “Everyone needs data.” You’ve probably run into these and similar expressions more than once. The reason you hear them so often is that they are true.
The craziest thing happened to me during this holiday season! It may have been all of the magic in the air (or the extra partying), but one day, just before Christmas, I suddenly realized I can travel through time. Of course, the first attempt I made was to go back and prevent several historical events from happening. But alas, it turned out I could only travel through my own personal timeline.
In case you missed our pair programming session about how to run, crash, and debug a Native application using Sentry, worry not! Our artificial intelligence Richard — much more intelligent than it thinks — has used its special powers to upload a recording of our session. This time, we chose a very special victim: Symbolicator. That’s the service responsible at Sentry for processing native crash reports.
Dear Dev Santa, How are things at the north pole? I hope you and Mrs. Santa have good wifi reception, and that the elves aren’t driving you crazy with their electric scooters and kombucha tea. I know that at this time of year you’re very busy going over Git Blame, trying to see which developers were naughty and which were nice. And I’m guessing it’s also a crazy time at the gift factory, designing Christmas-themed tech conference swag and candy.
It’s 2 AM on a Saturday and you get a call. You bolt out of bed and pick up the phone knowing that something terrible has happened. No, your dog didn’t get kidnapped and you don’t need to use your particular set of skills and parental rage to bring its captors to justice. Instead, your weekend slumber has been interrupted because there’s a bug in a system and you have to fix it.
Two months in one! We’re wrapping things up for the year, but wanted to give you all an update on all the great things we’ve shipped in the closing of 2019.
We recently got back from an amazing KubeCon in San Diego, where attendance has skyrocketed to over 12,000 people. The impressive number of attendees is yet another sign of the extremely fast pace at which Cloud Native Computing and the surrounding tech space is growing. Organizations like the Cloud Native Computing Foundation (CNCF) have been gaining steam in growing the community of both enterprise and open-source software.
