### Routes Resource
Routes let you configure logspout to hand-off logs to another system using logspout adapters, such as syslog.
#### Creating a route
Takes a JSON object like this:
The main fields are `adapter` and `address`. The field `options` is passed to the adapter. There are three filter fields: `filter_name`, `filter_sources`, and `filter_id`. These let you limit which containers or types of logs to route. Use `filter_id` to limit to a particular container by ID. Use `filter_name` to match against container names. These can include wildcards. Use `filter_sources` to limit to `stdout` or `stderr`, or soon `syslog`.
To route all logs of all types on all containers, don't specify any filter values.
The `append_tag` field of `options` is adapter specific to `syslog`. It lets you append to the tag of syslog packets for this route. By default the tag is `<container-name>`, so an `append_tag` value of `.app` would make the tag `<container-name>.app`.
And yes, you can just specify an IP and port for `address`, but you can also specify a name that resolves via DNS to one or more SRV records. That means this works great with [Consul](http://www.consul.io/) for service discovery.
#### Listing routes
Returns a JSON list of current routes:
#### Viewing a route
Returns a JSON route object:
#### Deleting a route