From 68b7d43be90023f742f9715306971174005a09a7 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Mon, 20 Nov 2023 12:48:12 +0530 Subject: [PATCH 01/12] Update markdown-syntax.md --- docs/dashboards-classic/get-started/markdown-syntax.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/dashboards-classic/get-started/markdown-syntax.md b/docs/dashboards-classic/get-started/markdown-syntax.md index c1a2f2d0e7..316327d712 100644 --- a/docs/dashboards-classic/get-started/markdown-syntax.md +++ b/docs/dashboards-classic/get-started/markdown-syntax.md @@ -104,3 +104,7 @@ precede each line with either a number and a period or an asterisk `*`. This will be displayed in the Text Panel as: ![Combined list](/img/dashboards/markdown_combined_list.png) + +:::info +To know more about the supported markdown elements, refer to the [Markdown guide](https://markdownguide.offshoot.io/basic-syntax/#blockquotes-1). +::: From ef0c085beb1fa6e198cf1458d9e56f501ce829f6 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Fri, 24 Nov 2023 10:29:10 +0530 Subject: [PATCH 02/12] Update docs/dashboards-classic/get-started/markdown-syntax.md Co-authored-by: Kim <56411016+kimsauce@users.noreply.github.com> --- docs/dashboards-classic/get-started/markdown-syntax.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dashboards-classic/get-started/markdown-syntax.md b/docs/dashboards-classic/get-started/markdown-syntax.md index 316327d712..bbd87a0c46 100644 --- a/docs/dashboards-classic/get-started/markdown-syntax.md +++ b/docs/dashboards-classic/get-started/markdown-syntax.md @@ -106,5 +106,5 @@ This will be displayed in the Text Panel as: ![Combined list](/img/dashboards/markdown_combined_list.png) :::info -To know more about the supported markdown elements, refer to the [Markdown guide](https://markdownguide.offshoot.io/basic-syntax/#blockquotes-1). +To learn more about the supported markdown elements, refer to the [Markdown guide](https://markdownguide.offshoot.io/basic-syntax/#blockquotes-1). ::: From 9b36bf52b5d9e05ebead43337d01202b506cd3e4 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Fri, 24 Nov 2023 17:33:19 +0530 Subject: [PATCH 03/12] added supported elements note --- docs/dashboards-classic/get-started/markdown-syntax.md | 2 +- docs/dashboards/panels/markdown-syntax.md | 10 +++++++--- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/dashboards-classic/get-started/markdown-syntax.md b/docs/dashboards-classic/get-started/markdown-syntax.md index bbd87a0c46..a11aca242c 100644 --- a/docs/dashboards-classic/get-started/markdown-syntax.md +++ b/docs/dashboards-classic/get-started/markdown-syntax.md @@ -7,7 +7,7 @@ id: markdown-syntax The following Markdown Syntax options are supported in Dashboards. When your syntax is supported, you'll see "Markdown Supported" near the bottom left corner of the text box. Unsupported syntax prevents you from clicking the **Submit** button. :::important -Images in Text Panels are not supported. +Images, blockquotes, code blocks, URLs, and email addresses are not supported in the text panels. ::: ## Basic text diff --git a/docs/dashboards/panels/markdown-syntax.md b/docs/dashboards/panels/markdown-syntax.md index 5ea1f68569..1bf34e83fe 100644 --- a/docs/dashboards/panels/markdown-syntax.md +++ b/docs/dashboards/panels/markdown-syntax.md @@ -4,11 +4,11 @@ title: Markdown Syntax description: Markdown Syntax options are supported in Dashboards. --- - - The following Markdown Syntax options are supported in Dashboards. When your syntax is supported, you will see "Markdown Supported" near the bottom left corner of the text box. Unsupported syntax prevents you from clicking the **Submit** button. -Images in Text Panels are not supported. +:::important +Images, blockquotes, code blocks, URLs, and email addresses are not supported in the text panels. +::: ## Basic text @@ -101,3 +101,7 @@ To created a combined, nested list of numbered and bulleted items, just precede This will be displayed in the Text Panel as: ![Combined list](/img/reuse/monitor-alert/markdown_combined_list.png) + +:::info +To learn more about the supported markdown elements, refer to the [Markdown guide](https://markdownguide.offshoot.io/basic-syntax/#blockquotes-1). +::: \ No newline at end of file From 707ef38fe2e1fd1e56a2b20f4ef993d2febc0769 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Fri, 24 Nov 2023 17:35:53 +0530 Subject: [PATCH 04/12] removed code block content --- docs/dashboards-classic/get-started/markdown-syntax.md | 6 ------ docs/dashboards/panels/markdown-syntax.md | 6 ------ 2 files changed, 12 deletions(-) diff --git a/docs/dashboards-classic/get-started/markdown-syntax.md b/docs/dashboards-classic/get-started/markdown-syntax.md index a11aca242c..53bc5a512a 100644 --- a/docs/dashboards-classic/get-started/markdown-syntax.md +++ b/docs/dashboards-classic/get-started/markdown-syntax.md @@ -22,12 +22,6 @@ To make text bold, surround the phrase in `** **`. For example, `**This text wil You can combine bold and italic syntax if you'd like. -## Code formatting/block - -To make a snippet of text display as code, surround the phrase with: `‘ ‘ ` - -To make a block of code, surround the content with: `‘‘‘ ‘‘‘` - ## Headings Text can be set to one of six levels, by preceding the text with #: diff --git a/docs/dashboards/panels/markdown-syntax.md b/docs/dashboards/panels/markdown-syntax.md index 1bf34e83fe..d5f1629ad1 100644 --- a/docs/dashboards/panels/markdown-syntax.md +++ b/docs/dashboards/panels/markdown-syntax.md @@ -22,12 +22,6 @@ To make text bold, surround the phrase in `** **`. For example, `**This text wil You can combine bold and italic syntax if you'd like. -## Code formatting/block - -To make a snippet of text display as code, surround the phrase with: `‘ ‘ ` - -To make a block of code, surround the content with: `‘‘‘ ‘‘‘` - ## Headings Text can be set to one of six levels, by preceding the text with `#`: From deddd8476f954b2f172179648acd2f6ab835a15e Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Thu, 11 Jul 2024 10:52:22 +0530 Subject: [PATCH 05/12] Update salesforce-source.md --- .../cloud-to-cloud-integration-framework/salesforce-source.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md index b220d5c0bd..755066ac8c 100644 --- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md +++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md @@ -76,7 +76,7 @@ To configure a Salesforce Source: 1. **Fields.** Click the **+Add Field** link to define the fields you want to associate, each field needs a name (key) and value. * ![green check circle.png](/img/reuse/green-check-circle.png) A green circle with a check mark is shown when the field exists in the Fields table schema. * ![orange exclamation point.png](/img/reuse/orange-exclamation-point.png) An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema it is ignored, known as dropped. -1. **SignOn URL.** Enter your Sign on URL, e.g. https://login.salesforce.com/services/oauth2/token. +1. **SignOn URL.** Enter your Sign on URL, e.g. https://.my.salesforce.com/services/oauth2/token. https://MyDomainName.my. 1. **Client ID.** Enter the Consumer Key of the ConnectedApp.  1. **Client Secret.** Enter the Consumer Secret of the ConnectedApp.  1. **Build In Memory Lookup.** Keep this checked. This will resolve IDs to human-readable names. From 845b78fb61e566fa092872046aa37cf283eeca6a Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Thu, 11 Jul 2024 10:55:12 +0530 Subject: [PATCH 06/12] Update salesforce-source.md --- .../cloud-to-cloud-integration-framework/salesforce-source.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md index 755066ac8c..90ad7d29e9 100644 --- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md +++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md @@ -76,7 +76,7 @@ To configure a Salesforce Source: 1. **Fields.** Click the **+Add Field** link to define the fields you want to associate, each field needs a name (key) and value. * ![green check circle.png](/img/reuse/green-check-circle.png) A green circle with a check mark is shown when the field exists in the Fields table schema. * ![orange exclamation point.png](/img/reuse/orange-exclamation-point.png) An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema it is ignored, known as dropped. -1. **SignOn URL.** Enter your Sign on URL, e.g. https://.my.salesforce.com/services/oauth2/token. https://MyDomainName.my. +1. **SignOn URL.** Enter your Sign on URL. For example, `https://.my.salesforce.com/services/oauth2/token`. 1. **Client ID.** Enter the Consumer Key of the ConnectedApp.  1. **Client Secret.** Enter the Consumer Secret of the ConnectedApp.  1. **Build In Memory Lookup.** Keep this checked. This will resolve IDs to human-readable names. From 27247d3ece439ef61666c0a767ced26e33cf8b25 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Thu, 11 Jul 2024 11:35:15 +0530 Subject: [PATCH 07/12] updated note --- blog-service/2024-07-05-collection.md | 6 +- .../get-started/markdown-syntax.md | 104 ------------------ 2 files changed, 5 insertions(+), 105 deletions(-) delete mode 100644 docs/dashboards-classic/get-started/markdown-syntax.md diff --git a/blog-service/2024-07-05-collection.md b/blog-service/2024-07-05-collection.md index a374d4cfc1..fe933f93af 100644 --- a/blog-service/2024-07-05-collection.md +++ b/blog-service/2024-07-05-collection.md @@ -37,4 +37,8 @@ If you have the Salesforce source set up and choose to upgrade it, follow the in 1. In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. 1. Search for the required source and click the **Upgrade** button.upgrade-source 1. You will be directed to the configuration page. Ensure you do not change any of the configurations set. -1. Click **Upgrade** at the bottom of the configuration page. \ No newline at end of file +1. Click **Upgrade** at the bottom of the configuration page. + +:::note +If your sign-on URL is set to `https://login.salesforce.com/services/oauth2/token`, make sure you update it to `https://.my.salesforce.com/services/oauth2/token`. +::: \ No newline at end of file diff --git a/docs/dashboards-classic/get-started/markdown-syntax.md b/docs/dashboards-classic/get-started/markdown-syntax.md deleted file mode 100644 index 53bc5a512a..0000000000 --- a/docs/dashboards-classic/get-started/markdown-syntax.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -id: markdown-syntax ---- - -# Markdown Syntax - -The following Markdown Syntax options are supported in Dashboards. When your syntax is supported, you'll see "Markdown Supported" near the bottom left corner of the text box. Unsupported syntax prevents you from clicking the **Submit** button. - -:::important -Images, blockquotes, code blocks, URLs, and email addresses are not supported in the text panels. -::: - -## Basic text - -You don't need to apply any syntax to display basic text. Just type the phrase in the Text box. - -## Bold/italic text - -To make text italic, surround the phrase in `* *`. For example, `*This text will be italic*` - -To make text bold, surround the phrase in `** **`. For example, `**This text will be bold**` - -You can combine bold and italic syntax if you'd like. - -## Headings - -Text can be set to one of six levels, by preceding the text with #: - -```sql -# head one - -## head two - -### head three - -#### head four - -##### head five - -###### head six -``` - -## Lists - -### Ordered Lists - -To create a numbered list, precede each list item with a number and a -period. Indent by adding a space.  - -```sql -1. Item One - -2. Item Two - - 1. Indented Item One - - 2. Indented Item Two -``` - -This will be displayed in the Text Panel as: - -![Ordered list](/img/dashboards/markdown_ordered_list.png) - -### Unordered Lists - -To create an unordered bullet list, add `*` or `-` to each item. Both -will produce a bullet. Indent by adding a space. - -```markdown -* Bullet One - -* Bullet Two - - * Bullet Indent One - - * Bullet Indent Two -``` - - This will be displayed in the Text Panel as: - -![Markdown unordered list](/img/dashboards/markdown_unordered_list.png) - -#### Combined Lists - -To created a combined, nested list of numbered and bulleted items, just -precede each line with either a number and a period or an asterisk `*`. - -```markdown -1. Item One - - * Bullet Indent One - -2. Item Two - - * Bullet Indent Two -``` - -This will be displayed in the Text Panel as: - -![Combined list](/img/dashboards/markdown_combined_list.png) - -:::info -To learn more about the supported markdown elements, refer to the [Markdown guide](https://markdownguide.offshoot.io/basic-syntax/#blockquotes-1). -::: From 741666b82e14b117c556536cd6cd094166c0dfee Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Thu, 11 Jul 2024 12:34:25 +0530 Subject: [PATCH 08/12] updated the salesforce doc --- blog-service/2024-07-05-collection.md | 6 +-- .../salesforce-source.md | 50 +++++++++++++++---- 2 files changed, 40 insertions(+), 16 deletions(-) diff --git a/blog-service/2024-07-05-collection.md b/blog-service/2024-07-05-collection.md index fe933f93af..a374d4cfc1 100644 --- a/blog-service/2024-07-05-collection.md +++ b/blog-service/2024-07-05-collection.md @@ -37,8 +37,4 @@ If you have the Salesforce source set up and choose to upgrade it, follow the in 1. In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. 1. Search for the required source and click the **Upgrade** button.upgrade-source 1. You will be directed to the configuration page. Ensure you do not change any of the configurations set. -1. Click **Upgrade** at the bottom of the configuration page. - -:::note -If your sign-on URL is set to `https://login.salesforce.com/services/oauth2/token`, make sure you update it to `https://.my.salesforce.com/services/oauth2/token`. -::: \ No newline at end of file +1. Click **Upgrade** at the bottom of the configuration page. \ No newline at end of file diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md index 90ad7d29e9..a19941a41a 100644 --- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md +++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md @@ -137,29 +137,37 @@ After you configure your Source, you should check the status of the source in th The following section details how you can resolve various errors:  +### No client credentials user enabled + **Error**: `{\"error\":\"invalid_grant\",\"error_description\":\"no client credentials user enabled\"}`. This is due to incorrect policies and permissions for authorization. -To resolve this, if you have migrated your source from v2.1.1 to v3.x.x, make sure to follow the steps mentioned in **Vendor Configuration** section related to client credentials with attention. +**Solution**: To resolve this, if you have migrated your source from v2.1.1 to v3.x.x, make sure to follow the steps mentioned in **Vendor Configuration** section related to client credentials with attention. + +### Object type 'Document' is not supported **Error**: Object type 'Document' is not supported -To resolve this:  +**Solution**: 1. In Salesforce, go to **Setup\>Administration\>Users\>Profile\>New Profile / Edit Profile**. 1. Under **Standard Object Permissions** \> **Documents** select **Read** permission click on the **Save** button.  1. Now assign this profile to the user, whose credentials you have configured as part of the Salesforce Source. +### Object type 'Report' is not supported + **Error**: Object type 'Report' is not supported -To resolve this: +**Solution**: 1. Go to **Setup\>Administration\>Users\>Profile**. 1. Edit specific Profile which is assigned to the user 1. Go to: **General User Permissions** and enable / disable **Run Reports**. **Run Reports** should be enabled for access to REPORT +### Object type 'EventLogFile' is not supported + **Error**: Object type 'EventLogFile' is not supported -To resolve this: +**Solution**: 1. Go to **Setup\>Administration\>Users\>Permission Sets**. 1. Create New Permission Set and assign to user or Edit specific Permission Set which is assigned to user. @@ -172,9 +180,11 @@ To resolve this: If the error still occurs after following the above instructions, contact the Salesforce Support Team. The root cause is likely a licensing issue, which requires their help to resolve. ::: +### Object type ‘SetupAuditTrail’ is not supported + **Error**: Object type ‘SetupAuditTrail’ is not supported -To resolve this: +**Solution**: 1. Go to **Setup\>Administration\>Users\>Profile**. 1. Edit specific Profile which is assigned to the user @@ -184,31 +194,43 @@ To resolve this: If the error still occurs after following the above instructions, contact the Salesforce Support Team. The root cause is likely a licensing issue, which requires their help to resolve. ::: +### Token endpoint mismatch + **Error**: Token Endpoint must match the format `"https:///services/oauth2/token"`. This is due to incorrect source configuration. -To resolve this, provide the correct "SignOn Url".  +**Solution**: Provide the correct "SignOn Url".  + +### Client identifier invalid **Error**: `{"error":"invalid_client_id","error_description":"client identifier invalid"}`. This is due to incorrect source configuration. -To resolve this, provide the correct “Client ID”. +**Solution**: Provide the correct “Client ID”. + +### Invalid client credentials **Error**: `{"error":"invalid_client","error_description":"invalid client credentials"}`. This is due to incorrect source configuration. -To resolve this, provide the correct “Client Secret”.  +**Solution**: Provide the correct “Client Secret”.  + +### Unknown error: Retry your request **Error**: `{"error":"unknown_error","error_description":"retry your request"}`. This is due to an invalid SignOn Url. -To resolve this, change it from login.salesforce.com to `.salesforce.com` +**Solution**: Change it from login.salesforce.com to `.salesforce.com` + +### More Memory Required **Error**: MoreMemoryRequired: Available: 100 FileSize: 200. Please create a support ticket. -To resolve this, create a support ticket with sumo logic to increase the memory for your container. +**Solution**: Create a support ticket with sumo logic to increase the memory for your container. + +### Inconsistencies in Field Values **Error**: Inconsistencies in `DASHBOARD_ID_DERIVED_LOOKUP` Field Values You might see that in certain logs, the `DASHBOARD_ID_DERIVED_LOOKUP` field has value, but in other logs, it's completely empty. This could be because of a problem with permissions. -To resolve this:  +**Solution**: 1. In Salesforce, go to **Setup\>Administration\>Users\>Profile**. 1. Click the **Edit** button for the user's profile you set up for the Salesforce Source. @@ -216,6 +238,12 @@ To resolve this:  1. In the **General User Permissions** section, check the box for **View My Team's Dashboards** permission. 1. Click the **Save** button +### invalid_grant: request not supported on this domain + +**Error**: `invalid_grant` + +**Solution**: Check your sign-on URL. If your sign-on URL is set to `https://login.salesforce.com/services/oauth2/token` change it to `https://.my.salesforce.com/services/oauth2/token`. + ## FAQ :::info From 272e575ba2b92e6215d533863b59481d4f47354a Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Thu, 11 Jul 2024 12:35:36 +0530 Subject: [PATCH 09/12] minor fix --- .../cloud-to-cloud-integration-framework/salesforce-source.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md index a19941a41a..90e3ab9757 100644 --- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md +++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md @@ -238,7 +238,7 @@ You might see that in certain logs, the `DASHBOARD_ID_DERIVED_LOOKUP` field has 1. In the **General User Permissions** section, check the box for **View My Team's Dashboards** permission. 1. Click the **Save** button -### invalid_grant: request not supported on this domain +### Request not supported on this domain **Error**: `invalid_grant` From 2e0946f77e9612e0eccabee20275f8e8685950f5 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Thu, 11 Jul 2024 16:26:43 +0530 Subject: [PATCH 10/12] Update salesforce-source.md --- .../cloud-to-cloud-integration-framework/salesforce-source.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md index 90e3ab9757..de666a0052 100644 --- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md +++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/salesforce-source.md @@ -242,7 +242,7 @@ You might see that in certain logs, the `DASHBOARD_ID_DERIVED_LOOKUP` field has **Error**: `invalid_grant` -**Solution**: Check your sign-on URL. If your sign-on URL is set to `https://login.salesforce.com/services/oauth2/token` change it to `https://.my.salesforce.com/services/oauth2/token`. +**Solution**: Check your sign-on URL. If your sign-on URL is set to `https://login.salesforce.com/services/oauth2/token` you likely need to change it to another value, such as `https://.my.salesforce.com/services/oauth2/token`. ## FAQ From dcc1bf1520ec1f8b5160c65917dc6e45d06f3e9a Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Mon, 22 Jul 2024 11:36:16 +0530 Subject: [PATCH 11/12] Update datadog.md --- docs/integrations/saas-cloud/datadog.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/integrations/saas-cloud/datadog.md b/docs/integrations/saas-cloud/datadog.md index ab86daf55b..6d3ffcd051 100644 --- a/docs/integrations/saas-cloud/datadog.md +++ b/docs/integrations/saas-cloud/datadog.md @@ -15,7 +15,9 @@ The Sumo Logic Integration for Datadog allows you to send events and alerts from 3. Copy the URL that you get after creating the source in the previous step. 4. In Datadog, go to the **Sumo Logic Integration** settings screen. 5. Enter the **Collector Name** you want to assign to the collector and the **Collector URL** from step 3.
Thumbnail icon - + :::note + Ensure the collector name in the Datadog configuration page is same as that of the collector name you entered while creating the collector in the Sumo Logic configuration screen in Step 1. + ::: Next time you'd like to send a message from Datadog to Sumo Logic, use `@sumologic-{YOUR COLLECTOR NAME}`. To send Sumo Logic alerts to your Datadog account, see [Sumo Logic Webhook Connection for Datadog](/docs/alerts/webhook-connections/datadog). From fbf56db2f0a35ff74e54ed8f9c6f2eeda89205eb Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Mon, 22 Jul 2024 11:45:09 +0530 Subject: [PATCH 12/12] minor formatting --- docs/integrations/saas-cloud/datadog.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/integrations/saas-cloud/datadog.md b/docs/integrations/saas-cloud/datadog.md index 6d3ffcd051..074d1ee6b2 100644 --- a/docs/integrations/saas-cloud/datadog.md +++ b/docs/integrations/saas-cloud/datadog.md @@ -15,9 +15,10 @@ The Sumo Logic Integration for Datadog allows you to send events and alerts from 3. Copy the URL that you get after creating the source in the previous step. 4. In Datadog, go to the **Sumo Logic Integration** settings screen. 5. Enter the **Collector Name** you want to assign to the collector and the **Collector URL** from step 3.
Thumbnail icon - :::note - Ensure the collector name in the Datadog configuration page is same as that of the collector name you entered while creating the collector in the Sumo Logic configuration screen in Step 1. - ::: -Next time you'd like to send a message from Datadog to Sumo Logic, use `@sumologic-{YOUR COLLECTOR NAME}`. + :::note + Ensure that the collector name on the Datadog configuration page matches the collector name you entered when creating the collector in the Sumo Logic configuration screen in Step 1. + ::: + +Next time, when you like to send a message from Datadog to Sumo Logic, use `@sumologic-{YOUR COLLECTOR NAME}`. To send Sumo Logic alerts to your Datadog account, see [Sumo Logic Webhook Connection for Datadog](/docs/alerts/webhook-connections/datadog).