Let’s be honest. No one wakes up in the morning thinking of reasons to contact customer support. It’s tedious, onerous, and can eat into your evening Netflix time. Thankfully, most brands realize that customer experiences drive brand loyalty and repeat purchases.
Even though most of us have spent this month working from home or furloughed due to COVID-19, glitches certainly haven’t been taking a break. We’re still relying on intricate software systems to keep the world moving, and we have little ability to maintain them in person. What’s more, changing usage patterns have stressed global networks in ways that are hard to anticipate. As a result, we find ourselves in a perfect storm for technical outages.
Managed service providers (MSPs) have been around for more than 20 years, and my how things have changed since they grew out of the original application service provider (ASP) model. Until recently, MSPs have focused primarily on remote monitoring, security, network management and other routine IT tasks that CIOs would rather outsource for cheaper than they can run internally.
On the internet, nothing necessarily stays easy, simple, and reliable forever – but we’re trying to keep it that way for your logs. When our customers use Kubernetes, they want to remain focused on the real challenges of scaling, and avoid infrastructure headaches, so that they can adapt to the unexpected easily and with a minimum of toil. That’s why we continue to invest in the LogDNA Agent. It’s built to handle file logging in even the most intensive Kubernetes deployments.
LogDNA is adding the ability to store and view raw lines, allowing customers to debug with logs in their unaltered form. If you’ve ever looked at your logs and noticed that the timestamp was different than what you expected, it is usually due to a long latency between the event and processing time of the logs. Depending on the size of the latency, we may update the log timestamp to order them accurately and to provide a cleaner and more intuitive search experience.
There are so many early serverless adopters and pioneers who many of us in the community know well: AWS heroes, in-demand speakers, and celebrated community organizers with thousands of followers, popular Twitch channels, and full speaking dockets. It’s a fantastic idea to follow these folks because they are known for a reason.We cover them regularly at Stackery!
Business leaders are always looking for ways to leverage technology so that employees can do their best work and meet evolving customer demands. While we settle into the new normal of remote work, mobile technology is taking on a new role in the enterprise, as employees adapt to an increased blending of their professional and personal lives. At ServiceNow, we recently conducted new research to understand how employees are taking advantage of mobile services offered by their organizations.
Many people are working from home (WFH) now and will be for at least the next few weeks. The VPN and TLS connections that remote workers rely on allow for secure access, and although these are not new connection types to monitor, the current WFH situation has created a significant increase in the number of these connections you must monitor. This new WFH scenario has made one thing easier: mobile users are no longer mobile.
As the responsibilities of the Security Operation Center (SOC) continue to increase, SOC teams are experiencing increased demand on their time and resources. Scaling a security team with little resources and funds can prove extremely difficult, especially when the incident response team spends most of their time chasing alerts.
Splunk is a tech company, which regularly gives us exposure to modern development practices, and the ability to implement them with our own technology. We want to share that with you. In this post, as part of a dogfooding series, I sat down with Ram Jothikumar, Head of Cloud Infrastructure & Operations for Observability at Splunk. Ram and I talk about how we support our SignalFx offering at scale, efficiently with resilience and reliability baked in.
