HAR File format has chanced for our ASM script monitors - why?

Products

• CA App Synthetic Monitor

Issue/Introduction

We discover that on 07 July 2021 the format of HAR file of one of our monitoring with type script changed.

We are using this HAR file for automatic reporting and with that change we had an error.

For us it's necessary to understand why the content of changed and how recover that.

Before the 12:00 of 07/07/21 the content of file was the follow:

"id":"page_0","title":"Login POST"

After the 12:00 of same day the content is:

"id":"page_0","title":"Page 1"

The difference is in the name of monitor step, before contained the name of step in the monitor, after a generic "Page 1".

 

 

Environment

Release : SAAS

Component : APP SYNTHETIC MONITOR ENVIRONMENTAL

Resolution

Har file format was changed as part of 10.7 release

Requests are now grouped by the transaction controllers.
If there is no transaction controller: they are grouped under single 'Page 1'.

See, before the title was the request name, because the page was containing one request with its name.
And now the page contains all requests inside it and you have to iterate these requests under the 'Page 1'.

The structure was before:
        page
          |_ one request
        page
          |_ one next request
        page
          |_ next request

Now it is: 
        page
          |_ one request
          |_ one next request
          |_ next request

 

The HAR is generated on-the-fly as a transformation of the stored JTL file, and intended for a user-friendly view of the check results. It's not meant for automated processing. For that purpose there is the JTL format, which can be retrieved via API 1.6 /rule_log or APIv3 /log endpoints.