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
Service Intelligence uses AI to generate a map of system services, revealing areas that require attention. It surfaces real-time signals for issues such as latency, errors, high traffic, and security anomalies, providing actionable paths for root-cause analysis.
17
+
AI-Driven Investigation uses AI to generate a map of system services, revealing areas that require attention. It surfaces real-time signals for issues such as latency, errors, high traffic, and security anomalies, providing actionable paths for root-cause analysis.
18
18
19
-
The functionality of Service Intelligence is similar to that of the [Services list and map](/docs/apm/services-list-map/), but uses AI to generate the list and map, providing deeper insights and more targeted surfacing for areas of concern.
19
+
The functionality of AI-Driven Investigation is similar to that of the [Services List and Map](/docs/apm/services-list-map/), but uses AI to generate the list and map, providing deeper insights and more targeted surfacing for areas of concern.
20
20
21
-
## What is Service Intelligence?
21
+
## What is AI-Driven Investigation?
22
22
23
-
Service Intelligence leverages an AI generative context engine to analyze your organization's raw log data to provide dynamic observability of the services in your enterprise. It determines real-time environment status and dynamically builds visualizations and instructions to guide troubleshooters. Service Intelligence provides developers, security, and IT operations teams with a single source of truth and remediation recommendations in natural language. Insights are generated by passing a sample of data for the past 15 minutes.
23
+
AI-Driven Investigation leverages an AI generative context engine to analyze your organization's raw log data to provide dynamic observability of the services in your enterprise. It determines real-time environment status and dynamically builds visualizations and instructions to guide troubleshooters. AI-Driven Investigation provides developers, security, and IT operations teams with a single source of truth and remediation recommendations in natural language. Insights are generated by passing a sample of data for the past 15 minutes.
24
24
25
-
Engineers that are responsible for maintaining the uptime of a service would benefit most from Service Intelligence. Depending upon the company and how you manage your operations, these could be development operations (DevOps) engineers, service reliability engineers (SREs), or information technology operations (ITOps) engineers.
25
+
Engineers that are responsible for maintaining the uptime of a service would benefit most from AI-Driven Investigation. Depending upon the company and how you manage your operations, these could be development operations (DevOps) engineers, service reliability engineers (SREs), or information technology operations (ITOps) engineers.
26
26
27
-
## View Service Intelligence
27
+
## View AI-Driven Investigation
28
28
29
-
To open Service Intelligence, in the main Sumo Logic menu of the [**New UI**](/docs/get-started/sumo-logic-ui), select **Service Intelligence**. You can also click the **Go To...** menu at the top of the screen and select **Service Intelligence**. (Service Intelligence is not available in the [**Classic UI**](/docs/get-started/sumo-logic-ui-classic).)
29
+
To open AI-Driven Investigation, in the main Sumo Logic menu of the [**New UI**](/docs/get-started/sumo-logic-ui), select **AI-Driven Investigation**. (AI-Driven Investigation is not available in the [**Classic UI**](/docs/get-started/sumo-logic-ui-classic).)
30
30
31
-
When you first open Service Intelligence, a list of services is displayed to the left, and and a map of the services is displayed to the right. These services are automatically identified by AI analysis of logs in your entire enterprise.
31
+
When you first open AI-Driven Investigation, a list of services is displayed to the left, and and a map of the services is displayed to the right. These services are automatically identified by AI analysis of logs in your entire enterprise.
32
32
33
33
The service list and map visually represents your application environment, giving you a greater understanding of your application architecture, hierarchy, and dependencies between monitored microservices. Health of each microservice is reflected in the color of nodes in the map to help you spot potential problems and bottlenecks in your application infrastructure.
34
34
35
-
<img src={useBaseUrl('img/observability/service-intelligence-initial-map.png')} alt="Service Intelligence list and map" style={{border: '1px solid gray'}} width="800" />
35
+
<img src={useBaseUrl('img/observability/service-intelligence-initial-map.png')} alt="AI-Driven Investigation list and map" style={{border: '1px solid gray'}} width="800" />
36
36
37
37
### View a summary of all service activity
38
38
39
-
Service Intelligence provides an AI-generated summary of all detected service signals and steps to take to remediate issues.
39
+
AI-Driven Investigation provides an AI-generated summary of all detected service signals and steps to take to remediate issues.
40
40
41
41
1. Click the summary button to the right of the services map. <img src={useBaseUrl('img/observability/summary-button.png')} alt="Summary button" width="30" /><br/>A **Summary** panel displays:<br/><img src={useBaseUrl('img/observability/service-intelligence-signals-summary.png')} alt="Signals summary" style={{border: '1px solid gray'}} width="300" />
42
42
1. The summary contains observations, root cause analysis, and next steps. Carefully review the summary to learn actions you can take to address the findings.
@@ -56,38 +56,39 @@ When you select a service in the list or a node in the map that has signals, a s
56
56
***Services with Signals**. Show only services with signals. Normally operating services will not be shown.
57
57
1. Click a service in the list, or a node in the map. A **Summary** panel displays to the right showing signals of interest:<br/><img src={useBaseUrl('img/observability/service-intelligence-service-example.png')} alt="Service summary example" style={{border: '1px solid gray'}} width="800" />
58
58
1. When you click an expand arrow on a signal, it displays an example of a log entry that illustrates the issue. You can use this information to query for logs with similar content.<br/><img src={useBaseUrl('img/observability/service-intelligence-log-example.png')} alt="Log example" style={{border: '1px solid gray'}} width="300" />
59
-
1. Scroll to the bottom of the **Summary** pane to the **Next Steps** section. This section describes concrete steps you can take to remediate issues identified in the selected service.<br/><img src={useBaseUrl('img/observability/service-intelligence-next-steps.png')} alt="Service Intelligence next steps" style={{border: '1px solid gray'}} width="300" />
60
-
1. Open [Copilot](/docs/search/copilot/) to investigate further.
59
+
1. Scroll to the bottom of the **Summary** pane to the **Next Steps** section. This section describes concrete steps you can take to remediate issues identified in the selected service.<br/><img src={useBaseUrl('img/observability/service-intelligence-next-steps.png')} alt="AI-Driven Investigation next steps" style={{border: '1px solid gray'}} width="300" />
1. The legend at the bottom of the screen shows that gold nodes in the map represent services with signals, while blue nodes indicate normal, expected activity. Use the zoom buttons to resize the map.<br/><img src={useBaseUrl('img/observability/service-intelligence-size-buttons.png')} alt="Resize buttons" style={{border: '1px solid gray'}} width="200" />
66
-
1. Click the <img src={useBaseUrl('img/observability/map-view-button.png')} alt="Map view button" style={{border: '1px solid gray'}} width="30" /> button in the upper right to refresh the services list and map. A dropdown menu displays:<br/><img src={useBaseUrl('img/observability/service-intelligence-regenerate-map.png')} alt="Refresh view" style={{border: '1px solid gray'}} width="200" />
67
-
<br/>Select one of the following:
68
-
* **Latest View**. Displays the latest view available. This represents the state of the services in the last 15 minutes.
69
-
* **Historical View**. Displays the next most recent view.
1. Click **Refresh** in the upper right to refresh the services list and map with the most current version.<br/><img src={useBaseUrl('img/observability/service-intelligence-refresh-button.png')} alt="Refresh button" style={{border: '1px solid gray'}} width="100" />
67
+
1. Click **History** in the upper right to select previously-generated versions.<br/><img src={useBaseUrl('img/observability/service-intelligence-history.png')} alt="Services history" style={{border: '1px solid gray'}} width="250" /><br/>To open a version:
68
+
* Select a previous version directly from the list, or
69
+
* Click **Select Date** and **Select Time** to find a specific version.
70
+
<br/>When you select a version, the time and date of the version appears at the top of the page:<br/><img src={useBaseUrl('img/observability/service-intelligence-historical-view-time.png')} alt="Timestamp" style={{border: '1px solid gray'}} width="250" />
71
+
1. Click the buttons on the right to regenerate the services list and map or provide feedback:<br/><img src={useBaseUrl('img/observability/service-intelligence-regenerate-and-feedback-buttons.png')} alt="Regenerate and feedback buttons" width="50" />
72
+
* Click the **Regenerate** <img src={useBaseUrl('img/observability/service-intelligence-regenerate-button.png')} alt="Regenerate button" width="20" /> button to display this dialog:<br/><img src={useBaseUrl('img/observability/regenerate-map.png')} alt="Regenerate map" style={{border: '1px solid gray'}} width="250" />
71
73
1. Select from **Concerns** to provide feedback about the current view, and select from **Variations** to request how AI should automatically adjust regeneration.
72
74
1. Click **Regenerate** to regenerate the service list and map with the last 15 minutes' worth of data.
73
75
:::warning
74
76
It is only necessary to regenerate if it has been longer than 15 minutes since last generation. Do not regenerate multiple times in quick succession, because doing so will not result in new results.
75
77
:::
76
-
1. Click **History** in the upper right to select previously-generated views.<br/><img src={useBaseUrl('img/observability/history.png')} alt="Services history" style={{border: '1px solid gray'}} width="250" /><br/>To open a view:
77
-
* Select a previous view directly from the list, or
78
-
* Click **Select Date** and **Select Time** to find a specific view.
78
+
* Click the **Mark as verified** <img src={useBaseUrl('img/observability/service-intelligence-thumbs-up.png')} alt="Mark as verified button" width="20" /> button to provide feedback that the current services list and map are good.
79
+
* Click the **Needs improvement** <img src={useBaseUrl('img/observability/service-intelligence-thumbs-down.png')} alt="Needs improvement button" width="20" /> button to provide feedback that the current services list and map need work. In the provided box, describe what was unclear, inaccurate, or unhelpful.
79
80
80
81
## FAQ
81
82
82
-
### How is data for Service Intelligence generated?
83
+
### How is data for AI-Driven Investigation generated?
83
84
84
-
Data for Service Intelligence is generated by our AI system leveraging Claude on Bedrock, which is specially trained to provide actionable signal intelligence at the system level. The dataset is sampled periodically every 15 to 30 minutes using our proprietary algorithm, which ensures comprehensive log collection from all services. It effectively deduplicates logs and filters out noise to maintain data quality.
85
+
Data for AI-Driven Investigation is generated by our AI system leveraging Claude on Bedrock, which is specially trained to provide actionable signal intelligence at the system level. The dataset is sampled periodically every 15 to 30 minutes using our proprietary algorithm, which ensures comprehensive log collection from all services. It effectively deduplicates logs and filters out noise to maintain data quality.
85
86
86
87
### What is the confidence level of the large language model (LLM) output?
87
88
88
89
There is a high degree of confidence in the AI outputs as verified through human judging of sample sets. Sumo Logic internally relies on the human judging process and follows that up with tuning the dataset or the prompt.
89
90
90
-
Furthermore, you can provide feedback on the map in the **Regenerate** panel, such as noting it is missing services.
91
+
Furthermore, you can provide feedback, such as noting it is missing services.
91
92
92
93
### What is generated ?
93
94
@@ -118,12 +119,12 @@ No customer data is used to train the model. We use a Foundation Model (FM) with
118
119
119
120
### What sort of instrumentation is required?
120
121
121
-
No instrumentation is required. You can send your structured and unstructured data to Sumo Logic through normal data collection to drive Service Intelligence.
122
+
No instrumentation is required. You can send your structured and unstructured data to Sumo Logic through normal data collection to drive AI-Driven Investigation.
122
123
123
124
### And are log format limitations?
124
125
125
-
There is no limitation on log formats.
126
+
There is no limitation on log formats.
126
127
127
-
### Can you choose which logs to use in Service Intelligence?
128
+
### Can you choose which logs to use in AI-Driven Investigation?
128
129
129
-
No, you can't choose which logs to use in Service Intelligence.
130
+
No, you can't choose which logs to use in AI-Driven Investigation.
0 commit comments