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
* updates for v1.2.0 release (#261).
* add hec-retry counter in the error message to know how many retries were needed to deliver a batch.
* updated HEC headers to include telemetry data (appname and appversion).
* update add-app-info configuration to be a list of app metadata fields.
* remove cf_origin and cf_ignored_app fields from app metadata.
* Added memory queue pressure monitoring capability, event received and event sent count.
* add functional tests automation(#264).
Co-authored-by: Rock Baek <[email protected]>
Co-authored-by: Mei Wang <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+12-14Lines changed: 12 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,26 +81,24 @@ This is recommended for dev environments only.
81
81
* `FIREHOSE_KEEP_ALIVE`: Keep alive duration for the Firehose consumer.
82
82
* `ADD_APP_INFO`: Enrich raw data with app info. A comma separated list of app metadata (AppName,OrgName,OrgGuid,SpaceName,SpaceGuid).
83
83
* `IGNORE_MISSING_APP`: If the application is missing, then stop repeatedly querying application info from Cloud Foundry.
84
-
* `MISSING_APP_CACHE_INVALIDATE_TTL`: How frequently the missing app info cache invalidates.
85
-
* `APP_CACHE_INVALIDATE_TTL`: How frequently the app info local cache invalidates.
86
-
* `ORG_SPACE_CACHE_INVALIDATE_TTL`: How frequently the org and space cache invalidates.
84
+
* `MISSING_APP_CACHE_INVALIDATE_TTL`: How frequently the missing app info cache invalidates (in s/m/h. For example, 3600s or 60m or 1h).
85
+
* `APP_CACHE_INVALIDATE_TTL`: How frequently the app info local cache invalidates (in s/m/h. For example, 3600s or 60m or 1h).
86
+
* `ORG_SPACE_CACHE_INVALIDATE_TTL`: How frequently the org and space cache invalidates (in s/m/h. For example, 3600s or 60m or 1h).
87
87
* `APP_LIMITS`: Restrict to APP_LIMITS the most updated apps per request when populating the app metadata cache.
88
88
* `BOLTDB_PATH`: Bolt database path.
89
89
* `EVENTS`: A comma separated list of events to include. Possible values: ValueMetric,CounterEvent,Error,LogMessage,HttpStartStop,ContainerMetric
90
90
* `EXTRA_FIELDS`: Extra fields to annotate your events with (format is key:value,key:value).
91
-
* `FLUSH_INTERVAL`: Time interval for flushing queue to Splunk regardless of CONSUMER_QUEUE_SIZE. Protects against stale events in low throughput systems.
91
+
* `FLUSH_INTERVAL`: Time interval (in s/m/h. For example, 3600s or 60m or 1h) for flushing queue to Splunk regardless of CONSUMER_QUEUE_SIZE. Protects against stale events in low throughput systems.
92
92
* `CONSUMER_QUEUE_SIZE`: Sets the internal consumer queue buffer size. Events will be pushed to Splunk after queue is full.
93
93
* `HEC_BATCH_SIZE`: Set the batch size for the events to push to HEC (Splunk HTTP Event Collector).
94
94
* `HEC_RETRIES`: Retry count for sending events to Splunk. After expiring, events will begin dropping causing data loss.
95
95
* `HEC_WORKERS`: Set the amount of Splunk HEC workers to increase concurrency while ingesting in Splunk.
96
96
* `ENABLE_EVENT_TRACING`: Enables event trace logging. Splunk events will now contain a UUID, Splunk Nozzle Event Counts, and a Subscription-ID for Splunk correlation searches.
97
97
* `SPLUNK_VERSION`: The Splunk version that determines how HEC ingests metadata fields. Only required for Splunk version 6.3 or below.
98
-
* `RLP_GATEWAY_RETRIES`: Number of retries to connect to RLP gateway.
99
-
* `STATUS_MONITOR_INTERVAL`: Time interval for monitoring memory queue pressure to help with back-pressure insights.
100
-
98
+
* `STATUS_MONITOR_INTERVAL`: Time interval (in s/m/h. For example, 3600s or 60m or 1h) for monitoring memory queue pressure. Use to help with back-pressure insights. (Increases CPU load. Use for insights purposes only) Default is 0s (Disabled).
101
99
### Please note
102
100
> SPLUNK_VERSION configuration parameter is only required for Splunk version 6.3 and below.
103
-
For Splunk version 6.3 or below, please deploy nozzle via CLI. Update nozzle_manifest.yml with splunk_version (eg:- SPLUNK_VERSION: 6.3) as an env variable and [deploy nozzle as an app via CLI](#push-as-an-app-to-cloud-foundry).
101
+
For Splunk version 6.3 or below, please deploy nozzle via CLI. Update nozzle_manifest.yml with splunk_version (For example:SPLUNK_VERSION: 6.3) as an env variable and [deploy nozzle as an app via CLI](#push-as-an-app-to-cloud-foundry).
104
102
105
103
**[Tile](https://network.pivotal.io/products/splunk-nozzle/)** only supports deployment for Splunk version 6.4 or above
106
104
@@ -137,11 +135,11 @@ on user authentication.
137
135
```
138
136
139
137
#### Dump application info to boltdb ####
140
-
If in production there are lots of Cloud Foundry applications(say tens of thousands) and if the user would like to enrich
141
-
application logs by including application meta data,querying all application metadata information from Cloud Foundry may take some time.
138
+
If in production there are lots of CF applications(say tens of thousands) and if the user would like to enrich
139
+
application logs by including application meta data,querying all application metadata information from CF may take some time.
142
140
For example if we include, add app name, space ID, space name, org ID and org name to the events.
143
141
If there are multiple instances of Spunk nozzle deployed the situation will be even worse, since each of the Splunk nozzle(s) will query all applications meta data and
144
-
cache the meta data information to the local boltdb file. These queries will introduce load to the Cloud Foundry system and could potentially take a long time to finish.
142
+
cache the meta data information to the local boltdb file. These queries will introduce load to the CF system and could potentially take a long time to finish.
145
143
Users can run this tool to generate a copy of all application meta data and copy this to each Splunk nozzle deployment. Each Splunk nozzle can pick up the cache copy and update the cache file incrementally afterwards.
146
144
147
145
Example of how to run the dump application info tool:
@@ -239,7 +237,7 @@ This topic describes how to troubleshoot Splunk Firehose Nozzle for Cloud Foundr
239
237
240
238
Are you searching for events and not finding them or looking at a dashboard and seeing "No result found"? Check Splunk Nozzle app logs.
241
239
242
-
To view the nozzle's logs running on Cloud Foundry do the following:
240
+
To view the nozzle's logs running on CF do the following:
243
241
244
242
<ol>
245
243
<li>Log in as an admin via the CLI.</li>
@@ -338,8 +336,8 @@ A correct setup logs a start message with configuration parameters of the Nozzle
0 commit comments