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-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@ This is recommended for dev environments only.
79
79
This is recommended for dev environments only.
80
80
* `FIREHOSE_SUBSCRIPTION_ID`: Tags nozzle events with a Firehose subscription id. See https://docs.pivotal.io/pivotalcf/1-11/loggregator/log-ops-guide.html.
81
81
* `FIREHOSE_KEEP_ALIVE`: Keep alive duration for the Firehose consumer.
82
-
* `ADD_APP_INFO`: Enriches raw data with app details.
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
84
* `MISSING_APP_CACHE_INVALIDATE_TTL`: How frequently the missing app info cache invalidates.
85
85
* `APP_CACHE_INVALIDATE_TTL`: How frequently the app info local cache invalidates.
@@ -95,6 +95,9 @@ This is recommended for dev environments only.
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
101
### Please note
99
102
> SPLUNK_VERSION configuration parameter is only required for Splunk version 6.3 and below.
100
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).
@@ -134,11 +137,11 @@ on user authentication.
134
137
```
135
138
136
139
#### Dump application info to boltdb ####
137
-
If in production there are lots of PCF applications(say tens of thousands) and if the user would like to enrich
138
-
application logs by including application meta data,querying all application metadata information from PCF may take some time.
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.
139
142
For example if we include, add app name, space ID, space name, org ID and org name to the events.
140
143
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
141
-
cache the meta data information to the local boltdb file. These queries will introduce load to the PCF system and could potentially take a long time to finish.
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
145
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.
143
146
144
147
Example of how to run the dump application info tool:
0 commit comments