You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-apps/logging.md
+23-1Lines changed: 23 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,11 @@ You can view the [log streams](log-streaming.md) in near real-time in the Azure
21
21
22
22
## Container console Logs
23
23
24
-
Container Apps captures the `stdout` and `stderr` output streams from your application containers and displays them as console logs. When you implement logging in your application, you can troubleshoot problems and monitor the health of your app.
24
+
Console logs originate from the `stderr` and `stdout` messages from the containers in your container app and Dapr sidecars. When you implement logging in your application, you can troubleshoot problems and monitor the health of your app.
25
+
26
+
27
+
> [!TIP]
28
+
> Instrumenting your code with well-defined log messages can help you to understand how your code is performing and to debug issues. To learn more about best practices refer to [Design for operations](/azure/architecture/guide/design-principles/design-for-operations).
25
29
26
30
## System logs
27
31
@@ -42,6 +46,24 @@ Container Apps generates system logs to inform you of the status of service leve
42
46
- Deactivating Old revisions
43
47
- Error provisioning revision
44
48
49
+
System logs emit the following messages:
50
+
51
+
| Source | Type | Message |
52
+
|---------|------|---------|
53
+
| Dapr | Info | Successfully created dapr component \<component-name\> with scope \<dapr-component-scope\>|
54
+
| Dapr | Info | Successfully updated dapr component \<component-name\> with scope \<component-type\>|
0 commit comments