DOCS-1777 - Document multi-notification support for Scheduled Searches

[JV0812]

Purpose of this pull request

This pull request documents the new multi-notification capability for Scheduled Searches: you can now add up to 10 alert types (mixing Email, Webhook, and other alert types) to a single Scheduled Search instead of choosing just one, with each alert configured independently and all sharing the same trigger condition. Updates Step 6 of the "Create a Scheduled Search" procedure and notes that existing single-alert schedules are unaffected.

Select the type of change

• Minor Changes - Typos, formatting, slight revisions
• Update Content - Revisions, updating sections
• New Content - New features, sections, pages, tutorials
• Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/DOCS-1777

[ashutosh-kumbhaj-sumo]

Suggestions :-

1. "Alert types" vs "notifications" terminology: The blog post says "up to 10 alert types" which could be misread as 10 distinct types. The docs clarify you can add "multiple Email alerts with different recipients" which is good — but the blog post could benefit from saying "up to 10 notifications" instead of "10 alert types" to avoid confusion.
2. The feature introduces a new notifications array in the API (Content Sync / Log Searches API). There's no mention of the API changes in this docs PR. Does API docs live elsewhere? or are they not required?

Rest looks good to me.

[JV0812]

Thanks for the review, @ashutosh-kumbhaj-sumo!

1. Fixed — the release note now says "up to 10 notifications" instead of "10 alert types" to avoid the distinct-types misread (d4f12f182).
2. On the API doc question: no change needed here. docs/api/log-searches.md is a landing/reference page (region-endpoint table + role capabilities) that links out to the auto-generated Swagger/OpenAPI spec — it's never had field-level schema details for any past feature (checked its history back through prior alert-type additions). The new notifications array will surface automatically in the Swagger reference once the API spec is updated on the engineering side; that's outside this docs PR's scope.

[amee-sumo]

Clean, well-scoped update. Verified the anchor rename (#step-6-choose-a-scheduled-search-alert-type → #step-6-add-scheduled-search-alert-types) doesn't break any other cross-references in the repo, the Step 5 cross-link resolves correctly, and the release note is consistent with the doc content.

One thing worth double-checking before merge: the sentence introducing the second screenshot says "combines Email, Webhook, and ServiceNow Connection alerts" (3 types), but the image's alt text says "listing four configured notifications." Could be accurate (e.g. two Email alerts + Webhook + ServiceNow = 4 notifications, 3 types), but worth a quick visual check against the actual screenshot to confirm the count/description matches.

Approving.

[JV0812]

@amee-sumo Good catch — checked the actual screenshot, and it's 4 notifications total: Email, Webhook, ServiceNow Connection, Email (Email appears twice). So the "3 types" phrasing and the alt text's "different alert types" were both slightly off. Fixed (22cb50a99): the sentence now says "combines four notifications ... two Email alerts, a Webhook alert, and a ServiceNow Connection alert," and the alt text matches. This also nicely reinforces the "multiple of the same alert type" point from Step 6.