Skip to content

Revert "Docusaurus Faster installation" #4936

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Jan 8, 2025
Merged

Revert "Docusaurus Faster installation" #4936

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
83011ee
Revert "Docusaurus Faster (take 2) (#4928)"
kimsauce Jan 7, 2025
1bb1a8a
convert html tables to md where possible
kimsauce Jan 7, 2025
3efd776
aws fix
kimsauce Jan 7, 2025
fe3b1a7
md fix
kimsauce Jan 7, 2025
278d38d
Merge branch 'main' into revert-4928-faster1
kimsauce Jan 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
408 changes: 1 addition & 407 deletions LICENSE
View file
Open in desktop

Large diffs are not rendered by default.

4 changes: 2 additions & 2 deletions docs/api/getting-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ Sumo Logic has several deployments that are assigned depending on the geographic

Sumo Logic redirects your browser to the correct login URL and also redirects Collectors to the correct endpoint. However, if you're using an API you'll need to manually direct your API client to the correct Sumo Logic API URL.

<table>
<table><small>
<tr>
<td>Deployment</td>
<td>Service Endpoint (login URL)</td>
Expand Down Expand Up @@ -192,7 +192,7 @@ https://endpoint9.collection.us2.sumologic.com/</td>
<td>syslog.collection.us2.sumologic.com</td>
<td>https://open-collectors.us2.sumologic.com</td>
</tr>

</small>
</table>

### Which endpoint should I should use?
Expand Down
2 changes: 1 addition & 1 deletion docs/api/organizations-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ With the Organizations Management API, you can get the credits usage details of
| JP | https://api.jp.sumologic.com/docs/#tag/orgsManagement |
| KR | https://api.kr.sumologic.com/docs/#tag/orgsManagement |
| US1 | https://api.sumologic.com/docs/#tag/orgsManagement |
| US2 | https://api.us2.sumologic.com/docs/#tag/orgsManagement<br/>https://organizations.sumologic.com/docs/#tag/organizationsManagement* <br/> *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. |
| 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> |

<!-- ## Required role capabilities

Expand Down
4 changes: 2 additions & 2 deletions docs/integrations/amazon-aws/aws-privatelink.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ With the NLB-created and ALB-registered as a target, requests over AWS PrivateL

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.

<table>
<table><small>
<tr>
<td><strong>Deployment</strong></td>
<td><strong>Collection Endpoint</strong></td>
Expand Down Expand Up @@ -119,7 +119,7 @@ https://endpoint9.collection.us2.sumologic.com</td>
<td>https://open-collectors.us2.sumologic.com</td>
<td>us-west-2</td>
</tr>
</table>
</small></table>

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

Expand Down
4 changes: 2 additions & 2 deletions docs/integrations/amazon-aws/global-intelligence-cloudtrail-secops.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ This application relies on 45 Scheduled Searches that Save to two different Inde
<details>
<summary>View the list of Scheduled Searches (<strong>click to expand</strong>)</summary>

<table>
<table><small>
<tr>
<td><strong>Folder</strong></td>
<td><strong>Scheduled Search Name (prefixed with gis_benchmarks)</strong></td>
Expand Down Expand Up @@ -282,7 +282,7 @@ This application relies on 45 Scheduled Searches that Save to two different Inde
<td>S3_ListBuckets</td>
<td>Counts S3 events related to listing buckets.</td>
</tr>
</table>
</small></table>

* To reduce false positives, the benchmarks and application filter out AWS CloudTrail events from legitimate cloud services including AWS itself and CloudHealth by VMware.
* Security posture requirements may vary between AWS accounts for a given customer. For example, development accounts might have less strict controls than production accounts. The app supports filtering findings by AWS account ID to facilitate AWS account level posture assessment.
Expand Down
4 changes: 2 additions & 2 deletions docs/integrations/amazon-aws/lambda.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,7 +200,7 @@ To collect the metrics in Sumo Logic, follow the steps below:

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

<table>
<table><small>
<tr>
<td>Metric </td>
<td>Description </td>
Expand All @@ -220,7 +220,7 @@ Once Provisioned Concurrency is enabled and you start collecting CloudWatch metr
<tr>
<td><strong>ProvisionedConcurrencySpilloverInvocations</strong> </td>
<td>Number of Invocations that are above Provisioned Concurrency </td>
</tr>
</tr></small>
</table>


Expand Down
4 changes: 2 additions & 2 deletions docs/integrations/app-development/jfrog-artifactory.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ In this step, you configure four local file sources, one for each log source lis

