Discover in this demo why 2 Steps is disrupting synthetic monitoring for Mobile in Splunk.
Transcripts available below.
Hi, and welcome to a very quick demo where I'm going to show you 2 Steps, a synthetic monitoring capability that is purpose-built for Splunk. In this demo, I'm going to show you how you can quickly build a synthetic monitoring test on Android without any scripts or embedded agents involved. We're using visual recognition to power the automation and it is as simple as clicking through the application as a user would. In the demo, we're going to have a look at the Google play store and we'll start by clicking on the play store icon. So the first thing that happens is 2 Steps finds the image that we're looking for, and you can see that represented by the blue box here. And the command builder appears the command builder is where I can tell 2 Steps what action to perform. So click on image and some text wait for an image, a mouse-over image click. If the image is visible, et cetera, et cetera. So we're going to label the first part of our test as 'Google Play store'. And we're going to choose the click image icon.
Hit the green button, and you can see the first part of our test is built here. The Google play store is the label and the function is click and the application moves on as you would expect. Next thing that we're going to do is we're going to search for a movie. So again, I click up into the search bar and I change the function this time to enter some text. So we'll call this 'Search'. We'll put in the film that we're looking for, Press the button, and here again, the components of the test are being built. And again, the operating system is moving on as we should expect. Finally, just going to click on the movie that we want. We'll call this 'Shrek'.
There we go. Very, very simple. Let's just save that Test. And the next thing that we're going to do is we're going to add some checkpoints into this test. And a checkpoint is a way where you can concatenate a number of the steps to create different points. So let's just call this one 'search' and maybe we're going to call this one 'movie'. Okay.
Again, we'll save that test. That's a test built. We have four different individual steps and we now have two different checkpoints in that test. And 2 Steps will push all of the performance data for each step into Splunk and also the individual checkpoints as well. The next thing that we'd want to do is schedule the test. So we create a new schedule and here is where we can choose the frequency. So maybe we want to run that every 10 minutes and we have an advanced feature here. If we wanted to run the test Monday to Fr iday nine-to-five, that is where you would manage the advanced schedule options. And finally we have the ability to set up different geographical monitoring nodes. So here we have the example of Melbourne and Sydney, but you may want to have even different office locations or maybe a test that's inside the firewall and outside the firewall.
All of this is, is possible. So that's how you would set up a test. If we have a look at some of the tests that we've built previously, we can have a look at what the results actually look like. So here we can have a look at one of the individual tests and we can see all of the checkpoint performances that are being pushed directly into Splunk different visualizations that are out of the box. The raw event data is available as well. And for web tests, we can actually bring back network timings, which is all of the components that make up a website. If we have looked at the overview, we can check the tests here for Bunnings, which is a website in Australia. Let's have a look at the status. We can see that a couple of these are failed.
Now, one of the unique parts of 2 Steps is not only can we put the performance results into dashboards that look familiar to you. We also have the ability to bring back video replays of every test that we run. So we can see that one of these tests has failed. We can quickly have a look at the test and see a video replay of what went wrong. So in this example, you can see that we've got four different steps. We've got searching for a product, adding a product, the purchase of details and the delivery. All of these steps are running within the SLAs. So 15 seconds where a SLA was 35 seconds, eight seconds, the SLA was 30, et cetera, et cetera, but you can see on the delivery component, it's timed out. It's taken more than 20 seconds and therefore has been deemed a failure. Now it's important to note that all of the SLAs and thresholds are completely configurable. And so our team can help you set that up. So there we have it, a very, very quick demo of 2 Steps on Android. I'm happy to get further into more depth at the right time. But hopefully that helps you understand a little bit more around 2 Steps for Splunk & Android, how easy it is to set up the tasks. As I mentioned, no embedded agents, no scripts is an agentless approach.