Then @brendanbenson I'm definitely keen to have this switched back to `/insight/`, matching the previous (and documented) behavior.  Previously there was a problem that you could specify any service that matched `/insight/` and it would attempt to use the credentials from those services, regardless of whether it was an Insight service, a Postgresql service, a New Relic service, etc..  Now though, we search a service that both matches `/insight/` and has the appropriate credentials ([which you updated](https://github.com/brendanbenson/java-buildpack/blob/insight_agent_ng2/lib/java_buildpack/framework/spring_insight.rb#L179)) which ensures that we're really getting an Insight service.