Splunk Enterprise Components?

-
Splunk Enterprise Components?

  • Search Head
    • Basically its a graphical user interface and contains all the dashboards, charts etc.
    • Also it enables us to have a solution to query the data according to our needs.
  • Indexer
    • It is the core component which do all the heavy tasks.
    • Major task is to get the data parsed i.e. your data is broken down into events and stored in the indexer.
    • Used by search head to query the data, once the data is queried all the events based on the search are returned back to the search head.
  • Forwarders
    • Universal
      • For understanding sake you can say it as an agent.
      • Collect data from remote data sources and feed it to Splunk indexer.
        • Example: Flat files, logs (web-server, database).
      • Very small daemon (light weight).
    • Heavy
      • Its heavier than universal forwarder.
      • Additional capabilities of parsing and storing the data.
        • Logically storing on heavy forwarder is not recommended.
      • Parsing means masking of the data (removing secret information like passwords etc.), removing unnecessary data (payloads etc).
      • Greatly reduces the load on indexer level.
  • License Manager
    • Keeps tracks of license usage.
    • Alerts Splunk admins, if in case Splunk licence is violated.
  • Deployment Server
    • Helps in managing Splunk infrastructure.
    • It can communicate with every component of Splunk.
  • Cluster Master
    • Helps is managing the cluster.
    • Helps in replicating the data.
    • Monitor health of cluster.

Comments

Post a Comment

Popular posts from this blog

#3 Splunk sub(Commands) [eval, round, trim, stats, ceil, exact, floor, tostring]

-
Image
ROUND: Eval with round takes one or two numeric arguments, returning 'first value' rounded to the amount of decimal places specified in 'second value'.  By default it will remove all the decimals. Example: index=idx_messages sourcetype=linux_logs | eval new_rt= trim ( replace (response_time, "ms.", "")) | stats avg (new_rt) as Average | eval Average= round (Average) Remove all the decimal values. Example: | eval Average= round (Average,3) Rounded the value up-to 3 decimal places. Example: | eval Average= ceil (Average) Round the value up-to the next highest integer. Example: | eval Average= exact (Average) Give the output with maximum possible number of decimal values. Example: | eval Average= floor (Average) Round the value down to the nearest whole integer. Apart from this, there are other functions as well which are used by eval command, for instance pi (), sqrt () etc. TOSTRING: Hel
Read more

#6 Splunk sub(Commands) [fields, rename, replace, table, transaction]

-
FIELDS:  This command helps to keep or remove specified fields from the search results, below command will keep just three fields in your search result. Example: | fields request, rc, pt RENAME:  This command helps to rename field(s), below command will rename a field named as service to serviceType and RC as responseCode Example: | rename service AS serviceType, RC AS responseCode REPLACE:  This command helps to replace the values of fields with another value, below command will replace the values "fetchReport" and "viewReport" as "Report" in "serviceType' field. Example: | replace fetchReport with Report, viewReport with Report in serviceType TABLE: This command helps to format the results into tabular output. Example: | table request, rc, pt TRANSACTION:  This command helps to merge events into a single event based upon a common identifier, below command will create events based on two events i.e. it will fetch the txn-id w
Read more

#2 Splunk sub(Commands) [eval, trim, chart, showperc, stats, avg]

-
Image
TRIM: Basically it helps you to create more meaning full data from existing data i.e. it helps you to remove noise from the results. Example: index=idx_messages sourcetype=linux_logs | eval new_rt= trim (replace( response_time , "ms.", "")) In above example, response_time is an existing field which consists of some unwanted data like "ms." which we don't want. So, by using eval and trim we can remove that unwanted data. If you will notice, above search will create a new field called new_rt which contains our intended results i.e. without "ms." CHART: It basically results your finished data in a table format, further that data can be used to visualize via different mechanism. Example: index=idx_messages sourcetype=linux_logs | chart count by date client useother=f Honestly the example is not so good but I believe, you are able to reach to the crux of it, i.e. it will show you which client on which date made how ma
Read more