Performing Beanviser Operations

Version added 17-Jan-2019| Modified 14-Feb-2019

This page shows the typical layout of the Beanviser user interface and then explains the key Beanviser features and how to use them. 

Screen Layout

Beanviser Screen Layout.png

A brief overview of the different elements of the Beanviser user interface.

A (Function tabs)

Each tab corresponds to a key Beanviser function. For details on each function, see Beanviser Functions

B (Operation tabs)

The operations that you can perform for a Beanviser function.

  • Start - Starts gathering and displaying live data. 

  • Stop - Pause or suspend data collection. 

  • Clear - Clears existing visualization charts from the tab. This option is enabled only when data collection is stopped.

  • Save - Saves the data in the local system. This option is enabled only when data collection is stopped.

    • The data is saved in the [Beanviser_installation_path]/logs directory. The log file name specifies the timestamp and the log type.

  • Import - Imports a saved file from the local system. This data is then displayed as per view. This option is enabled only when Beanviser is not connected to a target (webOS device or emulator).

C (Data modes)

The type of data to be displayed.

  • Live Monitoring (default): Shows live reports for the last one hour, from the time the operation was started.

  • History Data: Shows metrics older than one hour from the current timestamp. In case of log files, it shows logs older than 10000 logs. 

D (Data view)

The data (graph or table) is displayed here. 

Beanviser Functions

A detailed description and usage of each Beanviser function.

Overview

This tab provides a summarized view of all the information collected by the Beanviser. This information is updated in real-time, while measuring is active. 

You can export this information as a PDF file onto the local system.


System CPU

Provides CPU utilized by the system, which is categorized based on:

  • CPU modes (user mode and kernel mode)
  • CPU used by other entities
  • Overall CPU utilization

The above information is displayed in the following graphical views:

  • CPU usage (All cores)
  • CPU usage by each core

How to...

  • General Usage: Start the operation > View the data > Stop the operation  


System Memory

Provides memory consumed by the system. It is categorized based on how much memory is: 

  • Used
  • Free 
  • Shared 
  • Available 
  • Consumed overall
  • Stored in buffer

The above information is displayed in the following graphical views:

  • System memory
  • Swap memory (displays only total, used, and free memory)

How to...

  • General Usage: Start the operation > View the data > Stop the operation


Process CPU

Provides CPU utilized by different processes, which includes: 

  • JS services
  • Native services
  • The app you installed
  • System processes (processes that do not belong to the other groups).

How to...

  • General Usage: Start the operation > View the data > Stop the operation

  • Plot data for specific processes: By default, the graph shows only system-level CPU utilization. To plot for a specific process, select it from the list displayed in the top-right corner. 


Process Memory

Provides memory consumed by different processes, which includes: 

  • JS services
  • Native services
  • The app you installed
  • System processes (processes that do not belong to the other groups).

The above information is displayed using the following metrics:

  • In mega bytes
  • In percentage

How to...

  • General Usage: Start the operation > View the data > Stop the operation

  • Plot data for specific processes: By default, the graph shows only system level CPU utilization. To plot for a specific process, select it from the list displayed in the top-right corner.  


Log Viewer

Use this view to see the platform logs that are available on the webOS device. You can filter the logs based on:

  • Type of logs 
  • Processes 

How to...

  • Usage: Start the operation > View the data > Stop the operation 


LS Monitor

Provides details of traffic going over the webOS service bus (luna bus); similar to a network sniffer that lets you observe HTTP traffic.

How to...

  • General Usage: Start the operation > View the data > Stop the operation

  • Generate the sequence diagram (Available from Beanviser v2.0.0)Once the list is generated, use the Draw Flow option to create a diagram that shows sequence in which service calls are executed. 


Gstreamer

(Available from Beanviser v2.0.0)

Provides the following information:

  • Media debug logs from Gstreamer
  • Metadata from the webOS media server (umediaserver)
  • Dot graph
    • Generates a pipeline diagram for each media instance.
    • Reads information from .dot files and creates graphs that show how different modules of the pipeline communicate with each other. 

How to...

  • Usage: Set the log level > Start the operation > Logs are captured internally > Stop the operation > Captured logs are displayed

Unlike other functions, Gstreamer logs are not immediately displayed on start of the operation. The logs that are captured between the Start and Stop time are displayed, ONLY when the operation is stopped. 
Gstreamer logs are not available on emulator devices. 

Compare Log Files

Allows you to compare log files taken at different times.

  • Logs must be of the same type.
  • For example, you can compare a system CPU log with a system CPU log, but not a system CPU log with a system memory log.
  • To acquire log files, in the relevant tab, click Stop to stop measuring and then click Save to get the log file in the [Beanviser-installation-path]/logs directory. The log file name specifies the timestamp and the log type.

How to...

  • General Usage: Upload the files > View the data


Except as noted, this content is licensed under Creative Commons Attribution 4.0 and sample code is licensed under Apache License 2.0.