1、 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.AIM 346-SLive logs&prosper:Use AI to make logsa primary observability signalDavid HopeProduct Director Elastic 2025,Amazon Web Services,Inc.or its affiliates.All rig
2、hts reserved.Observability,the broken promiseAlerts without contextDashboards without answersFocus on signal collection,not root cause analysis 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.The result:Burnt out SREsLots of time and effort on fragile pipeline maintenanceDowntime
3、and reactive troubleshooting still an issue 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Because,the“why”has been missingMetricsUnderstanding the“what”Challenges with information densityTracesUnderstanding the“where”Challenges with completeness and invasiveness of instrumentati
4、onLogsAnswers the“why”Information dense and crucial for root cause and investigations 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Why arent SREs using logs more?Messy and unstructuredLot of logs,millions or more of lines All sorts of logs from different systems,no standard for
5、mat 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.user_id=542 status_code=200Server restarted host server_02use_id=175 status_code=500auth_method=oauth status_code=401Easiest signal to collect,no instrumentation needed,100%visibilityRich context:users,devices,regions,server stat
6、us,authLogs are everywhere!Richest context of any signalFoundational to all investigations 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Whats needed to manage logs well?Platform with scalable ingest,analysis,storageAI-driven analysis:extracting insights from log data 2025,Amazo