Part 1 Flashcards
Single instance of Splunk Enterprise handles
Input
Parsing
Indexing
Searching
In most splunk deployments ,——-serve as the primary way data is supplied for indexing
Forwarders
This role will only see their own knowledge objects and those that have been shared with them
User
In most production environments,—-will be used as the source of data input
Forwarders
When zooming in on the event time line; a new search is run
False
In a dashboard, a time range picker will only work on panels that include a ——- search
Inline
These roles can create reports
Power,admin.
To keep from overwriting existing fields with your lookup you can use the —— clause
Outputnew
When using a .csv file for lookups, the first row in the file represents this
Field names
The instant pivot button is displayed In the statistics and visualisations tabs when a ————- search is run
Non-transforming
Forwarders
Require minimal resources
Little impact on performance
Reside on machines where data originates
Main components of splunk
Indexer
Search head
Forwarder
Single instance deployment
Input
Parsing
Indexing
Searching
•proof of concept
Personal use
Learning
Might serve needs of small departments sized environments
Splunk cloud
Subscription service
Index up to 5gb per day up to 15 days
Roles
Determine what a user is able to see, do and interact with
Three main roles
Admin- install apps , create knowledge objects for all users
Power- can create and share knowledge objects for users of an app and do real-time searches
Users- will only see their own knowledge objects and those that have been shared with them
Upload, files only get indexed once .csv
Monitor , files & directories,http, tcp,scripts
Forward, receive data From external forwarders
Local files
Http
Indexes
Directories where data is stored
Having separate indexes
Will make data more efficient
Limits data amount splunk searches
Returns only events froM that index
Multiple indexes allow limiting access by user role.
- you control who sees what data
Separate indexes allow custom retention policies.
(Web data index) (6months)
(Main index)
(Security index)(1 year)
Search and reporting app
Default interface
Knowledge objects
Reports
Dashboards
Commands that create statistics and visualisations are called —-
Transforming commands
By default, a search job will remain active for ——
10mins—- after that a new search will have to be run, to keep for longer you can schedule a report
Shared search Jobs Remain active for —-
7days- and readable to everyone
print results or save to PDF
less load on server, more efficient
Export results Will allow you to export events from the job in —— format
Raw
CSV
XML
JSON
Fast
Smart
Verbose
Fast - field discovery is disabled for this mode - speed over complete
Smart- default , balances
Verbose - complete over speed
Timeline
Clicking and dragging- moves to past or future events
Zoom in- uses your original search job (re execute )
Zoom out- runs a new search job to return newly selected events(re executes )
Deselect- return to original results
Default fields
Host
Source
Sourcetype
Interesting fields
Have values in at least 20% of the events
a
#
String value (written to left)
Numeral (written to left)
Number to right - number of unique values for the field.
=* any results that contain this field action
When you add an event to selected fields list —-
The field will show where the events occurs
You can run more efficient searches by ——
Using fields in them
Field operators
=
!= used with numerical or string values
> =
<
<= numerical values
Time most efficient - less data you have to search , faster splunk will be.
After time ——
Default fields of :
Index
Source
Host
Sourcetype
Most powerful
(The more you tell search , better your results)
Filter
Early , faster
Filter events early in search —-
Indexes
Multiple indexes -users can search only what they need to make searches more efficient
Can also be used to limit access
Can search multiple indexes at same time
Wildcards can also be used for index values
Fields command —-
Include or exclude fields from search results
Fields —-
metafields- host, source, sourcetype, index
internal fields-time and raw
Field extraction - costly part of searching , being able to limit fields extracted can make searches more efficient
Field inclusion- happens before field extraction , can improve performance.
Field exclusion- happens after field extraction, only affecting displayed results
Renaming - once renamed , original name is not available to subsequent search commands( can’t access it with original name ) . New field names will need to be used further down the pipeline
fields command allows you to exclude , include specified fields in your search report.
fields+ before(default) improves performance
fields- after table/display easier to read.
Sort command
String data- sorted alphanumerically
Numeric data- sorted numerically
Transforming commands - into visualisations
raw data in to data table **transforms events into visualisations
Top- most common default 10 results (table-count,%)
Rare- least common
Stats Commands
chart
time chart
geostats
statistical functions: count dc- groups sum- adds avg- min, max, list - writes all values values -specify and write values once *count and sum must be within same pipe
Reports -Power user
Read and write permissions on report (everyone has read access)