stackdriver-tools
stackdriver-tools copied to clipboard
cloudfoundry-community
Stackdriver Nozzle for Cloud Foundry Loggregator, Host Monitoring Agents BOSH Release
Currently the pipeline only tests open source CF. This means the tile installation process is still tested by hand
We should start capturing CI/CD metrics for trend analysis. Things we could grab: * build history * tile filesize * BOSH release filesizes * BOSH release installation timings * Github...
After #237 and #238 we should create a Stackdriver Dashboard to view trends about the project.
It is critical the Stackdriver-Nozzle works well with high volumes of logs. A stress test job should be added to the concourse pipeline. - spins up X CF apps, each...
It would be nice if the stackdriver-nozzle tile deployed a smoke test BOSH release, just like how CF does: https://github.com/cloudfoundry/cf-smoke-tests
The nozzle logs everything to stdout. It should log errors to stderr.
The example app (for Stackdriver debugging) does not deploy to the concourse pipeline.
If the user leaves the firehose username/password fields blank, then the admin creds are used. Should this be an opt-in behavior?
Currently the golint linter is disabled due to lots of missing godoc. The godoc should be updated so it becomes a mandatory process for future development
The `cmd` binaries in the stackdriver-nozzle src directory have no documentation; they are very hidden. A doc should be added explaining the why/what/how of each.
Metadata
Owner
Metadata
Stackdriver Nozzle for Cloud Foundry Loggregator, Host Monitoring Agents BOSH Release