The Netsil Application Operations Center (AOC) generates auto-discovered application maps for unprecendented visibility into applications. Nodes on the application topology map represent groups of instances and links between the nodes represent network interactions. Instances can be pods, containers or hosts, i.e VMs or bare metal OS. Once collectors are installed on hosts, users can create multiple maps to visualize the application from multiple perspectives.

Create New Map

The Maps tab shows a list of static (out-of-the-box) maps and custom (user-defined) maps. Maps Tab Pre-canned and Custom Maps

We will use a custom map named "Kubernetes Pods" in this guide.

Map An Application Topology Map

  • Filters: Filter instances that will be included in the groups on the map.
  • GroupBy: Infrastructure tags used to group instances.
  • Time Window Slider: Select the time window for which the map is populated. Default "end-time" is "now" which provides real-time updates on the map.
  • Save or Discard changes made while editing a map
  • Map Navigation - Recenter, Zoom-in and Zoom-out

Using Filters and Groupby for Creating Map

Filters and GroupBy rules offer an extensive list of cloud, host, pod and container properties for filtering and grouping instances on the map.

For example, instance_type refers to the instance types supported in the AOC. Instance_type can be container, pod,host or remote. Remote refers to entities where AOC collector is not installed. Also note that there are cloud specific tags such as region and framework specific tags such as kube_*.

Maps can group the instances using various infrastructure tags. As shown in the image below, instances are grouped by host_name. host-name Instances grouped by host names

We can use filters to select specific instances. In the image below, we have filtered by host_name and selected only the gke* (Google Kubernetes Engine) hosts. (Note that filters support regex)

gke Set filters value for host names

And finally we can futher subgroup to see the kubernetes pods. Just add another GroupBy criteria using pod_name.

pods-map Kubernetes Pods map

Single Click View for Nodes

single-click-view Clicking on any node in the map will show a summary view containing the following:

  • Metrics : This includes out-of-the-box dashboards for infrastructure, network flows and the type of service (HTTP,DNS,MySQL, etc).
  • Instances : List of instances that are on this node
  • Status : of any alerts configured and triggered for this group. Note that in order to set the alert and see it triggered on the map, the alert groups must be at least as specific as groups on the map. You can read more about that in the Alerts Documentation.

Clicking on the links between any two nodes in topology map will provide insights on the network interactions among services. This includes valuable metrics such as throughput, error rates, latency, etc. link-view

Table View

The Table View is an alternate tabular view for the nodes in the map. The nodes are conveniently organized under protocol tabs such as HTTP,DNS, MySQL, etc., and also include Network Flows section for the TCP/IP communication details. table-view

Join our Public Slack Channel if you have any questions.