I am honored to be able to talk about Splunk’s investment and commitment to the OpenTelemetry project. I would like to take this opportunity to talk about the latest in the OpenTelemetry community, as well as the instrumentation and data collection distributions available from Splunk. Be sure to read through the whole post, as you will find some roadmap information too!
Databases have always been the backbone of applications – both web and enterprise. Now, more than ever before, you need to know not just overall statistics about your database, but you must identify how database performance interacts with the network, operating system, servers, configuration, and even third party dependencies.
I am very excited that this year’s.conf21was the first.conf where we got to showcase Dashboard Studio, which has come built-in with every Splunk Enterprise and Splunk Cloud Platform release, since 8.2 and 8.1.2103, respectively. I am even more excited to share a packed list of new features in the 8.2.2109 release, which coincides with.conf21! This blog post will highlight a few capability areas we've been heavily focused on that will help you do even more with your dashboards.
As the world watches the UN Climate Conference unfold in Glasgow, the manufacturing industry is under increased pressure to reduce its CO2 emissions. Companies are stepping up to the challenge, but much more remains to be done to keep climate change under control. Digitalization is part of the solution. The Power of Data has much to offer such as environmentally friendly manufacturing, efficient logistics, improved building and energy management and optimized renewable energy production.
When managing distributed environments, we find ourselves challenged with looking for different ways to understand performance better. Telemetry data is critical for solving such a challenge and helping DevOps and IT groups understand these systems’ behavior and performance. To get the most from telemetry data, it has to be captured and analyzed, then tagged to add relevant context, all while being sure to maintain the security and efficiency of user and business data.
Over the past few years, cloud computing has enabled agile, dynamic management of software and hardware components, on-demand. Nowadays, we can define our desired infrastructure in as little as a few lines of code, and we can provision real servers on cloud providers like AWS or Azure. Terraform is an open-source infrastructure-as-code (IaC) tool that has become the de facto solution for provisioning one aspect of those components.
Hi there, I guess that if you are here, you've already read the first part of this series and want some help to quickly get value from your NetFlow data, building trend analysis and advanced analytics with long term data (i.e months), in addition to playing with real-time data. You can take advantage of Splunk’s super flexible schema on read architecture to exploit your real-time data from the very first moment you get the data in.
Software development is getting faster and more complex – frustrating IT operations teams more than ever. So, DevOps gained popularity in order to combat siloed workflows, decreased collaboration and a lack of visibility. While establishing a culture of DevOps has helped teams collaborate better and deliver reliable software faster, DevOps teams don’t necessarily have someone specifically dedicated to developing systems that increase site reliability and performance.
Microsoft Azure is the public cloud computing platform by Microsoft which offers software as a service (SaaS), platform as a service (PaaS) and infrastructure as a service (IaaS). It comprises more than 600 cloud services and supports varied operating systems, databases, and developer tools. And, even better, Splunk On-Call integrates with Microsoft Azure to help on-call teams improve incident response for Azure-based environments.
DevOps-oriented engineers live at the intersection of IT operations and software development – understanding much of what it takes to maintain IT infrastructure while also being able to write code and deploy new services. DevOps-minded teams not only create services – but they also maintain them. A DevOps structure forces teams to take accountability for their applications and infrastructure instead of allowing developers to throw code over the proverbial wall to IT operations.
