Technology Preview

Table of Contents

Technology Preview

Technology Preview is your gateway into shaping new tools in the AppFirst Product. Tools and features that are still being developed are first released to Tech Preview so we can hear your feedback to incorporate in future versions. Access this feature by clicking the ‘Tech Preview’ button in the top right of the AppFirst Product. (Note: We only make tools available for segments of our users at a time. If the “Tech Preview” is not available, there are no tools available for your account at this moment.)

technology-preview1

The Technology Preview opens in a new tab in your browser. Tools available may vary by user.

The Tools in Technology Preview are actively being developed and will be updated and changing frequently. This means you’ll get the latest and greatest version of the Tool, but also may cause them to be temporarily unavailable or buggy as we work out how to make them more responsive and efficient.

Feedback

Tools in Technology Preview are aimed at getting user input. We would love to hear your feedback on how this is helpful, how it could be improved, and what you like or dislike. Email feedback@appfirst.com or give feedback directly from the tool by clicking the feedback icon in the lower right of the screen.

 

technology-preview2

Server/Device Topology (Tech Preview)

The first tool being released into Technology Preview is the Server/Device Topology.

Server Topology allows users to see, at a quick glance, the health and communication paths of their infrastructure. It was created to show the topology of your Servers and Devices as well as the metrics, processes, and logs associated for a given server or device. You are able to set metric thresholds to quickly see the overall health of a Server and its respective elements.

This was initially designed with two audiences in mind: for operators and for application owners.

Server Topology for Operations

For those responsible for the data center, Server Topology can act as a first alert of pinch-points in your infrastructure. By viewing a quick and simple visual, you can quickly identify systems running hot.

Server Topology for Application Owners

For those responsible for the applications running on top of the infrastructure, Server Topology provides a easy-to-digest view of any application crossover between environments.

In this situation, you can apply server tags by application. For example, let’s say you tag all the servers hosting Zookeeper, used as the management layer of our big data store. In this scenario the environment is designed to be self-contained. Therefore, it is critical that each backend is separate and has no communication between the two. Looking at the example below, Server Topology allows users to quickly identify if there is any crossover, which would indicate a misconfiguration on a server or in a line of code.

server-topology1

View A Topology

Viewing a topology is easy. Simply select a Server Tag to see its topology. If you want to see a specific layout, configure a Server Tag comprised of these servers before here (Admin – Organize Servers) .

The graph shows a topology of your servers and devices. Each server/device is colored according to its health, which is determined based on the thresholds on the right of the screen.

server-topology2

  • Red indicates that a process is exceeding a set threshold
  • Yellow indicates that a process is above eighty percent (80%) of the threshold
  • Green indicated the a process is healthy according to set thresholds
  • Grey indicates that No Process information can be found for that server or device

These colors percolate upwards; that is, if any process exceeds the threshold it becomes red, the server/device will also be red. You will only see green if all of processes associated with that server/device are below all the thresholds. The health of each process is recalculated when new thresholds are set or added. Similarly, when a metric is deleted, the health colors are recalculated using only the remaining thresholds. You can edit the min, max and step values of the thresholds.

Selecting a server or devices populates a table below the topology graph, displaying processes and metrics are causing problems by highlighting the cells that exceed the set thresholds.

  • Click logs to see Logs associated with server
  • Click correlate to see Correlate, allowing you to drill down to very specific granular metrics on a given server
  • Click return

Services (Tech Preview)

The Services tool was created to show the health of your system as well as which process groups (application components) interact with each other. The user is able to set metric thresholds to see the overall health of a Service and its respective components.

Service

A ‘Service’ is a grouping of process groups (also known as application components). The group consists of all the process groups that exist on a collection of servers (the server collection is defined by a server tag) We can either manually create those process groups or detect them automatically with Autodetect.

Topology of Services

The dropdown at the top left allows you to select a Server Tag. Server Tags are set up in Admin – Organize Servers. The mapping of server tags to process groups is done by first getting the servers in the tag and then determining the process groups that have processes running on these servers. The interaction between the processes is found by checking which processes are communicating with each other via socket connections.

services1

The graph shows a topology of your services. Each service is colored according to its health, which is determined based on the thresholds on the right of the screen.
services2

  • Red indicates that a process is exceeding a set threshold
  • Yellow indicates that a process is above eighty percent (80%) of the threshold
  • Green indicated the a process is healthy according to set thresholds
  • Grey indicates that no process information can be found for that server or device

These colors percolate upwards; that is, if any process exceeds the threshold on a designated metric – the process becomes red and the service will also be red. You will only see green if all of processes associated with that service are below all the thresholds. The health of each process is recalculated when new thresholds are set or added. Similarly, when a metric is deleted, the health colors are recalculated using only the remaining thresholds. You can edit the min, max and step values of the thresholds.

Process Table

Once the graph has loaded, you can select a particular Process Group (component) to view the servers that are associated with it.
The Process Table contains metrics such as Average Response Time, Page Faults and No. of Connections by default, while other metrics such as No. of Threads can be added by clicking Add Parameter in the Health Table (on the top right). The health of a particular process is determined by a threshold, which can be set via the window on the right of the graph in the Health Table. The health turns red when the process parameter crosses the set threshold, while yellow represents health over 80% of the threshold, and green is good health (below 80% of threshold). Additional parameters may be added or deleted as per required by specifying the threshold, minimum and maximum values.