Attachments

doc/3.2.1/Working With Portal/Service Availability Widget

1. Service Availability Widget

1.1. Purpose

The purpose of the Service Availability widget is to monitor the success rate of defined connections during predefined periods of time. Note that this widget only works for one single Engine. If one'd like to monitor connections on several Engines, one has to create one widget per Engine.

1.2. Creating widget

  • service_availability_config_1.png

  • select the Engine
  • configure the connections you want to monitor (called "services") along with the time period and a target


    Each field could be filtered using the option "keyword" with the following syntax:

     category:keyword

    For example if sources have a category "Location" with keyword "Lausanne" use "Location:Lausanne"


    service_availability_config_2.png

Note that by default a week begins on Monday and ends on Friday. It implies that if the time period is configured on weekdays then Saturday and Sunday will be ignored. The days of a week could be configured using the configuration file of the Portal. This configuration file is named portal-general-config.xml and is in conf directory. The syntax is the following:

<!--each el is a working day of the week and the number correspond to a day
    0 = Sunday, 1 = Monday, ..., 6 = Saturday -->
<weekDays>
  <el>1</el>
  <el>2</el>
  <el>3</el>
  <el>4</el>
  <el>5</el>
</weekDays>

1.3. Using widget

The results are summarized in a table and can be viewed with a "weekly" or "monthly" granularity.

  • service_availability_1.png

Day by day values can be obtained by clicking on the "details" button.

  • service_availability_2.png