Tag Archive for Splunk

AppDynamics, CiRBA, ExtraHop, New Relic, Puppet, SevOne, Splunk, Virtual Instruments, Virtustream, VMware, and VMTurbo have become the new leaders of the new management software industry. These vendors address the new requirements of the software-defined data center and the cloud that are neglected by the blind dinosaur legacy vendors: IBM, BMC, HP, and CA.

The Week That Was

Virtual Thoughts

Virtualization & Cloud Security Podcast

Help Share These Videos

It is that time of year again, when we see all the new toys, tools, ideas, and processes that make up the show called VMworld. This year, quite a few changes in virtualization security will be discussed by VMware and other organizations that work with virtual and cloud environments. One of the key messages will…

Open source alone is not going to kill Splunk. Innovation at the datastore layer may cause Splunk to shift to Hunk over a period of years. Open-source search and dashboarding is not going to kill Splunk either—not until those solutions solve the actual problems that Splunk solves for enterprises worldwide.

In Understanding the Value of Unique Management Data, we pointed out that tools that collect unique data about the performance of infrastructure and applications are more likely to be able to provide you the value you want than tools that just rely on commodity data. In this post, we expose the most frequent marketing lie…

...

Splunk has acquired CloudMeter, giving Splunk the ability to add custom configured slices of network data to its data store. There are likely numerous use cases for Splunk that will be enhanced by this capability, which will solidify Splunk’s position as the leader in the new ecosystem based management software business.

Recently I have had the pleasure of discussing security with a number of cloud providers. Specifically, we talked about what security they implement and how they inform their tenants of security-related issues. In other words, do they provide transparency? I have come to an early conclusion that there are two types of clouds out there:…

In Beware of the Franken-Monitor, we explained how many enterprises ended up with Franken-Monitors and the dangers associated with assuming that the present state of management tools can make the transition into the software-defined data center (SDDC) and the cloud. In Getting Rid of Your Franken-Monitor, we explained how to use green-field islands to put in place new ecosystem-based management stacks with the intent of eventually retiring your legacy management stacks. In this post, we detail how one could deploy one example of such an ecosystem of tools based upon Splunk and the vendors that comprise its ecosystem.

Getting rid of your Franken-Monitor right now is both possible and desirable if you take an incremental approach that slowly phases out the Franken-Monitor while replacing it in new environments with an approach that is flexible and scalable enough to meet your future needs.

If you have a Franken-Monitor, you should get rid of it. If you do not have a Franken-Monitor, you should avoid buying or building one at all costs. The correct approach is to use a strategy and an architecture to procure a set of best of breed solutions that can be easily integrated into a common big data back end datastore.