In this video, begin to set up the learning environment for the hands-on exercises in this course.
- [Instructor] Before we get into the details of Splunk, let's talk about the learning environment we'll be using. For the exercises in this course, we'll be using a tool called Vagrant. Vagrant is a simple way of managing virtual machines. Our Vagrant environment includes a couple of lightweight servers that will generate some log data for us to look at. Splunk offers Linux, Windows, and Mac OS versions of their software, so feel free to use the version you prefer, but I'll be installing the Linux version.
So if you wanna follow along with exactly what I'm doing, you should do the same thing. Vagrant is pretty easy to use and you don't really need to know all of the nuances of how it works. If you'd like to learn more about it, I would recommend searching for other Vagrant courses on LinkedIn Learning. You should find what you need. You can download Vagrant from VagrantUp.com. Vagrant manages VMs, but it doesn't actually run them, so we'll need what's called a hypervisor. I'll be using VirtualBox, since it's free and works pretty well with Vagrant.
Go to VirtualBox.org to download it. In the exercise files, you'll find a Vagrant file. This is a simple text file that Vagrant uses for configuring the VMs. Open it up in a text editor and take a look if you'd like. It's really just a Ruby script, with some Vagrant specific configuration options. It describes all of the VMs that we'll be using, and how they'll interact. Copy that file into an empty folder, where you plan to place your exercise files as you work.
Once you have Vagrant and VirtualBox installed, and the Vagrant file in place, open up a shell, and navigate to that directory. I'm using PowerShell on Windows 10, but you can use iTerm if you're on a Mac. Just navigate to the directory where you put the Vagrant file, and type vagrant up. That will initiate the process of setting up these servers. Vagrant needs to download the base OS image, before it can install any software, so it may take a bit of time. Just let that process run in the background, and we'll come back to it for the hands-on exercises.
Before we move on, I wanna mention a couple of potential issues you might run into with Vagrant and VirtualBox. Don't be concerned when you see a lot of output from the vagrant up command. Vagrant is pretty noisy. Any error messages are usually highlighted in red, and Vagrant will generally quit immediately if it runs into an error. If you're on Windows, you might run into an issue where VirtualBox won't run, because something called Hyper-V is enabled. Hyper-V is Microsoft's built-in hypervisor, and although it's technically possible to run VagrantBoxes with Hyper-V, it's a bit too complex for this course.
Unfortunately, you'll need to disable Hyper-V, before you can run another hypervisor, like VirtualBox. Just click on the Start Menu, and type Turn Space Win, and then click Turn Windows Features on and off, and I have to put my fingerprint in, and then down here you can see Hyper-V is one of the options. I've already disabled it, but it might be checked, so just uncheck that box, and click Okay. Another common issue that you might see, is that the virtualization features aren't enabled on your system.
Unfortunately, I can't demo this for you, since it requires rebooting, so I wouldn't be able to do a screen-capture. You need to reboot your system and enter the BIOS menu. To do this you'll need to press a key, before Windows boots, usually it's the Delete key. In that menu, you'll want to enable any virtualization extensions listed. For Intel processors, this is usually called VT-x, and for AMD, it's called AMD-V.
- Installing Splunk
- Filtering search data
- Advanced search syntax
- Creating reports and dashboards
- Creating alerts and actions
- Configuring remote data and multiple data streams