Was this page helpful?


Modified 13:48, 3 Nov 2017 by Anonymous? | Page History


    You have to bind a business hierarchy to a scenario through the NMC (Configuration/Scenarios) in order to generate reports via the NRS.
    By default, scenarios are binded on the TEST hierarchy and also all scenarios running on a Newtest Robot For Testing.
    Please Note : ​​No data from a scenario under TEST hierarchy will be trasferred to the DWH. Of course, in NRS reports, there won't be mesurements from this scenario.


    The cumulated duration of unavailability is based on the statusranges (for data ranges state scenario/robots) and is stored in your datawarehouse.
    The starttime of the unavailability holds the cumulated duration of unavailability.

    The "Availability and results trends" table uses two differents methods to display data. The first method uses the successful/degraded/failed executions to calculate the availability and unavailability. The second one uses the satusranges to display the cumulated duration of unavailability.
    The data in this table are not correlated.

    Custom reports

    How can we create the following custom report:

    • Availability indicator (green if >= 98.8%, Red if <98.8%) on the range 8h-20h 5/7
    • Indicator on the number of service disruption (green if <4 and red if >= 4)
    • Indicator on the response time (Green if <= the average response time of the previous month, red in other cases)

    These three applications are achievable with Newtest Business Intelligence (NBI) which is an optional module of Newtest. It allows users to customize and tune reports. To do this you need to define KPIs in the NBI.


    DTL-SUM-EXP-002 report

    Whatever your Newtest server version (2.1.X or 2.2.X), thé NRS doesn't offer you thé opportunity to observe probe state on more than one day.


    DTL-SUM-EXP-002 is the only report which shows you probe's states for a given location.

    However, if you want to see the probe state over a month , you can make a query on your datawarehouse in the StatusAgentLog table.

    The STS_CODE will give you the state of the robot for the period (13 : Running , 10 failed , 11 starting)
    All ranges in state 10 and 11 will give you the unavailability duration.
    You can get the name of the robots by making a join with table object on OBJ_ID.

    We invite you to download our data model available on our extranet site.


    Measures scales on reports

    The scale is automatically adjusted according to thé unavailability rate.


    Number of unavailabilities by business ITO-STA-UNB-001

    This report shows only scénarios unavailability, not unavailability probe duration. You will sée in thèse reports thé failure in business on a day.

    For a given location and business, this report shows, for a transaction and by location, a breakdown by duration of unavailabilities over the period: short (under 15 minutes), medium (15 minutes to 1 hour) and long (over 1 hour).
    This report facilitates quick identification of the elements at the origin of short but frequent unavailabilities that are indicative of instability either of the application or of the scenarios set up to monitor it.


    Error Categories

    To use these reports, you first have to qualify all errors that can be raised by your scenarios.
    To do so, open an NMC console, and go to Operations/Error Labels.
    Then, for each error in each scenario, set a category for the error, choosen between : 


     Custom reports

    Was this page helpful?
    Tag page (Edit tags)
    • No tags
    Page statistics
    8890 view(s), 13 edit(s) and 5874 character(s)


    You must login to post a comment.

    Attach file


    FileSizeDateAttached by 
    No description
    33.27 kB11:37, 29 Oct 2013cedActions