OS.app Monitoring

From OS.bee documentation
Jump to: navigation, search

OS.app Monitoring

The monitoring perspective helps to survaile the application. Information about eg. the resource usage, the user logins, the data import and export and other activities is show here.

Table Monitoring

Shows all monitors sorted descending by the last action.

Table Details

Shows the details for the selected monitor entry.

The columns are a subset of the items in the Dialog Detail below.

Dialog Detail

Shows the data of the selected detail entry in the table Details

  • Installation
    The application installation id, a combination of hostname, ip-address and working directory
  • Subcategory
    The referenced subcategory, the detail belongs to
  • recorded on
    date and time the entry has been created
  • status
    the state, the monitored event is in. Eg. in progress, error, warning, ....
  • nr
    the number of the detail entry with respect to the subcategory
  • content
    a brief description of the event or a error description
  • total memory
    the available memory for the application at the moment of the creation if the detail entry in bytes
  • used memory
    the part of the available memory for the application used at the moment of the creation if the detail entry in bytes
  • free memory
    the part of the available memory for the application free at the moment of the creation if the detail entry in bytes
  • used memory(%)
    the part of the available memory for the application used at the moment of the creation if the detail entry in percent
  • free memory(%)
    the part of the available memory for the application free at the moment of the creation if the detail entry in percent
  • CPU
    the part of the available CPU capacity in percent

Chart Resource usage

The line chart displays the resource usage within a timeframe based on all monitor detail entries.

The timeframe can be changed by selecting eg. today, yesterday, last week, ... in the combobox or by changing the content of the date fields.

A large amount of data will result in long response times, so use small time ranges.