Present k6 execution logs and console.log() messages in Insights.
We've had a problem with our cloud execution today, and our only recourse (without logs) was to run the full script locally. If we have to do that whenever there is a problem, we are probably better off always running it locally, abandoning cloud execution entirely unless we need load gens in multiple regions.
Any idea when we might see this?
Hey Steve. Yes, it's not a good experience at the moment at all, and we're sorry that customers have had to endure it for such a long time. This feature has been planned as one of the top 3 items to be implemented in Q1.
Same here! But creating a group with part of it's name as the result of the console log line or the error supplied by a 'try catch' statement helped in my case to debug a very specific call. ;)
Anyhow, we're hoping for this feature to be available soon, thanks!
You won't be notified about changes to this idea.