Service Virtualization

 View Only
Expand all | Collapse all


Rahul Verma

Rahul VermaNov 22, 2018 10:55 PM

  • 1.  VSE_METRICS_PERIODICS Table Details

    Posted Nov 21, 2018 10:37 AM

    I am trying to get some information from VSE_METRIC_PERIODICS table to genarate some useful report out of it But not clear about below things. Kindly provide details how this works. All Vse metric properties in file are kept as default. 

    Version used: 8.0

    Databse : Derby

    - Is metric value for response time in millisecond and is this averaged for all the trnsactions recived 

    - By default VSE logs in table every 5 minutes . So is it like it only logs trnsaction count recived at that particular time or sum of all the trnsactions recived within that 5 minutes .

    - I want to get the transactions at particular second with response time and genrate something useful.

  • 2.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Nov 22, 2018 10:55 PM

    MarcyNunns deoma03  Kindly help here Bit urgent

  • 3.  Re: VSE_METRICS_PERIODICS Table Details

    Broadcom Employee
    Posted Nov 26, 2018 12:45 PM

    I will have to find out how the data is stored.


    On the second point; the VSE will collect the details in memory and then write out the details to the database every 5 minutes for these tables:


    On the last point; it is suggested to do a test run for at least 15 minutes (so there should be at least 2 * 5 minute intervals covered) and then check the contents of the VSE_METRICS_PERIODICS table. Note that the VS_NAME lists the name of the Virtual Service and PERIOD_TS should show the Time Stamp. You could export the table to a csv file and then further manipulate the rows in a spreadsheet to calculate the average of a specific run. 


    Hope this helps.

  • 4.  Re: VSE_METRICS_PERIODICS Table Details

    Broadcom Employee
    Posted Nov 26, 2018 12:55 PM

    I found a bit more information so might be able to answer your first question:


    PERIOD_LENGTH is the sampling time (300013) would be 30 seconds 13 ms. 

  • 5.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Nov 26, 2018 05:37 PM

    Thanks Mercy. I will test this for Load /Endurance test since we need to get actual trnsactions at micro level . 

    TPS we recieve as of now varies from 50-200 . I will post my observations here . kindly check for more information.

  • 6.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Nov 27, 2018 01:46 PM

    Hi Mercy . I tested one service with 100 Vusers for 15 minutes test . Below i got in Periodics table.




    Test_sv560Response Time130000011/27/2018 22:45
    Test_sv15019Transactions/Second13330000011/27/2018 22:45
    Test_sv740Response Time130001711/27/2018 22:50
    Test_sv14796Transactions/Second13330001711/27/2018 22:50
    Test_sv1000Response Time130001011/27/2018 22:55

    11/27/2018 22:55












    What i can interpret here is that response time is avergaed to 1Millisecond but Avergae response time is noticed in Test Run during statging is different . 


    I want to genearte a report for particular service that shows tps along with Avg response time by fetvhing data from Perioidc count table . How can i do that at micro level . 


    i also tried setting lisa.vse.metrics.sample.interval=1s and 1 minute but that averges to same . just huge records i get that is expected .

  • 7.  Re: VSE_METRICS_PERIODICS Table Details

    Broadcom Employee
    Posted Nov 27, 2018 05:52 PM

    I will do more research.

  • 8.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Nov 28, 2018 11:39 AM

    Thanks Marcy . I will wait for your reply

  • 9.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Nov 28, 2018 02:14 PM

    Hi Rahul,


    Can you share some details on how you are executing your load test? Are you directly load testing the virtual service? Or do you have a system in between your load test and the virtual service? Knowing the architectural setup will help us better understand your performance testing scenario.


    Can you also share how you intend to use the metrics that you're collecting? Is it for auditing purposes where you collect metrics around the virtual services to see how they are being utilized? Or is it for another purpose? If so, please share these details as well, as there may be a better way to do what you're intending to do.

  • 10.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Nov 29, 2018 03:33 PM

    Hi William,


    Here i am directly hitting the virtual service just to check the table data how it behaves. But actual scenario is below what i am trying to achieve.

    We have virtualized different vendor systems to be utilized for performnace testing which are working well enough . Between front end (UI) and Vendor system there is a middleware that hits different vendors (virtulized) and consumes responses . TPS varies from 150-200. in version 8.0 we don't have reporting templates where i can get TPS and response time for each service at microlevel so that we can have something useful for testing team and internal use as well. 

    Then i came across lisa internal tables that stores VSE metrics at service level ,something useful to me. i am able to extract information from tables using SQL queries i have designed as per my requirment but how some fields are storing data is still not clear to generate a useful report and lisa.vse.metrics.sample.interval property is not handling value less than 1 sec if i want metrics sampling after few milliseconds ,

  • 11.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Nov 29, 2018 04:54 PM
      |   view attached

    Hi Rahul,


    Thanks for clarifying the performance test setup/scenario.


    The difference that you see in the response time could be the fact that the virtual service only records how long it takes for it to respond, whereas the average response time in the staged test run result factors in the entire RTT (round trip time), meaning it records from the time the request is sent plus the time for the service to respond plus the actual time for it to be sent back over the wire. So you're comparing two different type of metrics.


    So are you just concerned about the discrepancies of the results from the staged test run results and the VSE database metrics table? Or are you not able to get the level of detail of metrics from the VSE database?


    I'm not sure if there's a way to lower the value of the lisa.vse.metrics.sample.interval property. It might be this way by design as anything lower than 1sec may overload the database connection.


    If you really need a workaround for this, then one suggestion would be to customize the VSM to calculate the information that you're looking for. For example, if you want to collect the response time then you can add a Timestamp filter on the Listen step and on the Responder step and then add a separate scripting step after the Responder step to calculate the response time using the two timestamp values from the listen and responder step.


    I'm attaching a sample project with the above example implementation for your reference.


    Timestamp filter on Listen step:


    Timestamp filter on Responder step:


    Scripting step after the Responder step:


    zip   17 KB 1 version

  • 12.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Nov 30, 2018 11:51 AM

    Hi William,

    Thanks for your reply.

    I would like to get actual metrics that are stored in VSE table for all the services which i am able to get using SQL queries on VSE Periodics table . 

    I have set lisa.vse.metrics.sample.interval=1s to get metrics at each second . But i have same question .


    For METRIC_NAME "Response Time" . Are values stored as milliseconds . I believe those are not in seconds or anyhting else because TPS is much high and Concurrency i have set to 13 . Kindly confirm on this. 

    Below is extract from VSE_PERIODIC table tested for a service keeping Sample interval to 1 second. 


    I would generate a dynamic graph from this that shows TPS and Response time so that we can leverage this for reporting purpose . Also let me know do i need to perform any averaging or anyhting else on this or this data is good to go . 


    Extract from VSE_PERIODCS. Service name and VSE Name is replaced with soemthing dummy. Rest values are actual.


    71005Vse_LinkTest_Service125125Transactions/Second125100111/27/2018 23:41
    71009Vse_LinkTest_Service1125Transactions/Second58107911/27/2018 23:41
    71003Vse_LinkTest_Service8585Transactions/Second85100611/27/2018 23:41
    71004Vse_LinkTest_Service1453Response Time29100611/27/2018 23:41
    71010Vse_LinkTest_Service2461Response Time8107911/27/2018 23:41
    71006Vse_LinkTest_Service492Response Time7100111/27/2018 23:41
    71011Vse_LinkTest_Service149149Transactions/Second149101311/27/2018 23:41
    71007Vse_LinkTest_Service122122Transactions/Second122100511/27/2018 23:41
    71008Vse_LinkTest_Service532Response Time4100511/27/2018 23:41
    71012Vse_LinkTest_Service591Response Time3101311/27/2018 23:41
    71022Vse_LinkTest_Service51Response Time1100011/27/2018 23:41
    71018Vse_LinkTest_Service591Response Time3100111/27/2018 23:41
    71019Vse_LinkTest_Service134134Transactions/Second134100111/27/2018 23:41
    71016Vse_LinkTest_Service341Response Time2100211/27/2018 23:41
    71013Vse_LinkTest_Service140140Transactions/Second140100311/27/2018 23:41
    71017Vse_LinkTest_Service132132Transactions/Second132100111/27/2018 23:41
    71014Vse_LinkTest_Service151Response Time2100311/27/2018 23:41
    71021Vse_LinkTest_Service135135Transactions/Second135100011/27/2018 23:41
    71015Vse_LinkTest_Service130130Transactions/Second130100211/27/2018 23:41
    71020Vse_LinkTest_Service161Response Time1100111/27/2018 23:41
    71030Vse_LinkTest_Service51Response Time1100011/27/2018 23:41
    71023Vse_LinkTest_Service125125Transactions/Second125100111/27/2018 23:41
    71026Vse_LinkTest_Service101Response Time1101011/27/2018 23:41
    71024Vse_LinkTest_Service141Response Time1100111/27/2018 23:41
    71032Vse_LinkTest_Service71Response Time1100711/27/2018 23:41
    71028Vse_LinkTest_Service121Response Time1100211/27/2018 23:41
    71029Vse_LinkTest_Service130130Transactions/Second130100011/27/2018 23:41
    71027Vse_LinkTest_Service129129Transactions/Second129100211/27/2018 23:41
    71025Vse_LinkTest_Service1441Transactions/Second72101011/27/2018 23:41
    71031Vse_LinkTest_Service131131Transactions/Second131100711/27/2018 23:41
    71038Vse_LinkTest_Service61Response Time1100011/27/2018 23:41
    71036Vse_LinkTest_Service51Response Time1100011/27/2018 23:41
    71034Vse_LinkTest_Service131Response Time1100011/27/2018 23:41
    71040Vse_LinkTest_Service51Response Time1101111/27/2018 23:41
    71037Vse_LinkTest_Service129129Transactions/Second129100011/27/2018 23:41
    71041Vse_LinkTest_Service134134Transactions/Second134100011/27/2018 23:41
    71035Vse_LinkTest_Service130130Transactions/Second130100011/27/2018 23:41
    71039Vse_LinkTest_Service137137Transactions/Second137101111/27/2018 23:41




  • 13.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Nov 30, 2018 01:38 PM

    Hi Rahul,


    I'm not familiar with this metrics table and we will probably need confirmation from support/development team MarcyNunns


    But my guess is that the metrics are in milliseconds and the response time is the average response time for the duration, which is 1sec in this case. Again this needs to be further confirmed..

  • 14.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Nov 30, 2018 02:09 PM

    No prob William. She is working on the same . Thank you

  • 15.  Re: VSE_METRICS_PERIODICS Table Details
    Best Answer

    Broadcom Employee
    Posted Dec 06, 2018 12:44 PM




    From the research I have done as well as asking other engineers, all of the data should be stored as milliseconds.



  • 16.  Re: VSE_METRICS_PERIODICS Table Details

    Posted Dec 12, 2018 12:54 AM

    Thanks MarcyNunns . I was able to capture total Count as well . Now i have to play with SQL queries to get meanigfull data . 

    Thanks everyone for your inputs.