#Disclaimer

This project is based on https://github.com/vmware-archive/firehose-to-loginsight

Since v0.0.10 we stop supporting username and password for authentication.

Please use ClientId and ClientSecret.

firehose-to-loginsight

Firehose nozzle to pull events and send to LogInsight ingestion API inspired and leverages firehose-to-sylog

Options

usage: main --api-endpoint=API-ENDPOINT [<flags>]

Flags:
  --help                       Show context-sensitive help (also try --help-long and --help-man).
  --debug                      Enable debug mode. This enables additional logging
  --api-endpoint=API-ENDPOINT  Api endpoint address. For bosh-lite installation of CF: https://api.10.244.0.34.xip.io
  --doppler-endpoint=DOPPLER-ENDPOINT  
                               Overwrite default doppler endpoint return by /v2/info
  --subscription-id="firehose-to-loginsight"  
                               Id for the subscription.
  --client-id="admin"          Client ID.
  --client-secret="admin-client-secret"  
                               Client Secret.
  --skip-ssl-validation        Please don't
  --fh-keep-alive=25s          Keep Alive duration for the firehose consumer
  --events="LogMessage"        Comma separated list of events you would like. Valid options are ContainerMetric, CounterEvent, Error, HttpStartStop, LogMessage,
                               ValueMetric
  --boltdb-path="my.db"        Bolt Database path
  --cc-pull-time=60s           CloudController Polling time in sec
  --extra-fields=""            Extra fields you want to annotate your events with, example: '--extra-fields=env:dev,something:other
  --insight-server=INSIGHT-SERVER   Default to "data.mgmt.cloud.vmware.com" 
                               log insight server address
  --insight-server-port=443   log insight server port
  --insight-server-token="Token here"   log insight server port
  --insight-reserved-fields="event_type"  
                               comma delimited list of fields that are reserved
  --insight-has-json-log-msg   app log message can be json
  --concurrent-workers=50      number of concurrent workers pulling messages from channel
  --noop                       if it should avoid sending to log-insight
  --max-idle-connections=100   Max http idle connections
  --max-idle-connections-per-host=100  
                               max idle connections per host
  --idle-connection-timeout-seconds=90  
                               seconds for timeout
  --logs-buffer-size=10000     Number of envelope to be buffered
  --enable-stats-server        Will enable stats server on 8080
  --orgs=""                    Forwarded on the app logs from theses organisations' example: --orgs=org1,org2
  --ignore-missing-apps        Enable throttling on cache lookup for missing apps
  --version                    Show application version.

** !!! --events Please use --help to get last updated event.

#Endpoint definition

We use gocf-client which will call the CF endpoint /v2/info to get Auth., doppler endpoint.

But for doppler endpoint you can overwrite it with --doppler-address as we know some people use different endpoint.

Event documentation

See the dropsonde protocol documentation for details on what data is sent as part of each event.

Caching

We use boltdb for caching application name, org and space name.

We have 3 caching strategies:

• Pull all application data on start.
• Pull application data if not cached yet.
• Pull all application data every "cc-pull-time".

To test and build

    # Setup repo
    go get github.com/pivotalservices/firehose-to-loginsight
    cd $GOPATH/src/github.com/pivotalservices/firehose-to-loginsight
    glide install --strip-vendor —strip-vcs
    # Test
	ginkgo -r .

    # Build binary
    go build

Run against a bosh-lite CF deployment

    go run main.go \
		--debug \
		--skip-ssl-validation \
		--api-endpoint="https://api.10.244.0.34.xip.io"

Parsing the logs with Logstash

logsearch-for-cloudfoundry

Push as an App to Cloud Foundry

Create doppler.firehose enabled user

uaac target https://uaa.[your cf system domain] --skip-ssl-validation
uaac token client get admin -s [your admin-secret]
uaac client add firehose-to-loginsight \
      --name firehose-to-loginsight \
      --secret [your_client_secret] \
      --authorized_grant_types client_credentials,refresh_token \
      --authorities doppler.firehose,cloud_controller.admin_read_only

Download the latest release of firehose-to-loginsight from GITHub releases (https://github.com/mohitsharma-in/firehose-to-loginsight-cloud/releases)

chmod +x firehose-to-loginsight-cloud

Utilize the CF cli to authenticate with your PCF instance.

cf login -a https://api.[your cf system domain] -u [your id] --skip-ssl-validation

Push firehose-to-loginsight.

cf push firehose-to-loginsight-cloud -c ./firehose-to-loginsight-cloud -b binary_buildpack -u process --no-start

Set environment variables with cf cli or in the manifest.yml.

cf set-env firehose-to-loginsight-cloud API_ENDPOINT https://api.[your cf system domain]
cf set-env firehose-to-loginsight-cloud INSIGHT_SERVER [Your Log Insight IP. Default to data.mgmt.cloud.vmware.com]
cf set-env firehose-to-loginsight-cloud INSIGHT_SERVER_PORT [Your Log Insight Ingestion Port, defaults to 443]
cf set-env firehose-to-loginsight-cloud INSIGHT_SERVER_TOKEN [Your Log Insight Token]
cf set-env firehose-to-loginsight-cloud LOG_EVENT_TOTALS true
cf set-env firehose-to-loginsight-cloud LOG_EVENT_TOTALS_TIME "10s"
cf set-env firehose-to-loginsight-cloud SKIP_SSL_VALIDATION true
cf set-env firehose-to-loginsight-cloud FIREHOSE_SUBSCRIPTION_ID firehose-to-loginsight
cf set-env firehose-to-loginsight-cloud FIREHOSE_CLIENT_ID  [your doppler.firehose enabled user]
cf set-env firehose-to-loginsight-cloud FIREHOSE_CLIENT_SECRET  [your doppler.firehose enabled user password]

Push the app.

cf push firehose-to-loginsight-cloud --no-route

Contributors

• Caleb Washburn
• Ian Zink
• Mohit Sharma