BlueXP is now NetApp Console
Monitor and run hybrid cloud data services
Hey, are you one of those customers who are looking to transition from Splunk Classic to Splunk Smart Store or are you just getting started with Splunk Smart Store? No matter where you are in this journey, NetApp has a Splunk certified solution for you. My name is Joseph Kandati Paramble. I'm a solutions architect for the storage grid group and I lead the big data analytics vertical for storage grid. And today I'm here to talk about Splunk Smart Store and why Storage Grid is your go-to solution for Splunk Smart Store. Let's talk about Splunk. First, Splunk is this data indexing tool that lets you ingest large amounts of data into Splunk. And once the data is in Splunk, you can search through that data, analyze that data, gather business insights, and make important business decisions. But what we have seen among our customers is that they buy Splunk licenses for a use case or two, but then they quickly realize that they can use it for several other use cases. And what this means from an infrastructure perspective is that your data exponentially grows within Splunk. So on the right side here I have Splunk Classic. Splunk classic was how customers traditionally deployed Splunk in their environments. Here you have log data getting ingested into Splunk and you have your Splunk users pulling that data from Splunk to analyze that data. Now all the data that is getting ingested into Splunk resides in this tier called indexer tier. Typically what we have seen among customers environment is the search window is usually a week old or maybe a month old or at tops a three months old. But let's say you've been ingesting data into Splunk for about a year. you have all these different grades of data residing in the same tier. This doesn't really make sense economically where you're not using your resources efficiently and secondly when it comes to scaling it gets very challenging and it becomes a very tedious process. So in order to get around this issue Splunk basically introduce something called Splunk Smart Store. Now let's take a look at what uh Splunk smart store is. Splunk smart store basically allows you to decouple compute and storage. This way you can size your compute layer for your search window. So let's say your search window is about a week long. You can size your compute layer or your indexer tier for that one week uh search window. And for the rest of your data, you can basically size your remote store to basically size for capacity.This way you've you're using your resources efficiently where you're sizing your compute for your search and your remote store for your uh capacity and you can scale them independently as your requirements change within your infrastructure.Splunk smart store brings data closer to your compute based on access patterns and data age. This way it gives you gives Splunk users a seamless uh search experience.Now for Splunk Smart Store, we put storage grid to test in order to certify storage grid with Splunk Smart Store and we basically went through some extensive testing by testing uh you know migrating from Splunk Classic to Splunk Smart Store and also did some performance testing as well as failure testing and we found out that there was some key differentiators that we have that our competitors don't. Now let's take a look at what are some of the unique advantages that storage grid has to offer when it comes to Splunk smart store solution. Storage grid has something called true global namespace where you can keep your sites activewhen it comes to multi-sight scenarios and this helps you optimize for performance where you can keep your remote store closer to your compute. This gives Splunk admins a seamless search experience. Next we have something called ILM policy engine which is veryunique to storage grid. And with using the ILM policy engine you can choose to keep or you can decide where and how your data resides within uh storage grid. And what I mean by that is you can have or you can choose to have multiple copies of your Splunk data and you can also erase code that uh Splunk data asyour time as your requirements evolve. And what I mean by that is um you can basically modify these rules uh with time. So let's say youhave a higher performance requirement for the first one month. You can choose to have multiple copies of that Splunk data and then after that one month you can just erase code that Splunk data uh within your within storage grid and reclaim that additional capacity. So this allows you to reuse storage resources efficiently and uh giving you the best bang for your buck. Next is scalability.is very important to Splunk especially given that it's a workload that grows exponentially and dealing with uh downtime is not an option. So for a Splunk admin it is very important tostill be able to scale without any downtime. And the unique thing about storage grid is you can actually scale in terms of performance as well as capacity. So let's say your performancerequirement has increased, you can add performance dense nodes within your storage grid and match that performance requirement or you can basically just scale in terms of capacity by adding expansion shells or nodes within storage grid.Now lastly uh durability is very important where even in terms of failure you want to keep your data available for Splunk searches and within storage grid you have something called dual layer erasia coding sorry dual layer protection where you have protection at the hardware level as well as the software level. Now the hardware layer protection is backed by something called DDP which is very similar to RAID. And at the software level we have something called ILM engine which basically helps you protect your data by either choosing to keep it in you know multiple copies or even eraser coding that data. And because we have this dual layer eraser uh dual layer protection, you can actually you know lose drives you can actually lose nodes in certain scenarios and you can also lose sites in certain scenarios and still have your data available for your searches and as well as ingest. So for a Splunk admin, a lot of these, you know, downtimes andpain points havebeen removed when it comes to Splunk smart store and storage grid has this ability to offer these unique advantages when it comes to remote store. Now that you know why storage grid is your should be your go-to solution for Splunk smart store, I would recommend reach out to your infrastructure team and see how NetApp can help you uh take advantage of uh Splunk Smart Store in this scenario. Thanks everyone [music] for watching this video.
Increase Splunk admins ability to take advantage of SmartStore with efficient indexing, no downtime, and unmatched performance.