Minimum requirements for GCP instance group collector startup-script

For engineers Troubleshooting
2

Hi @simonbreton so everything below the TELEMETRY section can be removed - this is used for sending analytics information back to us so we can understand how our OS is being used.

I would recommend keeping the Docker section the same:

sudo docker run \
  -d \ # Runs the container in detached mode so will not block the boot handler of the VM
  --name collector \
  --restart always \ # Ensures your container will reboot on fatal exceptions
  --network host \ # Binds to the host network which means you do not end up routing requests via the inbuilt Docker proxy (this can have quite a lot of compute cost if disabled)
  --log-driver gcplogs \ # Ensures logs from the Collector are saved to GCP Monitoring
  -v ${CONFIG_DIR}:/snowplow/config \
  -p 8080:8080 \
  -e 'JAVA_OPTS=-Dorg.slf4j.simpleLogger.defaultLogLevel=info' \
  snowplow/scala-stream-collector-pubsub:2.7.0 \
  --config /snowplow/config/collector.hocon

The host network binding is possibly also why its not working currently.

There seems to be one other bug in there where you have double collector in the config HOCON:

sudo cat << EOF > ${CONFIG_DIR}/collector.hocon
collector collector {

-> Should be

sudo cat << EOF > ${CONFIG_DIR}/collector.hocon
collector {

Hope this helps!

1 Like