Skip to content

Commit 1bb1a8a

Browse files
kimsaucekimsauce
committed
convert html tables to md where possible
1 parent 83011ee commit 1bb1a8a

File tree

12 files changed

+378
-1164
lines changed

12 files changed

+378
-1164
lines changed

‎docs/api/organizations-management.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,9 @@ With the Organizations Management API, you can get the credits usage details of
2828
| JP | https://api.jp.sumologic.com/docs/#tag/orgsManagement |
2929
| KR | https://api.kr.sumologic.com/docs/#tag/orgsManagement |
3030
| US1 | https://api.sumologic.com/docs/#tag/orgsManagement |
31-
| US2 | https://api.us2.sumologic.com/docs/#tag/orgsManagement<br/>https://organizations.sumologic.com/docs/#tag/organizationsManagement* <br/><small> *This assembly is exclusive to the US2 deployment and is designed to manage APIs for Sumo Logic orgs that are not tied to a specific deployment. For example, a parent organization might have child organizations across different deployments. As a result, the [List Organizations API](https://organizations.sumologic.com/docs/#operation/listOrganizations), which lists child organizations, is included in this assembly to accommodate child organizations spread across multiple deployments.</small> |
31+
| US2 | https://api.us2.sumologic.com/docs/#tag/orgsManagement<br/>https://organizations.sumologic.com/docs/#tag/organizationsManagement <sup>`*`</sup> |
32+
33+
<sup>`*`</sup> This assembly is exclusive to the US2 deployment and manages APIs for Sumo Logic orgs not tied to a specific deployment, such as parent orgs with child orgs across multiple deployments. It includes the [List Organizations API](https://organizations.sumologic.com/docs/#operation/listOrganizations) to support this setup.
3234

3335
<!-- ## Required role capabilities
3436

‎docs/integrations/amazon-aws/aws-privatelink.md‎

Lines changed: 17 additions & 88 deletions
Original file line numberDiff line numberDiff line change
@@ -13,18 +13,18 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
1313

1414
<p><a href="/docs/beta"><span className="beta">Beta</span></a></p>
1515

16-
Sumo Logic provides the ability to configure private connectivity between your AWS Infrastructure and Sumologic via [AWS PrivateLink](https://aws.amazon.com/privatelink). This prevents any traffic from being accessible to the public internet.
16+
Sumo Logic provides the ability to configure private connectivity between your AWS Infrastructure and Sumologic via [AWS PrivateLink](https://aws.amazon.com/privatelink). This prevents any traffic from being accessible to the public internet.
1717

18-
Following sources are supported for AWS PrivateLink:
18+
Following sources are supported for AWS PrivateLink:
1919

2020
- **Installed Collector sources**. Data collected on Installed collectors deployed on customer VPC and sent to Sumo Logic.
2121
- **Sumo Logic OpenTelemetry Distro Collector sources**. Data collected on OpenTelemetry Distro collectors deployed on customer VPC and sent to Sumo Logic.
2222
- **HTTPs sources**. Data sent by the applications hosted in customers VPC and sent over to Sumologic using [HTTP Logs and Metrics Source](/docs/send-data/hosted-collectors/http-source/logs-metrics/) and Kinesis Firehose Source for Logs and Metrics.
23-
- **OTLP Source**. An [OTLP/HTTP Source](/docs/send-data/hosted-collectors/http-source/otlp/) is an endpoint for receiving OTLP-formatted Logs and Metrics from OpenTelemetry collectors using [OTLP exporter](https://github.com/open-telemetry/opentelemetry-collector/tree/v0.99.0/exporter/otlphttpexporter#otlphttp-exporter).
23+
- **OTLP Source**. An [OTLP/HTTP Source](/docs/send-data/hosted-collectors/http-source/otlp/) is an endpoint for receiving OTLP-formatted Logs and Metrics from OpenTelemetry collectors using [OTLP exporter](https://github.com/open-telemetry/opentelemetry-collector/tree/v0.99.0/exporter/otlphttpexporter#otlphttp-exporter).
2424

25-
The following sources are not supported for AWS PrivateLink:
25+
The following sources are not supported for AWS PrivateLink:
2626

27-
- Cloud Syslog
27+
- Cloud Syslog
2828
- AWS S3
2929
- AWS Cloudwatch source
3030
- RUM sources
@@ -37,89 +37,18 @@ With the NLB-created and ALB-registered as a target, requests over AWS PrivateL
3737

3838
Sumo Logic exposes AWS PrivateLink endpoints to different [regions that depend on your Sumo Logic deployment](/docs/api/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security). If you're using the VPC in a different region where the Sumo Logic PrivateLink endpoint service is set up, you need to set up VPC peering. Either way, you need to create an endpoint.
3939

40-
<table><small>
41-
<tr>
42-
<td><strong>Deployment</strong></td>
43-
<td><strong>Collection Endpoint</strong></td>
44-
<td><strong>OpenTelemetry Collector Endpoint</strong></td>
45-
<td><strong>AWS Region of Sumo PrivateLink Endpoint Service</strong></td>
46-
</tr>
47-
<tr>
48-
<td>AU</td>
49-
<td>https://collectors.au.sumologic.com</td>
50-
<td>https://open-collectors.au.sumologic.com</td>
51-
<td>ap-southeast-2</td>
52-
</tr>
53-
<tr>
54-
<td>CA</td>
55-
<td>https://collectors.ca.sumologic.com</td>
56-
<td>https://open-collectors.ca.sumologic.com</td>
57-
<td>ca-central-1</td>
58-
</tr>
59-
<tr>
60-
<td>DE</td>
61-
<td>https://collectors.de.sumologic.com</td>
62-
<td>https://open-collectors.de.sumologic.com</td>
63-
<td>eu-central-1</td>
64-
</tr>
65-
<tr>
66-
<td>EU</td>
67-
<td>https://collectors.eu.sumologic.com<br/>
68-
https://endpoint1.collection.eu.sumologic.com</td>
69-
<td>https://open-collectors.eu.sumologic.com</td>
70-
<td>eu-west-1</td>
71-
</tr>
72-
<tr>
73-
<td>IN</td>
74-
<td>https://collectors.in.sumologic.com</td>
75-
<td>https://open-collectors.in.sumologic.com</td>
76-
<td>ap-south-1</td>
77-
</tr>
78-
<tr>
79-
<td>JP</td>
80-
<td>https://collectors.jp.sumologic.com</td>
81-
<td>https://open-collectors.jp.sumologic.com</td>
82-
<td>ap-northeast-1</td>
83-
</tr>
84-
<tr>
85-
<td>KR</td>
86-
<td>https://collectors.kr.sumologic.com<br/></td>
87-
<td>https://open-collectors.kr.sumologic.com</td>
88-
<td>ap-northeast-2</td>
89-
</tr>
90-
<tr>
91-
<td>KR</td>
92-
<td>https://collectors.kr.sumologic.com</td>
93-
<td>https://open-collectors.kr.sumologic.com</td>
94-
<td>ap-northeast-2</td>
95-
</tr>
96-
<tr>
97-
<td>US1</td>
98-
<td>https://collectors.sumologic.com<br/>
99-
https://endpoint1.collection.sumologic.com<br/>
100-
https://endpoint2.collection.sumologic.com<br/>
101-
https://endpoint3.collection.sumologic.com<br/>
102-
https://endpoint4.collection.sumologic.com<br/>
103-
https://endpoint5.collection.sumologic.com</td>
104-
<td>https://open-collectors.sumologic.com</td>
105-
<td>us-east-1</td>
106-
</tr>
107-
<tr>
108-
<td>US2</td>
109-
<td>https://collectors.us2.sumologic.com<br/>
110-
https://endpoint1.collection.us2.sumologic.com<br/>
111-
https://endpoint2.collection.us2.sumologic.com<br/>
112-
https://endpoint3.collection.us2.sumologic.com<br/>
113-
https://endpoint4.collection.us2.sumologic.com<br/>
114-
https://endpoint5.collection.us2.sumologic.com<br/>
115-
https://endpoint6.collection.us2.sumologic.com<br/>
116-
https://endpoint7.collection.us2.sumologic.com<br/>
117-
https://endpoint8.collection.us2.sumologic.com<br/>
118-
https://endpoint9.collection.us2.sumologic.com</td>
119-
<td>https://open-collectors.us2.sumologic.com</td>
120-
<td>us-west-2</td>
121-
</tr>
122-
</small></table>
40+
| Deployment | Collection Endpoint | OpenTelemetry Collector Endpoint | AWS Region of Sumo PrivateLink Endpoint Service |
41+
|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|----------------------------------------------------|
42+
| AU | https://collectors.au.sumologic.com | https://open-collectors.au.sumologic.com | ap-southeast-2 |
43+
| CA | https://collectors.ca.sumologic.com | https://open-collectors.ca.sumologic.com | ca-central-1 |
44+
| DE | https://collectors.de.sumologic.com | https://open-collectors.de.sumologic.com | eu-central-1 |
45+
| EU | https://collectors.eu.sumologic.com<br/> https://endpoint1.collection.eu.sumologic.com | https://open-collectors.eu.sumologic.com | eu-west-1 |
46+
| IN | https://collectors.in.sumologic.com | https://open-collectors.in.sumologic.com | ap-south-1 |
47+
| JP | https://collectors.jp.sumologic.com | https://open-collectors.jp.sumologic.com | ap-northeast-1 |
48+
| KR | https://collectors.kr.sumologic.com | https://open-collectors.kr.sumologic.com | ap-northeast-2 |
49+
| US1 | https://collectors.sumologic.com<br/> https://endpoint1.collection.sumologic.com<br/> https://endpoint2.collection.sumologic.com<br/> https://endpoint3.collection.sumologic.com<br/> https://endpoint4.collection.sumologic.com<br/> https://endpoint5.collection.sumologic.com | https://open-collectors.sumologic.com | us-east-1 |
50+
| US2 | https://collectors.us2.sumologic.com<br/> https://endpoint1.collection.us2.sumologic.com<br/> https://endpoint2.collection.us2.sumologic.com<br/> https://endpoint3.collection.us2.sumologic.com<br/> https://endpoint4.collection.us2.sumologic.com<br/> https://endpoint5.collection.us2.sumologic.com<br/> https://endpoint6.collection.us2.sumologic.com<br/> https://endpoint7.collection.us2.sumologic.com<br/> https://endpoint8.collection.us2.sumologic.com<br/> https://endpoint9.collection.us2.sumologic.com | https://open-collectors.us2.sumologic.com | us-west-2 |
51+
12352

12453
### Create an endpoint to connect with the Sumo Logic endpoint service
12554

‎docs/integrations/amazon-aws/lambda.md‎

Lines changed: 8 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -200,38 +200,21 @@ To collect the metrics in Sumo Logic, follow the steps below:
200200

201201
Once Provisioned Concurrency is enabled and you start collecting CloudWatch metrics, the following new metrics will be available:
202202

203-
<table><small>
204-
<tr>
205-
<td>Metric </td>
206-
<td>Description </td>
207-
</tr>
208-
<tr>
209-
<td><strong>ProvisionedConcurrentExecutions</strong> </td>
210-
<td>Concurrent Executions using Provisioned Concurrency </td>
211-
</tr>
212-
<tr>
213-
<td><strong>ProvisionedConcurrencyUtilization</strong> </td>
214-
<td>Fraction of Provisioned Concurrency in use </td>
215-
</tr>
216-
<tr>
217-
<td><strong>ProvisionedConcurrencyInvocations</strong> </td>
218-
<td>Number of Invocations using Provisioned Concurrency </td>
219-
</tr>
220-
<tr>
221-
<td><strong>ProvisionedConcurrencySpilloverInvocations</strong> </td>
222-
<td>Number of Invocations that are above Provisioned Concurrency </td>
223-
</tr></small>
224-
</table>
225-
203+
| Metric | Description |
204+
|:-----------|:-------------------------|
205+
| **ProvisionedConcurrentExecutions** | Concurrent Executions using Provisioned Concurrency |
206+
| **ProvisionedConcurrencyUtilization** | Fraction of Provisioned Concurrency in use |
207+
| **ProvisionedConcurrencyInvocations** | Number of Invocations using Provisioned Concurrency |
208+
| **ProvisionedConcurrencySpilloverInvocations** | Number of Invocations that are above Provisioned Concurrency |
226209

227210
These metrics can then be queried using Sumo Logic [Metrics queries](/docs/metrics/metrics-queries), as shown in the following example:
228211

229212
<img src={useBaseUrl('img/integrations/amazon-aws/AWS-Lambda-Search-Provisioned-Concurrency-Metrics.png')} alt="Search Provisioned Concurrency Metrics" />
230213

231214
### Field in Field Schema
232215

233-
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Fields**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Fields**. You can also click the **Go To...** menu at the top of the screen and select **Fields**.
234-
1. Search for the “**functionname**” field.
216+
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Fields**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Fields**. You can also click the **Go To...** menu at the top of the screen and select **Fields**.
217+
1. Search for the “**functionname**” field.
235218
1. If not present, create it. Learn how to create and manage fields [here](/docs/manage/fields.md#manage-fields).
236219

237220

‎docs/integrations/app-development/jfrog-xray.md‎

Lines changed: 13 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -228,52 +228,19 @@ Advanced configuration can be used with all JFrog Xray script-based collection c
228228

229229
This section provides a list of variables for Jfrog Xray that you can define in the configuration file.
230230

231-
<table><small>
232-
<tr>
233-
<td>Variable </td>
234-
<td>Usage </td>
235-
</tr>
236-
<tr>
237-
<td>BACKFILL_DAYS in Collection Section </td>
238-
<td>Number of days before the event collection will start. If the value is 1, then events are fetched from yesterday to today. </td>
239-
</tr>
240-
<tr>
241-
<td>LOG_FORMAT in Logging Section </td>
242-
<td>Log format used by the python logging module to write logs in a file. </td>
243-
</tr>
244-
<tr>
245-
<td>ENABLE_LOGFILE in Logging Section </td>
246-
<td>Set to TRUE to write all logs and errors to a log file. </td>
247-
</tr>
248-
<tr>
249-
<td>ENABLE_CONSOLE_LOG in Logging Section </td>
250-
<td>Enables printing logs in a console. </td>
251-
</tr>
252-
<tr>
253-
<td>LOG_FILEPATH in Logging Section </td>
254-
<td>Path of the log file used when ENABLE_LOGFILE is set to TRUE. </td>
255-
</tr>
256-
<tr>
257-
<td>NUM_WORKERS in Collection Section </td>
258-
<td>Number of threads to spawn for API calls. </td>
259-
</tr>
260-
<tr>
261-
<td>MAX_RETRY in Collection Section </td>
262-
<td>Number of retries to attempt in case of request failure. </td>
263-
</tr>
264-
<tr>
265-
<td>BACKOFF_FACTOR in Collection Section </td>
266-
<td>A backoff factor to apply between attempts after the second try. If the backoff_factor is 0.1, then sleep() will sleep for [0.0s, 0.2s, 0.4s, ...] between retries. </td>
267-
</tr>
268-
<tr>
269-
<td>TIMEOUT in Collection Section </td>
270-
<td>Request time out used by the requests library. </td>
271-
</tr>
272-
<tr>
273-
<td>HTTP_LOGS_ENDPOINT in SumoLogic sectio </td>
274-
<td>HTTP source endpoint url created in Sumo Logic for ingesting Logs. </td>
275-
</tr></small>
276-
</table>
231+
| Variable | Usage |
232+
|:----|:-----------------------|
233+
| BACKFILL_DAYS in Collection Section | Number of days before the event collection will start. If the value is 1, then events are fetched from yesterday to today. |
234+
| LOG_FORMAT in Logging Section | Log format used by the Python logging module to write logs in a file. |
235+
| ENABLE_LOGFILE in Logging Section | Set to TRUE to write all logs and errors to a log file. |
236+
| ENABLE_CONSOLE_LOG in Logging Section | Enables printing logs in a console. |
237+
| LOG_FILEPATH in Logging Section | Path of the log file used when ENABLE_LOGFILE is set to TRUE. |
238+
| NUM_WORKERS in Collection Section | Number of threads to spawn for API calls. |
239+
| MAX_RETRY in Collection Section | Number of retries to attempt in case of request failure. |
240+
| BACKOFF_FACTOR in Collection Section | A backoff factor to apply between attempts after the second try. If the backoff_factor is 0.1, then sleep() will sleep for [0.0s, 0.2s, 0.4s, ...] between retries. |
241+
| TIMEOUT in Collection Section | Request timeout used by the requests library. |
242+
| HTTP_LOGS_ENDPOINT in Sumo Logic Section | HTTP source endpoint URL created in Sumo Logic for ingesting logs. |
243+
277244

278245
</details>
279246

0 commit comments

Comments
 (0)