Skip to content

Commit 028a3cc

Browse files
authored
Merge branch 'main' into add-note-about-null-value
2 parents b06b659 + e2b1301 commit 028a3cc

File tree

6 files changed

+66
-32
lines changed

6 files changed

+66
-32
lines changed

docs/integrations/saas-cloud/jamf.md

Lines changed: 23 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -862,15 +862,33 @@ _sourceCategory="Labs/Jamf" computer_management
862862
| count as num_profiles
863863
```
864864

865-
## Set up collection
865+
## Collection configuration and app installation
866866

867-
Follow the instructions provided to set up [Cloud-to-Cloud Integration for Jamf Source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/jamf-source/) to create the source and use the same source category while installing the app. By following these steps, you can ensure that your Jamf app is properly integrated and configured to collect and analyze your Jamf data.
867+
import CollectionConfiguration from '../../reuse/apps/collection-configuration.md';
868868

869-
## Installing the Jamf app
869+
<CollectionConfiguration/>
870870

871-
import AppInstall2 from '../../reuse/apps/app-install-v2.md';
871+
:::important
872+
Use the [Cloud-to-Cloud Integration for Jamf Source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/jamf-source/) to create the source and use the same source category while installing the app. By following these steps, you can ensure that your Jamf app is properly integrated and configured to collect and analyze your Jamf data.
873+
:::
874+
875+
### Create a new collector and install the app
876+
877+
import AppCollectionOPtion1 from '../../reuse/apps/app-collection-option-1.md';
878+
879+
<AppCollectionOPtion1/>
880+
881+
### Use an existing collector and install the app
882+
883+
import AppCollectionOPtion2 from '../../reuse/apps/app-collection-option-2.md';
884+
885+
<AppCollectionOPtion2/>
886+
887+
### Use an existing source and install the app
888+
889+
import AppCollectionOPtion3 from '../../reuse/apps/app-collection-option-3.md';
872890

873-
<AppInstall2/>
891+
<AppCollectionOPtion3/>
874892

875893
## Viewing the Jamf dashboards
876894

docs/integrations/saas-cloud/symantec-endpoint-security-service.md

Lines changed: 23 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -209,15 +209,33 @@ _sourceCategory="Labs/SES" device_uid
209209
| limit 10
210210
```
211211

212-
## Set up collection
212+
## Collection configuration and app installation
213213

214-
To set up the [Cloud-to-Cloud Integration for Symantec Endpoint Security Source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/symantec-endpoint-security-source/), follow the instructions provided. These instructions will guide you through the process of creating a source using the Symantec Endpoint Security Source category, which you will need to use when installing the app. By following these steps, you can ensure that your Symantec Endpoint Security app is properly integrated and configured to collect and analyze your Symantec Endpoint Security data.
214+
import CollectionConfiguration from '../../reuse/apps/collection-configuration.md';
215215

216-
## Installing the Symantec Endpoint Security app
216+
<CollectionConfiguration/>
217217

218-
import AppInstall2 from '../../reuse/apps/app-install-v2.md';
218+
:::important
219+
Use the [Cloud-to-Cloud Integration for Symantec Endpoint Security Source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/symantec-endpoint-security-source/) to create the source and use the same source category while installing the app. By following these steps, you can ensure that your Symantec Endpoint Security app is properly integrated and configured to collect and analyze your Symantec Endpoint Security data.
220+
:::
221+
222+
### Create a new collector and install the app
223+
224+
import AppCollectionOPtion1 from '../../reuse/apps/app-collection-option-1.md';
225+
226+
<AppCollectionOPtion1/>
227+
228+
### Use an existing collector and install the app
229+
230+
import AppCollectionOPtion2 from '../../reuse/apps/app-collection-option-2.md';
231+
232+
<AppCollectionOPtion2/>
233+
234+
### Use an existing source and install the app
235+
236+
import AppCollectionOPtion3 from '../../reuse/apps/app-collection-option-3.md';
219237

220-
<AppInstall2/>
238+
<AppCollectionOPtion3/>
221239

222240
## Viewing the Symantec Endpoint Security dashboards
223241

docs/platform-services/automation-service/app-central/integrations/darktrace.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
77

88
<img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/darktrace.png')} alt="darktrace" width="100"/>
99

10-
***Version: 1.6
11-
Updated: Mar 4, 2024***
10+
***Version: 1.7
11+
Updated: Jan 10, 2025***
1212

1313
Perform threat intelligence evidence gathering with Darktrace.
1414

@@ -45,3 +45,4 @@ Perform threat intelligence evidence gathering with Darktrace.
4545
+ Updated resource: Resolved bug related to integration resource
4646
* February 28, 2024 (v1.5) - Updated code for compatibility with Python 3.12
4747
* March 4, 2024 (v1.5) - Updated code for compatibility with Python 3.12
48+
* January 10, 2025 (v1.7) - Fixed timedelta related error in all actions

docs/platform-services/automation-service/app-central/integrations/servicenow-v2.md

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
66

77
<img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/servicenow-v2.png')} alt="servicenow" width="100"/>
88

9-
***Version: 2.5
10-
Updated: May 31, 2024***
9+
***Version: 2.6
10+
Updated: Jan 13, 2025***
1111

