Not Monitored
Tag not monitored by Microsoft.
37,794 questions
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I expect the following to log in order from top to bottom but results show that they're not in order
// Azure function handler
export const browseIssues = context => {
context.log.info({ a: 'first object', b: { q: 'test 1' } });
context.log.info({ a: 'second object', b: { q: 'test 2' } });
context.log.info({ a: 'third object', b: { q: 'test 3' } });
context.log.info(JSON.stringify({ a: 'first string', b: { q: 'test 1' } }));
context.log.info(JSON.stringify({ a: 'second string', b: { q: 'test 2' } }));
context.log.info(JSON.stringify({ a: 'third string', b: { q: 'test 3' } }));
context.log.info('first simple string');
context.log.info('second simple string');
context.log.info('third simple string');
}
Results
Here's a bare bone repository where this is reproducible
https://github.com/keidyz/azure-function-logging-issue
Any ideas on why this is happening and how to remedy this? Issue seems to be confined in azure context's log as console.log logs synchronously.
Node version: v18.12.1