mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-22 03:01:19 +00:00
Added logging doc intro
Added splunk doc Fixed splunk index page Fixed splunk img Fixed splunk img path Cleaning splunk doc Fixed missing splunk img Cleaned splunk docs Fixed typo Updated splunk docs Fixed img Fixed splunk token img Comestic changes Added troubleshooting Final cleanup One final commit Added logging/splunk doc Added splunk doc Added splunk doc
This commit is contained in:
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: Logging
|
||||
weight: 3725
|
||||
---
|
||||
|
||||
Rancher has the capability to push out cluster and project logs to an external
|
||||
log monitoring tool such as Splunk or a Syslog server. This allows you to be
|
||||
alerted of errors and warnings in your Kubernetes infrastructure.
|
||||
+94
@@ -0,0 +1,94 @@
|
||||
---
|
||||
title: Splunk
|
||||
weight: 3725
|
||||
---
|
||||
|
||||
The following guide will demonstrate how to monitor your container
|
||||
infrastructure using Splunk.
|
||||
|
||||
## Configure HTTP Event Collector
|
||||
|
||||
The first step is to identify what port Splunk is using for the HTTP Event
|
||||
collector. Usually the port is either **8088** or **8089**. HEC is used to
|
||||
send log data from Rancher to Splunk using HTTP or HTTPS.
|
||||
|
||||
Login to Splunk and go to:
|
||||
|
||||
Settings > Data inputs > HTTP Event Collector > **Global Settings**
|
||||
|
||||

|
||||
|
||||
Make sure to click on **Enabled** for all tokens. By default it is set to
|
||||
disabled. This will allow Splunk to collect HTTP Event data sent from Rancher.
|
||||
|
||||
Click on **Save** to update the HEC settings.
|
||||
|
||||
## Generate Token
|
||||
|
||||
This step might not be applicable, if you already have a token. Now we will
|
||||
generate the token that will be used by Rancher to send HTTP Event data.
|
||||
|
||||
- Click Settings > Data inputs > HTTP Event Collector > **New Token**
|
||||
- Click monitor
|
||||
- Select HTTP Event Collector
|
||||
- In the Name field, enter a name for the token (ex. **rancher**)
|
||||
- Click Next
|
||||
- Select the indexe(s) desired (history, main, and summary)
|
||||
- You can also create a new index and add it to the step above
|
||||
- Click Review
|
||||
- Confirm that all settings for the token are what you want
|
||||
- Click Submit to generate the token
|
||||
|
||||
|
||||
|
||||
Congratulations you now are ready to feed Splunk with HTTP Event data. You
|
||||
should see a page like the one below with your generated token. This is the
|
||||
token that will be used in rancher to communicate with Splunk.
|
||||
|
||||

|
||||
|
||||
## Configure Cluster Logging
|
||||
|
||||
In this section we will configure and enable Splunk cluster logging in Rancher.
|
||||
|
||||
- Head on over to local > Tools > **Logging**
|
||||
- Select Splunk
|
||||
- Enter the Splunk endpoint using the port specified for **HEC** (ex. http://splunk-server:8088)
|
||||
- Enter the token generated above (ex. 8da70994-b1b0-4a79-b154-bfaae8f93432)
|
||||
- Enter the Source, name of the token created earlier (ex. **rancher**)
|
||||
- You can also enter an index, this is optional (ex. **main**)
|
||||
|
||||
|
||||
|
||||

|
||||
|
||||
Repeate the same step for Project Logging, if desired. This is not required and is optional.
|
||||
|
||||
## View Logs
|
||||
|
||||
You should now be receiving logging data from your cluster. Head on over to
|
||||
Splunk to view your logs.
|
||||
|
||||
Click on **Search & Reporting**, you should see **Indexed Events** increasing.
|
||||
Click on Data Summary and select the Sources tab.
|
||||
|
||||

|
||||
|
||||
To view the actual logs click on the source that you declared earlier
|
||||
(ex. rancher -> http:**rancher**)
|
||||
|
||||

|
||||
|
||||
## Troubleshooting
|
||||
|
||||
You can use curl to see if **HEC** is listening for HTTP Event Data.
|
||||
|
||||
```bash
|
||||
$ curl http://splunk-server:8088/services/collector/event \
|
||||
-H 'Authorization: Splunk 8da70994-b1b0-4a79-b154-bfaae8f93432' \
|
||||
-d '{"event": "hello world"}'
|
||||
```
|
||||
|
||||
You should see **json** data returnining Success code 0. You should be able
|
||||
to send logging data to HEC. If you received an error, check your configuration
|
||||
in Splunk & Rancher Cluster Logging.
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 92 KiB |
Executable
BIN
Binary file not shown.
|
After Width: | Height: | Size: 76 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 453 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 69 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 690 KiB |
Reference in New Issue
Block a user