1212
ServiceNow V2 SaaS is for technical management support - create, update, and gather ServiceNow ticket information.
1313

@@ -44,26 +44,26 @@ Query used to filter the result set.
4444

4545
Building the query:
4646

47-
Syntax: sysparm\_query=&lt;col\_name&gt;&lt;operator&gt;&lt;value&gt;.
47+
Syntax: `<col_name><operator><value>`
4848

49-
* &lt;col\_name&gt;: Name of the table column to filter against.
50-
* &lt;operator&gt;: Supports the following values:
51-
=: Exactly matches &lt;value&gt;.
52-
!=: Does not match &lt;value&gt;.
53-
^: Logically AND multiple query statements.
54-
^OR: Logically OR multiple query statements.
55-
LIKE: &lt;col\_name&gt; contains the specified string. Only works for &lt;col\_name&gt; fields whose data type is string.
56-
STARTSWITH: &lt;col\_name&gt; starts with the specified string. Only works for &lt;col\_name&gt; fields whose data type is string.
57-
ENDSWITH: &lt;col\_name&gt; ends with the specified string. Only works for &lt;col\_name&gt; fields whose data type is string.
58-
* &lt;value&gt;: Value to match against.
49+
* `<col_name>`: Name of the table column to filter against.
50+
* `<operator>`: Supports the following values:
51+
* `=:` Exactly matches `<value>`.
52+
* `!=`: Does not match `<value>`.
53+
* `^`: Logically AND multiple query statements.
54+
* `^OR`: Logically OR multiple query statements.
55+
* `LIKE`: `<col_name>` contains the specified string. Only works for `<col_name>` fields whose data type is string.
56+
* `STARTSWITH`: `<col_name>` starts with the specified string. Only works for `<col_name>` fields whose data type is string.
57+
* `ENDSWITH`: `<col_name>` ends with the specified string. Only works for `<col_name>` fields whose data type is string.
58+
* `<value>`: Value to match against.
5959

6060
All parameters are case-sensitive.
6161

6262
Queries can contain more than one entry.
6363

64-
For example: sysparm\_query=&lt;col\_name&gt;&lt;operator&gt;&lt;value&gt;[&lt;operator&gt;&lt;col\_name&gt;&lt;operator&gt;&lt;value&gt;]
64+
For example: `<col_name><operator><value>[<operator><col_name><operator><value>]`
6565

66-
For more info please check the official API doc: &lt;https://developer.servicenow.com/dev.do#!/reference/api/sandiego/rest/c_TableAPI#table-GET&gt;
66+
For more information check the [ServiceNow API documentation](https://developer.servicenow.com/dev.do#!/reference/api/xanadu/rest/c_TableAPI#table-GET).
6767

6868
**Create Ticket**
6969

@@ -92,3 +92,4 @@ Ticketing System
9292
* June 30, 2023 (v2.3) - Integration code improved.
9393
* April 5, 2024 (v2.4) - Fixed an issue that prevents the resource testing to work correctly.
9494
* May 31, 2024 (v2.5) - Fixed an issue in actions **Create Ticket** and **Update Ticket** in which the JSON Query field was not visible.
95+
* Jan 13, 2025 (v2.6) - Modified hint of the **query** field as it was misleading.

docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,6 @@ description: The Azure Event Hubs Source for Logs provides a secure endpoint to
77
import useBaseUrl from '@docusaurus/useBaseUrl';
88
import ForwardToSiem from '/docs/reuse/forward-to-siem.md';
99

10-
:::note
11-
Azure Event Hubs for Logs is preferred for higher throughput but does not support IP restrictions. We recommend using the [Azure Event Hubs cloud-to-cloud source collection method](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source) if you have IP address restrictions on Event Hubs. If you require higher throughput and have IP address restrictions on Event Hubs, consider splitting your Event Hubs into smaller namespaces, each staying within the 1MB/s (86GB/day) limit, and create a Cloud-to-Cloud collection method for each namespace.
12-
:::
1310

1411
The Azure Event Hubs Source provides a secure endpoint to receive data from Azure Event Hubs. It securely stores the required authentication, scheduling, and state tracking information.
1512

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,7 @@ import ForwardToSiem from '/docs/reuse/forward-to-siem.md';
1515
import useBaseUrl from '@docusaurus/useBaseUrl';
1616

1717
:::note
18-
- Collecting data from Azure Event Hubs using this Cloud-to-Cloud collection method supports a throughput limit of 1MB/s (86GB/day) per named Event Hub egress rate. If you require higher throughput, we recommend using the [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source).
19-
- The only caveat is this Cloud-to-Cloud collection method supports IP restrictions and the [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/) does not. If you require higher throughput and have IP address restrictions on Event Hubs, consider splitting your Event Hubs into smaller namespaces, each staying within the 1MB/s (86GB/day) limit, and create a Cloud-to-Cloud collection method for each namespace.
18+
Collecting data from Azure Event Hubs using this Cloud-to-Cloud collection method supports a throughput limit of 1MB/s (86GB/day) per named Event Hub egress rate. If you require higher throughput, we recommend using [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source).
2019
:::
2120

2221
<img src={useBaseUrl('img/send-data/azure-event-hub.svg')} alt="icon" width="40"/>

0 commit comments

Comments
 (0)