The following suffixes are required. For example, you could use `_sourceCategory=<Foo>/artifactory/console`, but the suffix **artifactory/console** must be used.

<table>
<table><small>
<tr>
<td><strong>Log source</strong></td>
<td><strong>File Path</strong></td>
Expand All @@ -139,7 +139,7 @@ The following suffixes are required. For example, you could use `_sourceCategory
<td>Traffic</td>
<td>$JFROG_HOME/&#60;product&#62;/var/log/artifactory-traffic.*.log</td>
<td>artifactory/traffic</td>
</tr>
</tr></small>
</table>

:::note
Expand Down
4 changes: 2 additions & 2 deletions docs/integrations/app-development/jfrog-xray.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -228,7 +228,7 @@ Advanced configuration can be used with all JFrog Xray script-based collection c

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

<table>
<table><small>
<tr>
<td>Variable </td>
<td>Usage </td>
Expand Down Expand Up @@ -272,7 +272,7 @@ This section provides a list of variables for Jfrog Xray that you can define in
<tr>
<td>HTTP_LOGS_ENDPOINT in SumoLogic sectio </td>
<td>HTTP source endpoint url created in Sumo Logic for ingesting Logs. </td>
</tr>
</tr></small>
</table>

</details>
Expand Down
8 changes: 4 additions & 4 deletions docs/integrations/containers-orchestration/docker-ulm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ There are alternative methods for collecting Docker logs and metrics. See [Docke
There will be no **Network** metrics if you use the `host` network mode for the container.
:::

<table>
<table><small>
<tr>
<td><strong>Metrics Name</strong></td>
<td><strong>Unit</strong></td>
Expand Down Expand Up @@ -451,7 +451,7 @@ There will be no **Network** metrics if you use the `host` network mode for the
<td>current </td>
<td>Count </td>
<td>Number of PIDs (Not available on Windows) </td>
</tr>
</tr></small>
</table>


Expand Down Expand Up @@ -491,7 +491,7 @@ The table below defines the types of variables you can use.

Docker engine event log data doesn't support the tagging with metadata.

<table>
<table><small>
<tr>
<td><strong>Namespace/VAR_TYPE</strong> </td>
<td><strong>Description</strong> </td>
Expand Down Expand Up @@ -521,7 +521,7 @@ Docker engine event log data doesn't support the tagging with metadata.
<td>User-defined container environment variables that are set with <code>--env|-e</code> flags when starting a container. </td>
<td>The name of the variable.
<br/>Dot characters (<code>.</code>) are not supported. </td>
</tr>
</tr></small>
</table>


Expand Down
4 changes: 2 additions & 2 deletions docs/integrations/databases/mysql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -826,7 +826,7 @@ This section describes the monitors provided with the MySQL app. These monitors

Here are the Telegraf metrics for MySQL collected by the MySQL app.

<table>
<table><small>
<tr>
<td>mysql_aborted_clients<br/>
mysql_aborted_connects<br/>
Expand Down Expand Up @@ -927,5 +927,5 @@ mysql_threads_connected<br/>
mysql_threads_created<br/>
mysql_threads_running<br/>
mysql_uptime</td>
</tr>
</tr></small>
</table>
4 changes: 2 additions & 2 deletions docs/integrations/databases/postgresql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -619,7 +619,7 @@ Use this dashboard to:

Here are the metrics available for PostgreSQL.

<table>
<table><small>
<tr>
<td>PostgreSQL Metrics List</td>
</tr>
Expand Down Expand Up @@ -757,7 +757,7 @@ Here are the metrics available for PostgreSQL.
</tr>
<tr>
<td>postgresql_table_size </td>
</tr>
</tr></small>
</table>


Expand Down
8 changes: 4 additions & 4 deletions docs/integrations/google/workspace/collect-logs-legacy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,7 @@ In the future, if Google adds a new alert type do the following to add new alert

This section provides a list of environment variables for Google Workspace Alert Center and their usage. For information on how to set these environment variables, refer to this [Google Cloud document](https://cloud.google.com/functions/docs/env-var).

<table>
<table><small>
<tr>
<td>Environment Variable </td>
<td>Usage </td>
Expand Down Expand Up @@ -227,7 +227,7 @@ This section provides a list of environment variables for Google Workspace Alert
<tr>
<td><code>SUMO_ENDPOINT</code> </td>
<td>HTTP source endpoint url created in Sumo Logic. </td>
</tr>
</tr></small>
</table>

#### Troubleshooting the GCP Function
Expand Down Expand Up @@ -298,7 +298,7 @@ This section provides a list of environment variables for Google Workspace Alert

For information on how to set these environment variables, refer to this [Google Cloud document](https://cloud.google.com/functions/docs/env-var).

<table>
<table><small>
<tr>
<td>Environment Variable</td>
<td>Usage </td>
Expand Down Expand Up @@ -368,7 +368,7 @@ For information on how to set these environment variables, refer to this [Google
<tr>
<td><code>SUMO_ENDPOINT</code> </td>
<td>HTTP source endpoint url created in Sumo Logic.</td>
</tr>
</tr></small>
</table>


Expand Down
69 changes: 52 additions & 17 deletions docs/integrations/google/workspace/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,12 +20,24 @@ Each Google Workspace app has its own log that tracks actions in JSON format. Th

The common areas of the logs are:

| Event | Description |
|:-------------|:-----------------------------|
| Id | Contains `applicationName` (for example, `drive` or `admin`). |
| Actor | Contains `email`, which is the Google email address of the person performing the action. |
| ipAddress | The IP address of the user performing the action. |

<table>
<tr>
<td><strong>Event</strong></td>
<td><strong>Description</strong></td>
</tr>
<tr>
<td>Id</td>
<td>Contains applicationName (for example, drive or admin).</td>
</tr>
<tr>
<td>Actor</td>
<td>Contains email, which is the Google email address of the person performing the action.</td>
</tr>
<tr>
<td>ipAddress</td>
<td>The IP address of the user performing the action.</td>
</tr>
</table>


The events sections of logs are:
Expand All @@ -34,24 +46,47 @@ The events sections of logs are:

### Google Workspace Login App

| Event | Description |
|:---------------------|:---------------------------------------------------------------|
| Login type name | Equivalent of status or type of activity: `login_success`, `logout`, or `login_failure`. In the Login Dashboard, there is also a panel showing `login_failure_type`, which displays a reason for the login failure. |
| login_challenge | Records action related to a Login Challenge for suspicious sign-ins. Specific results are logged in `login_challenge_status`, where possible values are `Challenge Failed` or `Challenge Passed`. For more information on `login_challenge`, refer to the [Google documentation](https://support.google.com/a/answer/6002699?hl=en). |

<table>
<tr>
<td><strong>Event</strong> </td>
<td><strong>Description</strong> </td>
</tr>
<tr>
<td>Login type name </td>
<td>Equivalent of status or type of activity: login_success, logout, or login_failure. In the Login Dashboard, we also have a Panel showing login_failure_type, which displays a reason for the login failure. </td>
</tr>
<tr>
<td>login_challenge </td>
<td>Records action related to a Login Challenge for suspicious sign ins. Specific results are logged in the login_challenge_status, where the possible values are Challenge Failed or Challenge Passed. For more information on login_challenge, refer to Google documentation:
<p><a href="https://support.google.com/a/answer/6002699?hl=en">https://support.google.com/a/answer/6002699?hl=en</a></p> </td>
</tr>
</table>



### Google Workspace Admin and Token Apps

These are actions performed by Google site administrators.

| Event | Description |
|:--------------------|:---------------------------------------------------------|
| USER_SETTINGS | These are actions performed at the individual user level, such as `CREATE_USER`, `DELETE_USER`, `CHANGE_PASSWORD`. A specific type of individual user action is `CREATE_DATA_TRANSFER_REQUEST`. This typically occurs after a user has been deleted, and the user’s contents, such as Drive, are transferred to that user’s manager. |
| GROUP_SETTINGS | These are actions such as adding and removing users from groups. |
| Other | Other types of actions take place, but they are less common (for example, `CHROME_OS_SETTINGS`, `DEVICE_SETTINGS`). |

<table>
<tr>
<td>Event </td>
<td>Description </td>
</tr>
<tr>
<td>USER_SETTINGS </td>
<td>These are actions performed at the individual user level, such as CREATE_USER, DELETE_USER, CHANGE_PASSWORD.
<p>A specific type of individual user action is CREATE_DATA_TRANSFER_REQUEST. This typically occurs after a user has been deleted, and the user’s contents, such as Drive, are transferred to that user’s manager.</p> </td>
</tr>
<tr>
<td>GROUP_SETTINGS</td>
<td>These are actions such as adding and removing users from groups. </td>
</tr>
<tr>
<td>Other </td>
<td>Other types of actions take place, but they are less common (for example, CHROME_OS_SETTINGS, DEVICE_SETTINGS). </td>
</tr>
</table>



Expand Down
Loading
Loading