Hello. We're on module five. Talking about *** searches.
Being able to run good searches and *** is probably the most important skill set you can develop in splints.
Not everyone needs to be ableto onboard new data types and modify CONFIG files, but many people in different jobs have to be able to run searches.
Searches can range from extremely simple, too very long and complex.
T. It started with a search. You can log into the *** Web interface
and go to the search and reporting AP.
You can run searches using the command line interface or the rest a p I, but we'll stick to the APP on the Web interface for this course.
Here's a great image from sprint dot com. The illustrates the different parts of the search and reporting out
the example searches will talk about in this video would be entered into the search bar here.
You can easily change the time over here next to the search button, and then, if you want to save your search, you could go up here.
If you want to download the results of your search, you can go down to these search action buttons and click this one here.
You'll probably see the lies SPL a lot in Foreman and forums. It stands for a splint search processing language and means the language around running splint searches.
Swing searches can just be about retrieving events for you to look at interview.
But spilling searches can also be about transforming searches that
transform the retrieve data, such as by performing calculations on them.
There are six general categories of search commands.
We won't go too much into these, but we will use examples that could fit under different categories.
things to remember one running searches,
the more specific, the better. When you have a small environment like we have, running searches across all events isn't such a big deal
in a production environment. It can take a lot of time and processing power to check across lots of events,
good ways to limit searches or by time
in next and other fields.
Limiting the time for him you're searching across is one of the best ways to run an efficient search.
Knowing which index you need a check is a good way, not toys Time and resource is searching unrelated events.
If you're working in an environment you don't manage as possible. You won't be able to search across all indexes because of how your account rolls or set up.
Other fields are also good to narrow down
your search to find just what you're looking for.
Like we learned in the last module,
fields are searchable name and value pairings
specifying known fields and their values can help Bring up the search is you want
There are some things to remember when searching for fields.
Field names are case sensitive, but field values are not.
This means if you're searching for a field name called username and it has a capital you at the beginning, you need to type it this way.
I feel like you for user name equal Sara. It doesn't matter if the S is capitalized on Sara or not.
You can also use wild cards. One searching
if you know, for example,
that the user name you're looking for starts with F A. You could put a wild card. That's that *** tricks or star looking thing at the bottom there
after the 1st 2 letters and you'd be able to get results for things like Samantha and Sandy In addition to Sarah,
a space in the field values,
you should put quotation marks around it. If you're looking for name equal Sarah Smith, you need a format as name equal Sarah Smith with quotation marks.
When searching, you can use Boolean operators like an or and not, for example,
user name. Equal Sarah and machine equals. Host three will bring up results where events match both of these fields.
User name equal Sarah or machine equals host three will bring up events that match either field
user name equal. Sarah does not machine
equals Host tree will bring up events where the user name is Sarah. When the machine does not equal host. Three.
You see an exclamation mark in front of the equal sign. Means does not equal, but it is not the same as using the bully, and not
when you specified that the field does not equal ah value. It requires that
value to show up in search results.
When you're using the not before the field name,
you can get results that don't have that field.
You can also use princesses to group values. For searches,
you can use pipes to transform and filter your retrieved events on my keyboard. I can make a pipe by holding the shift key while pushing the black back flash key.
Some examples of transforming searches might be things like
in next Eagles Windows
Bye Count, and this were able to perform statistics on the results and sort and sort it so that the largest number displays at the top
and the second example
that would show the lists of hosts and then the de Doop command remove duplicate hosts in the results.
There are so many other examples, and we don't have time to go into the mall. In this course, you can do many, many things like look at standard deviations
two lists in a lookup table.
You could look for outliers in your results and evaluate and display events in many different ways.
Getting used to use in
the search language and swung. It takes practice.
Check the supplemental Mitch years for some lists of other useful example. Searches
for a last topic in this video will briefly talk about search modes.
When you run a search you can select the search mode.
If you want faster results, you guessed it. You can run in fast moan. If you want to be able to make sure that you're looking at all event data relating to your search, you can run the slower for both. Smoke search. There's obviously more to this, but that should be enough to get you started.
Who that was A lot in a short amount of time
for our quiz. Please fill in the blank.
If you're searching for a field value with the space in the middle, you should use
and the example of this video. If you're searching for a field name of name and a field value of Sarah Smith with a space in the middle, you should put quotation marks around it.
Great job making it through all of that, and our next video will be using our search knowledge to create alerts