Enhancement: Capture and report back the log statements from journey script.

[ZaidMomin1]

Hi Team,

In recent past we were trying to check if there's a way to capture and report back the log statements from journey script to observability uptime monitor and there's was discussion about the same here.

Basis the discussion it was concluded to open up an enhancement request for the same.

Thanks,
Zaid

[vigneshshanmugam]

@ZaidMomin1 Thanks for opening the Enhancement request. Just for myself to clarify, Do you want

1. Log statements from the Journey script to be associated with the Monitor OR
2. Log statements from the Browser window which is the URL under test. If this was the case, we do collect those log statements, but will be reported only for failed journeys to save on storage.

For no 1, we would need to implement something like this #188

[ZaidMomin1]

Hi @vigneshshanmugam

Apologies for the extremely delayed response.

Consider I have a below step which calls the wrapper methods like navigateTo, waitForElementToBeVisible etc and displays the message App successfully launched once everything is done (this is a simple example)

step('Launch app', async () => {
        let joinNowButton = '#joinNow'
        await navigateTo(page, url)
        if (!(await isElementVisible(page, joinNowButton)))
            await reloadPage(page)
        await waitForElementToBeVisible(page, joinNowButton)
        let joinNowButtonText = await getElementInnerText(page, joinNowButton)
        expect(joinNowButtonText).toBe("JOIN NOW")
       console.log(`App successfully launched`)
    });

Once this step is executed on the monitor, the way script executed is captured it would be great if the console logs are displayed on the monitor as well.

I'm assuming issue-188 that you mentioned would solve this problem.

[paulb-elastic]

@vigneshshanmugam would #817 help with this (looks like we're including console.log in those too, assuming there aren't too many messages in total)?

[vigneshshanmugam]

would #817 help with this (looks like we're including console.log in those too, assuming there aren't too many messages in total)?

#817 only captures the browser log messages, we don't associate all the console logs from the Journey scripts itself.

Once this step is executed on the monitor, the way script executed is captured it would be great if the console logs are displayed on the monitor as well.

We don't have this capability right now, but we capture raw logs from the STDOUT and STERR, but don't use show them on the UI under the monitor. Yeah #188 is the way to go to get this associated with the step level information, We will update this issue once we start working on this. Thanks!

[shahzad31]

@ZaidMomin1 @vigneshshanmugam wouldn't using page.evaluate solve this use?

i mean using it

    await page.evaluate(() => {
      console.log('test lgog');
    });