9/30/22 Traces release (#400)

Author: kimsauce

docs/apm/traces/working-with-tracing-data/search-query-language-support-for-traces.md

@@ -16,6 +16,9 @@ Tracing data retention in `_trace_spans` index is the same as default log index
     * Logreduce without a field, value, or key suffices
 * `_index` and `_view` are not supported other than when specified as `_trace_spans`.
 * Adding to Dashboard is supported as long as your total dashboard-originated `_trace_spans `read volume does not exceed 200x of your tracing ingest. Contact your Sumo Logic representative for paid subscription service options for volume requirements exceeding 200x of your tracing ingest.
+* Field extraction rules are not supported as the index has well defined schema
+* Data forwarding is not supported
+
 
 ## Search span data
 
@@ -40,15 +43,16 @@ Syntax: `_any<value>`
 
 The `_any` option is not supported outside of the scope of a query. This is supported for the Security and Tracing tiers.
 
-### Parse
+### Parse Your Spans
 
 You can parse your spans in the same way you parse log data. This includes any value from the **tags** field by using the field option with the JSON operator, for example, `| json field=tags`. See how to Parse JSON Formatted Logs for details.
 
-### View
+### View Your Search Results
 
-When viewing your search results you can add any parsed fields to display by selecting them from the Field Browser on the left, or by using the fields operator in your query. The following image shows a query using the `fields` operator to display `operation`, `service`, `spanid`, `statuscode`, and `traceid`. The Field Browser can also set the fields to display.
+When viewing your search results you can add any parsed fields to display by selecting them from the Field Browser on the left, or by using the fields operator in your query. The following image shows a query using the `fields` operator to display `operation`, `service`, `spanid`, `statuscode`, and `traceid`. The Field Browser can also set the fields to display.<br/> ![spans search with fields highlighted.png](/img/traces/spans-search-with-fields-highlighted.png)
 
-![spans search with fields highlighted.png](/img/traces/spans-search-with-fields-highlighted.png)
+### Monitors and Scheduled Searches
+You can also set Monitors and Scheduled Searches for Traces.
 
 ## Span structure
 
@@ -57,7 +61,6 @@ Each span is written in JSON format. Span attributes are parsed to individual fi
 The following two lists contain the fields returned in your search results after running a query:
 
 Displayed by default:
-
 * Time
 * Message (empty and reserved for future use)
 

docs/releasenotes/service.md

@@ -7,16 +7,25 @@ description: Looking for more information about new features in the Sumo Logic S
 
 import useBaseUrl from '@docusaurus/useBaseUrl';
 
-Service Release Notes for the current year are listed here. If you need to see previous Service Release Notes, check the [Archive](docs/releasenotes/archive).
+Service Release Notes for the current year are listed here. If you need to see previous Service Release Notes, check the [Archive](/docs/releasenotes/archive).
+
+---
+## September 30, 2022 (Traces)
+
+Ability to configure monitors with Search Query Language based on Trace Spans index has been officially enabled for all customers. [Learn more](/docs/apm/traces/working-with-tracing-data/search-query-language-support-for-traces).
+
+Additionally, we now also support:
+* [Scheduled Searches](/docs/alerts/scheduled-searches) for Traces
+* [Scheduled Views](/docs/manage/scheduled-views) for Traces
 
 
 ---
 ## September 22, 2022 (Security)
 
-Collection
+#### Collection
 Update - Good news! We've increased the number of Cloud-to-Cloud Sources that customers with paid Sumo Logic subscriptions can have, from 20 to 50. For users of free accounts, the limit remains 20 Cloud-to-Cloud Sources. For more information, see [Cloud-to-Cloud Integration Framework](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework).
 
-Metrics
+#### Metrics
 Update - We've updated the release note published on August 30, 2022, which incorrectly stated that the timeslice metrics operator had been released.
 
 ---