diff --git a/blog-cse/2026-07-31-application.md b/blog-cse/2026-07-31-application.md new file mode 100644 index 00000000000..da0954803fc --- /dev/null +++ b/blog-cse/2026-07-31-application.md @@ -0,0 +1,15 @@ +--- +title: July 31, 2026 - Application Update +image: https://assets-www.sumologic.com/company-logos/_800x418_crop_center-center_82_none/SumoLogic_Preview_600x600.jpg?mtime=1617040082 +keywords: + - insights + - automation +hide_table_of_contents: true +--- + +import useBaseUrl from '@docusaurus/useBaseUrl'; + +We're happy to announce a redesigned Automations page for Insights, featuring a new table view that replaces the previous card view, along with a new side panel for a more streamlined experience. + +The Insights Automations tab displays all associated playbook runs, including the trigger, start time, and current status. Select a playbook to view detailed execution information, switch to a graphical view, and navigate through nested playbooks. +[Learn more](/docs/cse/automation/automations-in-cloud-siem#view-results-of-an-automation). diff --git a/docs/cse/automation/automations-in-cloud-siem.md b/docs/cse/automation/automations-in-cloud-siem.md index 4214e31b2d5..6c26d51f4c2 100644 --- a/docs/cse/automation/automations-in-cloud-siem.md +++ b/docs/cse/automation/automations-in-cloud-siem.md @@ -113,7 +113,7 @@ If an automation is set to run when an insight is created or closed, it runs aut Automations can be run manually from the **Actions** drop-down menu on [insight details](/docs/cse/get-started-with-cloud-siem/about-cse-insight-ui#insight-details-page) pages: -Automations on the Actions menu +Automations on the Actions menu You will see three sections in the **Actions** menu: * **Insight Automation**. Displays a list of all enabled insight automations configured to run manually. @@ -148,40 +148,27 @@ If an automation is set to run when an insight is created or closed, it [runs au When automations run, the results display on insights and entities. 1. Open an insight or entity. -1. Click **Automations** at the top of the screen. The example below shows automations that ran on an insight. Each automation shows its result under **Status**. You can click **View Playbook** to see the playbook that the automation ran.
Automations on an insight - -While viewing an insight or entity, you can [run automations manually](#run-an-automation-manually). +1. Click the **Automations** tab. The example below shows automations that ran on an insight.
Automations on an insight
Each automation shows the following results: + - **Playbook Name**. The name of the associated playbook. + - **Trigger**. What caused the playbook to run. + - **Started on**. The time and date when the automation was run. + - **Status**. The current state of the playbook. + :::note + You may have to manually refresh this screen to see the most current status. + ::: +1. Click a playbook to view it's details.
Automations on an insight + + You can switch to the graphical view by clicking **Graph View** in the upper-right corner: + Playbook status graph + + You can click the front and back arrow to navigate between nested playbooks within a playbook execution.
Automations on an insight ### View enrichments provided by automations When automations run, they can provide enrichments to insights, entities, and signals. 1. Open an insight, entity, or signal with enrichments provided by an automation. -1. Click **Enrichments** at the top of the screen. -1. If threat indicators are set by the [enrichment](/docs/cse/integrations/enrichments-and-indicators), they are displayed. The following example shows a **Malicious** threat indicator.
Threat indicator example - -## View an automation's status - -After [running an automation](#run-an-automation-automatically), you can go to the **Automations** tab for the insight or entity to view the automation's status. - -Automations execution status - -For each automation you will find: -* The time and date when the automation was run. -* The name and description of the associated playbook. -* The playbook’s current status. -* A link to **View Playbook** in the Automation Service UI. - -:::note -You may have to manually refresh this screen to see the most current status. -::: - -If you click **View Playbook**, the Automation Service UI will open to the playbook status page: - -Playbook status - -You can switch to the graphical view by clicking **Graph View** in the upper-right corner: - -Playbook status graph +1. Click the **Enrichments** tab. +1. If threat indicators are set by the [enrichment](/docs/cse/integrations/enrichments-and-indicators), they are displayed. The following example shows a **Suspicious** threat indicator.
Threat indicator example ## Migrate from legacy actions and enrichments to the Automation Service diff --git a/static/img/cse/automations-actions-menu.png b/static/img/cse/automations-actions-menu.png index 52f10ad61fa..b4143fecbdf 100644 Binary files a/static/img/cse/automations-actions-menu.png and b/static/img/cse/automations-actions-menu.png differ diff --git a/static/img/cse/automations-execution-status.png b/static/img/cse/automations-execution-status.png index c19ddcbcb80..30e9ee3a404 100644 Binary files a/static/img/cse/automations-execution-status.png and b/static/img/cse/automations-execution-status.png differ diff --git a/static/img/cse/automations-on-insight.png b/static/img/cse/automations-on-insight.png index 8a40969c6c5..8e2e5996596 100644 Binary files a/static/img/cse/automations-on-insight.png and b/static/img/cse/automations-on-insight.png differ diff --git a/static/img/cse/automations-playbook-status-graph.png b/static/img/cse/automations-playbook-status-graph.png index 62019c58240..1c1e00fe97d 100644 Binary files a/static/img/cse/automations-playbook-status-graph.png and b/static/img/cse/automations-playbook-status-graph.png differ diff --git a/static/img/cse/automations-suspicious-threat-indicator.png b/static/img/cse/automations-suspicious-threat-indicator.png new file mode 100644 index 00000000000..be9aa0f4cc4 Binary files /dev/null and b/static/img/cse/automations-suspicious-threat-indicator.png differ diff --git a/static/img/cse/nested-playbook.png b/static/img/cse/nested-playbook.png new file mode 100644 index 00000000000..0b26a9bccf7 Binary files /dev/null and b/static/img/cse/nested-playbook.png differ diff --git a/static/img/cse/playbook-details.png b/static/img/cse/playbook-details.png new file mode 100644 index 00000000000..33d6eeb1c69 Binary files /dev/null and b/static/img/cse/playbook-details.png differ