0.207.0

Release Highlights

• Operators can provide an HTML template for error messages (See #179)
• Operators can more easily see when routes and endpoints are added or removed from a given gorouter's routing table in the gorouter logs. Noisy and less-helpful logs were changed to debug, more useful logs were changed to info or were added (fixes #172)
  • See Gorouter README section route-table-change-logs for examples of these log messges.

Logs that changed

log-message	description	old log level	new log level
register-route	Logs when gorouter receives a register message from nats. This log was kept around for backwards compatibility. Gorouter receives register messages for every route every 20 seconds. This log does not indicate that the routing table changed. A better log for debugging is "route-registered".	info	debug
unregister-route	Logs when gorouter receives a unregister message from nats. This log was kept around for backwards compatibility. Gorouter receives unregister messages for 10 minutes after a route has been unregistered. This log does not indicate that the routing table has changed. A better log for debugging is "route-unregistered".	info	debug
endpoint-unregistered	Logs when a backend is removed from the table, e.g. an app is scaled down and an app instance is stopped.	debug	info

Logs added

log-message	description	log level
route-registered	Logs when a new route is added to the routing table.	info
route-unregistered	Logs when an existing route is removed from the routing table.	info
endpoint-registered (when the route is new)	Logs when a new backend is added to the table, e.g. an app is scaled up and a new app instance is started.	info

Manifest Property Changes

Job	Property	0.206.0	0.207.0
gorouter	html_error_template	did not exist	configurable and defaults to "" (nothing/empty)