docs(installing/platform-logging): Update docs for off-cluster installs

Author: Jonathan Chauncey

src/installing-workflow/index.md

@@ -41,16 +41,16 @@ the master returned by `helmc target` matches the expected cluster.
 ## Choose Your Deployment Strategy
 
 Deis Workflow includes everything it needs to run out of the box. However, these defaults are aimed at simplicity rather than
-production readiness. Production and staging deployments of Workflow should, at a minimum, use off-cluster storage.
-Which is used by Workflow components to store and backup critical data. Should an operator need to completely re-install
+production readiness. Production and staging deployments of Workflow should, at a minimum, use off-cluster storage
+which is used by Workflow components to store and backup critical data. Should an operator need to completely re-install
 Workflow, the required components can recover from off-cluster storage. See the documentation for [configuring object
 storage](configuring-object-storage.md) for more details.
 
-Workflow may also be configured to use off-cluster persistence for [Postgres](configuring-postgres.md) and
-Redis; a deployment strategy that mirrors the "stateless" clusters from the Deis v1 PaaS.
-
-Last but not least, Workflow may also use a dedicated off-cluster image registry, including Docker Hub, Quay.io, ECR or
-GCR for all container images. Read more about [configuring your registry](configuring-registry.md).
+More rigorous installations would benefit from using outside sources for the following things:
+* [Postgres](configuring-postgres.md) - For example AWS RDS.
+* [Registry](configuring-registry.md) - This includes [quay.io](https://quay.io), [dockerhub](https://hub.docker.com), [Amazon ECR](https://aws.amazon.com/ecr/), and [Google GCR](https://cloud.google.com/container-registry/).
+* [Redis](../managing-workflow/platform-logging.md#configuring-off-cluster-redis) - Such as AWS Elasticache
+* [InfluxDB](../managing-workflow/platform-monitoring.md#configuring-off-cluster-influxdb) and [Grafana](../managing-workflow/platform-monitoring.md#off-cluster-grafana)
 
 ## Add the Deis Chart Repository
 

src/managing-workflow/platform-logging.md

@@ -10,6 +10,38 @@ If the message is from the [Workflow Router](https://github.com/deis/router) we
 
 Logger then acts as a consumer reading messages off of the NSQ logs topic storing those messages in a local Redis instance. When a user wants to retrieve log entries using the `deis logs` command we make an HTTP request from Controller to Logger which then fetches the appropriate data from Redis.
 
+## Configuring Off Cluster Redis
+Even though we provide a redis instance with the default Workflow install. It is recommended that operators use a 3rd party source like Elasticache or similar offering. This way your data is durable across upgrades or outages. If you have a 3rd party Redis installation you would like to use all you need to do is set the following values in `generate_params.toml` within your chart's tpl directory.
+
+* db = "0"
+* host = "my.host.redis"
+* port = "6379"
+* password = ""
+
+You can also provide this environment variables when you run your `helm generate` command instead of editing `generate_params.toml`.
+
+* LOGGER_REDIS_LOCATION="off-cluster"
+* DEIS_LOGGER_REDIS_DB="0"
+* DEIS_LOGGER_REDIS_SERVICE_HOST="my.host.redis"
+* DEIS_LOGGER_REDIS_SERVICE_PORT="6379"
+
+The database password can also be set as a kubernetes secret using the following name: `logger-redis-creds`.
+
+```
+apiVersion: v1
+kind: Secret
+metadata:
+  name: logger-redis-creds
+  namespace: deis
+  labels:
+    app: deis-logger-redis
+    heritage: deis
+  annotations:
+    helm-keep: "true"
+data:
+  password: your-base64-password-here
+```
+
 ## Debugging Logger
 If the `deis logs` command encounters an error it will return the following message:
 

src/managing-workflow/platform-monitoring.md

@@ -38,7 +38,7 @@ We now include a monitoring stack for introspection on a running Kubernetes clus
                        └──────────┘                               
 ```
 
-### Grafana
+## Grafana
 
 Deis Workflow exposes Grafana through the router using [service annotations](https://github.com/deis/router#how-it-works). This
 allows users to access the Grafana UI at `http://grafana.mydomain.com`. The default username/password of
@@ -54,7 +54,10 @@ Deis Workflow monitoring does not currently write data to the host filesystem or
 instance fails, modified dashboards are lost. Until there is a solution to persist this, export dashboards and store
 them separately in version control.
 
-### InfluxDB
+### Off Cluster Grafana
+It is recommended that users provide their own installation for Grafana if possible. The current deployment of Grafana within Workflow is durable across pod restarts which means custom dashboards that are created after startup will not be restored when the pod comes back up. If you wish to provide your own Grafana instance you can either set the `GRAFANA_LOCATION` environment variable when your run `helm generate` or set `grafana_location` in the generate_params.toml.
+
+## InfluxDB
 
 InfluxDB writes data to the host disk, however, if the InfluxDB pod dies and comes back on
 another host the data will not be recovered. We intend to fix this in a future release. The InfluxDB Admin UI is also
@@ -69,7 +72,16 @@ You can choose to not expose the Influx UI and API to the world by updating
 `$CHART_HOME/workspace/workflow-$WORKFLOW_RELEASE/manifests/deis-monitor-influxdb-ui-svc.yaml` and removing the
 following line - `router.deis.io/routable: "true"`.
 
-### Telegraf
+### Off Cluster Influxdb
+To use off-cluster Influx please provide the following values in either the `generate_params.toml` file or as environment variables when running `helm generate`.
+
+* `influxdb_location=off-cluster` - `INFLUXDB_LOCATION=off-cluster`
+* `url = "http://my-influxhost.com:8086"` - `INFLUXDB_SERVICE_URL="http://my-influxhost.com:8086"`
+* `database = "metrics"` - `INFLUXDB_DATABASE="metrics"`
+* `user = "InfluxUser"` - `INFLUXDB_USER="InfluxUser"`
+* `password = "MysuperSecurePassword"` - `INFLUXDB_PASSWORD="MysuperSecurePassword"`
+
+## Telegraf
 
 Telegraf is the metrics collection daemon used within the monitoring stack. It will collect and send the following metrics to InfluxDB: