CIRCLE-12738 update to monitoring doc to explain changes for Telegraf custom

Author: Marty Berryman

jekyll/_cci2/monitoring.md

@@ -75,19 +75,25 @@ Enter your DataDog API Key.
 
 After saving you can *verify* that metrics are forwarding by going to the DataDog metrics summary.
 
-#### Custom Metrics *(beta)*
+#### Custom Metrics
 
-A beta feature is to configure Telegraf by going to Replicated Admin > Settings > Custom Metrics and enabling the custom option, for example `https://example.com:8800/settings#custom_metrics`.
-
-![Custom](  {{ site.baseurl }}/assets/img/docs/metrics_custom1.png)
+Custom Metrics via Telegraf configuration file is an alternative to the predefined CloudWatch and Datadog metric sections above. It can also be used instead of those sections for more fine grained control.
 
 ##### Configuration
 
 Configuration options are based on Telegraf's documented output plugins. See their documentation [here](https://github.com/influxdata/telegraf#output-plugins).
 
-For example, if you would like to use the InfluxDB Output Plugin the configuration would look like the following.
-
-![Custom](  {{ site.baseurl }}/assets/img/docs/metrics_custom2.png)
+For example, if you would like to use the InfluxDB Output Plugin you would need to follow these steps;
+1. SSH into the Servics Machine
+2. cd `/etc/circleconfig/telegraf/influxdb.conf
+3. Adding the desired ouputs, e.g. ```
+[[output.influxdb]]
+  url = "http://52.67.66.155:8086"
+  database = "testdb"
+'''
+4. `docker restart telegraf` to restart the container to load or reload any changes.
+
+You may check the logs by running `docker logs -f telegraf` to confirm your output provider (e.g. influx) is listed in the configured outputs.
 
 Additionally, if you would like to ensure that all metrics in an installation are tagged against an environment you could place the following code in your config:
 ```