Skip to content

Commit a521925

Browse files
author
Vaughn Dice
authored
Merge pull request #615 from szymonpk/fix-nsq-io-link
fix(managing-workflow): provide proper link to nsq.io
2 parents e935d43 + e4ab885 commit a521925

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

src/managing-workflow/platform-logging.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ The logging platform is made up of 2 components - [Fluentd](https://github.com/d
44

55
[Fluentd](https://github.com/deis/fluentd) runs on every worker node of the cluster and is deployed as a [Daemon Set](http://kubernetes.io/v1.1/docs/admin/daemons.html). The Fluentd pods capture all of the stderr and stdout streams of every container running on the host (even those not hosted directly by kubernetes). Once the log message arrives in our [custom fluentd plugin](https://github.com/deis/fluentd/tree/master/rootfs/opt/fluentd/deis-output) we determine where the message originated.
66

7-
If the message was from the [Workflow Controller](https://github.com/deis/controller) or from an application deployed via workflow we send it to the logs topic on the local [NSQD](nsq.io) instance.
7+
If the message was from the [Workflow Controller](https://github.com/deis/controller) or from an application deployed via workflow we send it to the logs topic on the local [NSQD](http://nsq.io) instance.
88

99
If the message is from the [Workflow Router](https://github.com/deis/router) we build an Influxdb compatible message and send it to the same NSQD instance but instead place the message on the metrics topic.
1010

0 commit comments

Comments
 (0)