Monitoring App Builder applications with Log Forwarding
summary
App Builder adds configurable log forwarding from Adobe Runtime so backend function logs stream into third‑party systems instead of only the CLI aio app logs view; current beta sends to Splunk (host, port, index, token) and Azure Log Analytics. CLI today only shows recent activations and keeps logs seven days, missing many successful synchronous requests; forwarded logs appear in Splunk, are searchable by activation ID, show stdout/stderr and timecharts, and demoed successfully with no application performance impact.
AI-written summary · about
chapters (16)
- 0:00Introduction to speakers
- 1:26What is App Builder
- 2:49App Builder architecture
- 4:38Current log access methods
- 8:34Log forwarding explained
- 10:00Benefits of log forwarding
- 13:27Supported log destinations
- 14:51Beta and GA timeline
- 15:34Demo setup
- 19:28Production namespace setup
- 21:33Configuring Splunk destination
- 22:40Triggering error scenario
- 23:00Viewing logs in Splunk
- 25:52Demo wrap-up
- 26:12Accessing log forwarding beta
- 27:18Q&A and closing
related talks
31mThe Long and Winding Road to Application Logging [A]
44mEfficient Android app monitoring
20mFast log management for your apps
38mLogging, Instrumentation, Dashboards, Alerts
28mLogfire - Uncomplicated Observability
16mSession: Scale Your App! Applifter's OS Turns Insights Into Installs
29mApplication Logging
45mLogging, Instrumentation, Dashboards and Alerts - for Developers