m2s funcion error
Opened this issue · 2 comments
2022-11-17T07:31:55Z [Error] Executed 'Functions.m2s' (Failed, Id=f2604744-90db-4230-af9d-4115696d8098, Duration=11ms)
2022-11-17T07:31:55Z [Verbose] Timer for 'm2s' started with interval '00:00:04.9831276'.
2022-11-17T07:31:55Z [Information] Executing 'Functions.m2s' (Reason='Timer fired at 2022-11-17T07:31:55.0012874+00:00', Id=031a699a-c94b-4975-9d10-1ffe94384ed9)
2022-11-17T07:31:55Z [Verbose] Sending invocation id:031a699a-c94b-4975-9d10-1ffe94384ed9
2022-11-17T07:31:55Z [Verbose] Posting invocation id:031a699a-c94b-4975-9d10-1ffe94384ed9 on workerId:298bc4d6-ed57-43c0-b18e-c2d7a4dcaccd
2022-11-17T07:31:55Z [Error] Executed 'Functions.m2s' (Failed, Id=031a699a-c94b-4975-9d10-1ffe94384ed9, Duration=23ms)
2022-11-17T07:31:55Z [Verbose] Timer for 'm2s' started with interval '00:00:04.9657916'.
2022-11-17T07:32:00Z [Information] Executing 'Functions.m2s' (Reason='Timer fired at 2022-11-17T07:32:00.0014169+00:00', Id=1d358f25-78ed-40f6-b5cd-d32aeea3680f)
2022-11-17T07:32:00Z [Verbose] Sending invocation id:1d358f25-78ed-40f6-b5cd-d32aeea3680f
2022-11-17T07:32:00Z [Verbose] Posting invocation id:1d358f25-78ed-40f6-b5cd-d32aeea3680f on workerId:7eaa9a02-152b-4be0-b8ad-7ae76be839c5
2022-11-17T07:32:00Z [Error] Executed 'Functions.m2s' (Failed, Id=1d358f25-78ed-40f6-b5cd-d32aeea3680f, Duration=20ms)
2022-11-17T07:32:00Z [Verbose] Timer for 'm2s' started with interval '00:00:04.9702272'.
2022-11-17T07:32:00Z [Information] Executing 'Functions.m2s' (Reason='Timer fired at 2022-11-17T07:32:00.0007183+00:00', Id=e73a0990-cf5a-46ea-a17a-2aeeda516ac2)
2022-11-17T07:32:00Z [Verbose] Sending invocation id:e73a0990-cf5a-46ea-a17a-2aeeda516ac2
2022-11-17T07:32:00Z [Verbose] Posting invocation id:e73a0990-cf5a-46ea-a17a-2aeeda516ac2 on workerId:298bc4d6-ed57-43c0-b18e-c2d7a4dcaccd
2022-11-17T07:32:00Z [Error] Executed 'Functions.m2s' (Failed, Id=e73a0990-cf5a-46ea-a17a-2aeeda516ac2, Duration=16ms)
2022-11-17T07:32:00Z [Verbose] Timer for 'm2s' started with interval '00:00:04.9755645'.
2022-11-17T07:32:02Z [Verbose] [HostMonitor] Checking worker statuses (Count=1)
2022-11-17T07:32:02Z [Verbose] [HostMonitor] Worker status: ID=298bc4d6-ed57-43c0-b18e-c2d7a4dcaccd, Latency=4ms
2022-11-17T07:32:02Z [Verbose] [HostMonitor] Host process CPU stats (PID 107): History=(0,0,0,0,0), AvgCpuLoad=0, MaxCpuLoad=0
2022-11-17T07:32:02Z [Verbose] [HostMonitor] Host process CPU stats (PID 59): History=(1,1,1,2,2), AvgCpuLoad=1, MaxCpuLoad=2
2022-11-17T07:32:02Z [Verbose] [HostMonitor] Host aggregate CPU load 1
2022-11-17T07:32:02Z [Information] Executing StatusCodeResult, setting HTTP status code 200
This error message doesn't contain useful information to find the problem. I'm usually using the Live metrics feature in Applications Insights. Might be an option for you to get more useful error messages.
@wez3 App Insights live metrics stream is not working.
The message:
Data is temporarily inaccessible. The updates on our status are posted here http://aka.ms/aistatus
