You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -111,6 +111,8 @@ This is recommended for dev environments only.
111
111
* `STATUS_MONITOR_INTERVAL`: Time interval (in s/m/h. For example, 3600s or 60m or 1h) for Enabling Monitoring (Metric data of insights with in the connectors). Default is 0s (Disabled).
112
112
* `SPLUNK_METRIC_INDEX`: Index in which metric data will be ingested when monitoring module is enabled
113
113
* `SELECTED_MONITORING_METRICS`: Name of the metrics that you want to monitor and add using comma seprated values. List of the metrics that are supported in the metrics modules are given below
114
+
* `REFRESH_SPLUNK_CONNECTION`: If set to true, PCF will periodically refresh connection to Splunk (how often depends on KEEP_ALIVE_TIMER value). If set to false connection will be kept alive and reused. (Default: false)
115
+
* `KEEP_ALIVE_TIMER`: Time after which connection to Splunk will be refreshed, if REFRESH_SPLUNK_CONNECTION is set to true (in s/m/h. For example, 3600s or 60m or 1h). (Default: 30s)
114
116
115
117
__About app cache params:__
116
118
@@ -276,7 +278,7 @@ FORMAT = new_index
276
278
<p class="note"><strong>Note:</strong>Moving from version 1.2.4 to 1.2.5, timestamp will use nanosecond precision instead of milliseconds.</p>
277
279
278
280
279
-
__Monitoring(Metric data Ingestion):__
281
+
## __Monitoring(Metric data Ingestion):__
280
282
281
283
| Metric Name | Description
282
284
|---|---
@@ -301,6 +303,15 @@ __Monitoring(Metric data Ingestion):__
301
303
302
304
<p class="note"><strong>Note:</strong>Select value Rate(Avg) for Aggregation from Analysis tab on the top right.</p>
303
305
306
+
### Routing data through edge processor via HEC
307
+
Logs can be routed to Splunk via Edge Processor. Assuming that you have a working Edge Processor instance, you can use it with minimal
308
+
changes to nozzle configuration.
309
+
310
+
Configuratino fields that you should change are:
311
+
* `SPLUNK_HOST`: Use the host of your Edge Processor instance instead of Splunk. Example: https://x.x.x.x:8088.
312
+
* `SPLUNK_TOKEN`: It is a required parameter. A token used to authorize your request, can be found in Edge Processor settings. If your
313
+
EP token authentication is turned off, you can enter a placeholder values instead (e.x. "-").
314
+
304
315
## <a id='walkthrough'></a> Troubleshooting
305
316
This topic describes how to troubleshoot Splunk Firehose Nozzle for Cloud Foundry.
306
317
@@ -508,7 +519,7 @@ $ chmod +x tools/nozzle.sh
508
519
Build project:
509
520
510
521
```
511
-
$ make VERSION=1.3.0
522
+
$ make VERSION=1.3.1
512
523
```
513
524
514
525
Run tests with [Ginkgo](http://onsi.github.io/ginkgo/)
0 commit comments