Skip to content

Commit 68cf70c

Browse files
committed
Merge branch 'hotfix/env-readme'
2 parents 20a59f9 + 41bffe7 commit 68cf70c

1 file changed

Lines changed: 48 additions & 1 deletion

File tree

README.md

Lines changed: 48 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,7 @@ There are two ways to run this Nozzle:
3434

3535
1. Run as standalone app
3636
2. Run as a tile in Pivotal Cloud Foundry
37+
3. Push as an app in a Clod Foundry instance
3738

3839
### Run as standalone app
3940

@@ -112,10 +113,56 @@ The tile configuration is handled in the 'tile.yml' file. (If you want to modify
112113
* Then add it to the Installation Dashboard to configure it. You should able to configure the settings created in the tile file.
113114
* Update the changes and you should start to see some logs in the Sumo Logic Endpoint defined.
114115
116+
### Push as an app in a Cloud Foundry instance
117+
118+
1. Download the latest release of cloudfoundry-sumologic-nozzle.
119+
```
120+
$ git clone https://github.com/mcplusa/cloudfoundry-sumologic-nozzle.git
121+
$ cd cloudfoundry-sumologic-nozzle
122+
```
123+
124+
2. Utilize the CF cli to authenticate with your PCF instance.
125+
```
126+
$ cf login -a https://api.[your cf system domain] -u [your id] --skip-ssl-validation
127+
```
128+
3. Push cloudfoundry-sumologic-nozzle
129+
```
130+
$ cf push cloudfoundry-sumologic-nozzle --no-start
131+
```
132+
4. Set environment variables with cf cli or in the https://github.com/mcplusa/cloudfoundry-sumologic-nozzle/blob/master/manifest.yml. Example:
133+
```
134+
$ cf set-env cloudfoundry-sumologic-nozzle API_ENDPOINT https://api.[your cf system domain]
135+
$ cf set-env cloudfoundry-sumologic-nozzle SUMO_ENDPOINT https://sumo-endpoint
136+
$ cf set-env cloudfoundry-sumologic-nozzle FIREHOSE_SUBSCRIPTION_ID cloudfoundry-sumologic-nozzle
137+
$ cf set-env cloudfoundry-sumologic-nozzle CLOUDFOUNDRY_USER [your doppler.firehose enabled user]
138+
$ cf set-env cloudfoundry-sumologic-nozzle CLOUDFOUNDRY_PASSWORD [your doppler.firehose enabled user password]
139+
$ cf set-env cloudfoundry-sumologic-nozzle EVENTS LogMessage
140+
$ cf set-env cloudfoundry-sumologic-nozzle NOZZLE_POLLING_PERIOD 15s
141+
$ cf set-env cloudfoundry-sumologic-nozzle LOG_EVENTS_BATCHSIZE 200
142+
$ cf set-env cloudfoundry-sumologic-nozzle SUMO_POST_MINIMUM_DELAY 200ms
143+
$ cf set-env cloudfoundry-sumologic-nozzle SUMO_CATEGORY ExampleCategory
144+
$ cf set-env cloudfoundry-sumologic-nozzle SUMO_NAME ExampleName
145+
$ cf set-env cloudfoundry-sumologic-nozzle SUMO_HOST [some ip]
146+
$ cf set-env cloudfoundry-sumologic-nozzle VERBOSE_LOG_MESSAGES false
147+
$ cf set-env cloudfoundry-sumologic-nozzle CUSTOM_METADATA customData1:customValue1,CustomData2:CustomValue2
148+
$ cf set-env cloudfoundry-sumologic-nozzle INCLUDE_ONLY_MATCHING_FILTER ""
149+
$ cf set-env cloudfoundry-sumologic-nozzle EXCLUDE_ALWAYS_MATCHING_FILTER ""
150+
```
151+
152+
5. Turn off the health check if you're staging to Diego.
153+
154+
```
155+
$ cf set-health-check cloudfoundry-sumologic-nozzle none
156+
```
157+
158+
6. Push the app.
159+
```
160+
$ cf push cloudfoundry-sumologic-nozzle --no-route
161+
```
115162
## Authors
116163
117164
mcplusa.com
118165
119166
## Related Sources
120167
121-
* Firehose-to-syslog Nozzle
168+
* Firehose-to-Syslog Nozzle

0 commit comments

Comments
 (0)