Customizable external services

[2opremio]

Leftover from #1863 . Right now we only identify Amazon and Google (googleapis.com) services but users may want to configure and extend how external services are identified.

Ideally we will want to introduce this in the Scope UI, but this requires persistent user-configuration options in the app (which is suitable for but not yet implemented in Weave Cloud). As an alternative @rade suggests adding it to the probes.

[rade]

Ideally we will want to introduce this in the Scope UI.

Not sure about "ideally"; IMO the probes are perfectly fine place to configure this information.

[Preskton]

+1 - would be nice if this was configured by something in the UI, either at an account, cluster, user, or other level.

If I were to write this as a story, it might look something like:

As an operations manager, I would like the Scope UI to allow me which hostnames are considered external services so that communication with those endpoints are grouped into a separate set, allowing me to better understand the flow of outbound traffic to known/expected hosts.

Today, most of my external endpoints get grouped into a big bucket called "The Internet", which makes it difficult for me to know if these are expected (e.g. connections to Azure) or anomalies.

Some acceptance criteria for consideration:

• users should be able to configure this at either an account or cluster level
• should be able to add one or more hostname patterns (regexp/simple pattern matching) to a named group (ex: "Dev APIs" => *.dev.myapihost.blah)
• any outbound communication flows to hosts that match the above pattern should show up as one icon on the map
• should be able to specify a custom icon for the group (nice to have)

[errordeveloper]

This came up a few more times in recent conversation I've had with Scope users.

[joequery]

Hi there!

@Preskton 's acceptance criteria would meet many of our needs with Scope. We would like to visualize not just communications between containers, but also traffic with external hosts. This would allow us to visualize containers communicating with databases or external APIs. Having all outboud communication categorized only as "The Internet" is limiting in terms of visualizations capabilities.