diff --git a/blog-service/2023/12-31.md b/blog-service/2023/12-31.md index 056ad3d3e3..7d919fc02f 100644 --- a/blog-service/2023/12-31.md +++ b/blog-service/2023/12-31.md @@ -758,7 +758,7 @@ We're excited to announce the release of our new cloud-to-cloud source for Trell We’re happy to announce a new security option allowing administrators to set a custom policy for the number of days an API Access Key can go unused before being automatically deactivated. This setting allows administrators to tailor the feature to suit their organization’s specific security requirements. This enhances the security of your account by reducing the risk of unauthorized access through abandoned access keys. This ensures that only active access keys can be used to access your account and its resources. -[Learn more](/docs/manage/security/access-keys#edit-deactivate-or-delete-an-access-key). +[Learn more](/docs/manage/security/access-keys#access-keys-deactivation-policy). --- diff --git a/blog-service/2025-01-16-manage.md b/blog-service/2025-01-16-manage.md new file mode 100644 index 0000000000..3a5d7ed81e --- /dev/null +++ b/blog-service/2025-01-16-manage.md @@ -0,0 +1,32 @@ +--- +title: Access Keys Enhancements (Manage) +image: https://help.sumologic.com/img/sumo-square.png +keywords: + - access keys + - manage +hide_table_of_contents: true +--- + +import useBaseUrl from '@docusaurus/useBaseUrl'; + +icon + +We're excited to announce enhancements to how you create and manage access keys. + +### Personal Access Keys + +The **My Access Keys** section has been moved out of **Preferences** to its own tab and renamed **Personal Access Keys**. + +Personal access keys + +To open the Personal Access Keys tab: +* [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select your username and then **Preferences > Personal Access Keys**. +* [**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select your username, and then under **Preferences** select **Personal Access Keys**. You can also click the **Go To...** menu at the top of the screen and select **Personal Access Keys**. + +### Scopes + +You can now create permission scopes for access keys. Scopes limit the API endpoints an access key can be used to call. This allows you to specify only the permissions the access key needs to accomplish a specific task, making the key more secure. + +[Learn more](/docs/manage/security/access-keys). + +Custom scopes example diff --git a/docs/cse/integrations/insight-enrichment-server.md b/docs/cse/integrations/insight-enrichment-server.md index f3136e811c..e3e9aa429f 100644 --- a/docs/cse/integrations/insight-enrichment-server.md +++ b/docs/cse/integrations/insight-enrichment-server.md @@ -151,7 +151,7 @@ The following parameters control general server behaviors, as opposed to enrichm | Setting | Required? | Description | |:--|:--|:--| | `URL` | yes | The URL for your API endpoint. For more information, see [Sumo Logic API Authentication, Endpoints, and Security](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). | -| `api_id` | yes | Enter your Sumo Logic Access ID. For more information, see [Manage your access keys on Preferences page](/docs/manage/security/access-keys#from-the-preferences-page). | +| `api_id` | yes | Enter your Sumo Logic Access ID. For more information, see [Access Keys](/docs/manage/security/access-keys). | | `api_key` | yes | Enter your Sumo Logic Access Key.| | `log_level` | no | Log level the server should use. The options are:

-`error`. Only display error messages.
-`info`. Display informational messages. This is the recommended value.
-`debug`. Displays debug (or trace) data. Recommended only when debugging.

Default: `info` | | `poll_interval` | no | How often the Insight Enrichment Server should check for new insights. You can specify the interval in seconds (s), minutes (m), or hours (h).

Default: 10s | diff --git a/docs/cse/integrations/security-incident-response-integration.md b/docs/cse/integrations/security-incident-response-integration.md index 48cf61642e..c0b4491b71 100644 --- a/docs/cse/integrations/security-incident-response-integration.md +++ b/docs/cse/integrations/security-incident-response-integration.md @@ -36,7 +36,7 @@ Your Cloud SIEM role must allow you to use API keys and to retrieve and modify i In this step, you make a copy of your API credentials, which you'll need to supply when you install the SIR-Cloud SIEM integration in [Step 5](#step-5-install-the-sir-cloud-siem-integration) below.  -You’ll need to supply a Sumo Logic Access ID and Access Key. If necessary, you can create those on your **Preferences** page in the Sumo Logic UI. For more information, see [Create an access key on Preferences page](/docs/manage/security/access-keys#from-the-preferences-page). +You’ll need to supply a Sumo Logic Access ID and Access Key. If necessary, you can create those in the Sumo Logic UI. For more information, see [Access Keys](/docs/manage/security/access-keys). ## Step 2: Install ServiceNow plugins diff --git a/docs/get-started/account-settings-preferences.md b/docs/get-started/account-settings-preferences.md index 9695463169..ead23d4e83 100644 --- a/docs/get-started/account-settings-preferences.md +++ b/docs/get-started/account-settings-preferences.md @@ -66,10 +66,6 @@ To set up 2-Step Verification, you will need to install a Time-Based One-Time Pa 1. Scan the QR code displayed on your screen with your TOTP App. 1. After the TOTP App is configured, enter two consecutive authentication codes. -## My Access Keys - -In Sumo Logic, you'll need an access key to register new Collectors and use Sumo Logic APIs. If you have a role that grants the **Create Access Keys** capability, you can create and manage your own Access Keys. For more information, see [Access Keys](/docs/manage/security/access-keys). - ## My Preferences Preference settings are only changed for your personal account; they do not affect any other users in your organization. Any changes you make to your preferences take effect the next time you sign in, not during the current session. diff --git a/docs/get-started/index.md b/docs/get-started/index.md index 4bfb917f3c..074a386150 100644 --- a/docs/get-started/index.md +++ b/docs/get-started/index.md @@ -44,7 +44,7 @@ Let's get started!
icon

Account Preferences

 -

Account settings, access keys, and credentials.

+

Account settings and credentials.

diff --git a/docs/get-started/sumo-logic-ui-classic.md b/docs/get-started/sumo-logic-ui-classic.md index ca1ce4286b..f90cdac592 100644 --- a/docs/get-started/sumo-logic-ui-classic.md +++ b/docs/get-started/sumo-logic-ui-classic.md @@ -208,7 +208,6 @@ To manage your personal Sumo Logic account preferences, do the following: 1. In the Preferences page that appears on the right, you can modify settings in the following areas: * **My Profile**: username and password * **My Security Settings**: enable and disable 2-step verification - * **My Access Keys**: add, edit, and remove access keys * **My Preferences**: your account session settings For more information, see the [Preferences Page](account-settings-preferences.md). diff --git a/docs/get-started/sumo-logic-ui.md b/docs/get-started/sumo-logic-ui.md index c34c15f9aa..c8d14cfd0d 100644 --- a/docs/get-started/sumo-logic-ui.md +++ b/docs/get-started/sumo-logic-ui.md @@ -128,7 +128,6 @@ To manage your personal Sumo account preferences: 1. From the top nav bar, click the person icon, and then from the dropdown, select **Preferences**.
Account Preferences 1. In the Preferences page, you can modify the following settings: * **My Profile**. Username and password. - * **My Access Keys**. Add, edit, and remove access keys. * **My Preferences**. Your account session settings. For more information, see [Account Preferences and Credentials](account-settings-preferences.md). diff --git a/docs/integrations/amazon-aws/global-intelligence-guardduty.md b/docs/integrations/amazon-aws/global-intelligence-guardduty.md index 2c41adcde3..f01eba8158 100644 --- a/docs/integrations/amazon-aws/global-intelligence-guardduty.md +++ b/docs/integrations/amazon-aws/global-intelligence-guardduty.md @@ -155,7 +155,7 @@ These tasks require the Manage Collectors and Manage Access Keys [role capabilit In this step, you need to generate access key and access ID from the Sumo Logic console. To generate an access key and access ID, do the following: -1. Follow the instructions as described in this [Sumo Logic Access Key](/docs/manage/security/access-keys#create-an-access-key)) document. +1. Follow the instructions as described in [Access Keys](/docs/manage/security/access-keys). 2. Copy down both the values as you’ll need them to deploy the Sumo Logic GuardDuty Benchmark SAM App. diff --git a/docs/integrations/amazon-aws/guardduty-benchmark.md b/docs/integrations/amazon-aws/guardduty-benchmark.md index fe5bcc5e83..91def3c000 100644 --- a/docs/integrations/amazon-aws/guardduty-benchmark.md +++ b/docs/integrations/amazon-aws/guardduty-benchmark.md @@ -54,7 +54,7 @@ This section shows you how to generate an access key and access ID for log colle In this step, you need to generate access key and access ID from the Sumo Logic console. To generate an access key and access ID, do the following: -1. Follow the instructions as described in this [Sumo Logic Access Key](/docs/manage/security/access-keys#create-an-access-key)) document. +1. Follow the instructions as described in [Access Keys](/docs/manage/security/access-keys#create-an-access-key). 2. Copy down both the values as you’ll need them to deploy the Sumo Logic GuardDuty Benchmark SAM App. diff --git a/docs/integrations/app-development/jfrog-xray.md b/docs/integrations/app-development/jfrog-xray.md index 29b643146c..94e15270ae 100644 --- a/docs/integrations/app-development/jfrog-xray.md +++ b/docs/integrations/app-development/jfrog-xray.md @@ -129,7 +129,7 @@ When you configure the HTTP source, make sure to save the HTTP Source Address UR To add a hosted collector and HTTP source: 1. Create a new Sumo Logic hosted collector by performing the steps in [Configure a Hosted Collector](/docs/send-data/hosted-collectors/configure-hosted-collector). -2. Create a new HTTP source on the hosted collector created above by following [these instructions](/docs/send-data/hosted-collectors/http-source/logs-metrics). +2. Create a new HTTP source on the hosted collector created above by following instructions in [HTTP Logs and Metrics Source]](/docs/send-data/hosted-collectors/http-source/logs-metrics). ### Step 5: Set up a collection method for JFrog Xray diff --git a/docs/integrations/containers-orchestration/activemq.md b/docs/integrations/containers-orchestration/activemq.md index 873080fc8c..9e81898cc8 100644 --- a/docs/integrations/containers-orchestration/activemq.md +++ b/docs/integrations/containers-orchestration/activemq.md @@ -484,7 +484,7 @@ The monitors are disabled by default. Once you have installed the alerts using t ### Method 2: Install the alerts using a Terraform script -1. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using these[ instructions](/docs/manage/security/access-keys#from-the-preferences-page). To find out which deployment your Sumo Logic account is in, see [Sumo Logic endpoints](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). To find out which deployment your Sumo Logic account is in, see [Sumo Logic endpoints](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later. 3. Download the Sumo Logic Terraform package for ActiveMQ alerts: The alerts package is available in the Sumo Logic github[ repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/ActiveMQ). You can either download it through the “git clone” command or as a zip file. 4. Alert Configuration: After the package has been extracted, navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/ActiveMQ/`. @@ -555,10 +555,10 @@ Locate and install the app you need from the **App Catalog**. If you want to see 1. From the **App Catalog**, search for and select the app. 2. Select the version of the service you're using and click **Add to Library**. 3. To install the app, complete the following fields. - 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
 + 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app. 2. **Data Source.** Choose **Enter a Custom Data Filter** and enter a custom ActiveMQ cluster filter. Examples: * For all ActiveMQ clusters: `messaging_cluster=*` - * For a specific cluster: `messaging_cluster=activemq.dev.01`.
 + * For a specific cluster: `messaging_cluster=activemq.dev.01`. * Clusters within a specific environment: `messaging_cluster=activemq-1` and `environment=prod` (This assumes you have set the optional environment tag while configuring collection). 4. **Advanced**. Select the **Location in Library** (the default is the Personal folder in the library), or click **New Folder** to add a new folder. 5. Click **Add to Library**. diff --git a/docs/integrations/containers-orchestration/docker-community-edition.md b/docs/integrations/containers-orchestration/docker-community-edition.md index 6739771d99..be9e6ebfd1 100644 --- a/docs/integrations/containers-orchestration/docker-community-edition.md +++ b/docs/integrations/containers-orchestration/docker-community-edition.md @@ -307,8 +307,8 @@ In collector version 19.216-22 and later, when you configure the sourceCategory You build templates for sourceCategory and sourceHost specifying component variables in this form: `{{NAMESPACE.VAR_NAME}}`. Where: -* `NAMESPACE` is a namespace that indicates the variable type.
 -* `VAR_NAME` is the variable name.
 These are case-sensitive. +* `NAMESPACE` is a namespace that indicates the variable type. +* `VAR_NAME` is the variable name. These are case-sensitive. The table below defines the types of variables you can use. diff --git a/docs/integrations/containers-orchestration/kafka.md b/docs/integrations/containers-orchestration/kafka.md index 61ed4e3225..49aa1b000c 100644 --- a/docs/integrations/containers-orchestration/kafka.md +++ b/docs/integrations/containers-orchestration/kafka.md @@ -418,7 +418,7 @@ The monitors are disabled by default. Once you have installed the alerts using t ### Method B: Using a Terraform script -1. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using these[ instructions](/docs/manage/security/access-keys#from-the-preferences-page). Identify which deployment your Sumo Logic account is in using [this link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Identify which deployment your Sumo Logic account is in using [this link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later. 3. Download the Sumo Logic Terraform package for Kafka alerts. The alerts package is available in the Sumo Logic [GitHub repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/Kafka). You can either download it through the “git clone” command or as a zip file. 4. Alert Configuration. After the package has been extracted, navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/Kafka`. @@ -489,10 +489,10 @@ Locate and install the app you need from the **App Catalog**. If you want to see Version selection is not available for all apps. ::: 3. To install the app, complete the following fields. - * **App Name.** You can retain the existing name, or enter a name of your choice for the app.
 + * **App Name.** You can retain the existing name, or enter a name of your choice for the app. * **Data Source.** Choose **Enter a Custom Data Filter**, and enter a custom Kafka cluster filter. Examples: * For all Kafka clusters `messaging_cluster=*` - * For a specific cluster: `messaging_cluster=Kafka.dev.01`.
 + * For a specific cluster: `messaging_cluster=Kafka.dev.01`. * Clusters within a specific environment: `messaging_cluster=Kafka-1 and environment=prod`. This assumes you have set the optional environment tag while configuring collection. 4. **Advanced**. Select the **Location in Library** (the default is the Personal folder in the library), or click **New Folder** to add a new folder. 5. Click **Add to Library**. diff --git a/docs/integrations/containers-orchestration/kubernetes.md b/docs/integrations/containers-orchestration/kubernetes.md index 22c4234b09..da2af7a056 100644 --- a/docs/integrations/containers-orchestration/kubernetes.md +++ b/docs/integrations/containers-orchestration/kubernetes.md @@ -123,7 +123,7 @@ The monitors are disabled by default. Once you have installed the alerts using t ### Method B: Using a Terraform script -1. Generate a Sumo Logic access key and ID for a user that has the **Manage Monitors** role capability in Sumo Logic using [these instructions](/docs/manage/security/access-keys). There, you'll need to identify which deployment your Sumo Logic account is in ([learn more](/docs/api/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security)). +1. Generate a Sumo Logic access key and ID for a user that has the **Manage Monitors** role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). There, you'll need to identify which deployment your Sumo Logic account is in ([learn more](/docs/api/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security)). 1. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later. 1. Download the Sumo Logic Terraform package for Kubernetes alerts. The alerts package is available in the [Sumo Logic GitHub repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/kubernetes). You can either download it through the `git clone` command or as a zip file. 1. **Alert Configuration**. After the package has been extracted, navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/kubernetes/`. diff --git a/docs/integrations/containers-orchestration/rabbitmq.md b/docs/integrations/containers-orchestration/rabbitmq.md index 0b8d728b30..a53acbcc89 100644 --- a/docs/integrations/containers-orchestration/rabbitmq.md +++ b/docs/integrations/containers-orchestration/rabbitmq.md @@ -389,7 +389,7 @@ There are limits to how many alerts can be enabled. For more information, see [M #### Method B: Install Monitors using a Terraform script -1. Generate an access key and access ID for a user that has the **Manage Monitors** role capability. For instructions see [Access Keys](/docs/manage/security/access-keys#from-the-preferences-page). +1. Generate an access key and access ID for a user that has the **Manage Monitors** role capability. For instructions see [Access Keys](/docs/manage/security/access-keys). 2. Download [Terraform 0.13](https://www.terraform.io/downloads.html) or later, and install it. 3. Download the Sumo Logic Terraform package for MySQL monitors: The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/mysql). You can either download it using the git clone command or as a zip file. 4. Alert Configuration: After extracting the package, navigate to the terraform-sumologic-sumo-logic-monitor/monitor_packages/RabbitMQ/ directory. diff --git a/docs/integrations/databases/cassandra.md b/docs/integrations/databases/cassandra.md index b940eb2fe8..1dd12df004 100644 --- a/docs/integrations/databases/cassandra.md +++ b/docs/integrations/databases/cassandra.md @@ -551,7 +551,7 @@ There are limits to how many alerts can be enabled. For more information, see [M ### Method B: Using a Terraform script -1. Generate an access key and access ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys#from-the-preferences-page). +1. Generate an access key and access ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys). 2. Download [Terraform 0.13](https://www.terraform.io/downloads.html) or later and install it. 3. Download the Sumo Logic Terraform package for Cassandra monitors. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/Memcached). You can either download it using the git clone command or as a zip file. 4. Alert Configuration. After extracting the package, navigate to the `terraform-sumologic-sumo-logic-monitor/monitor_packages/Cassandra/` directory. diff --git a/docs/integrations/databases/couchbase.md b/docs/integrations/databases/couchbase.md index 8e1b832081..16a8ae1b30 100644 --- a/docs/integrations/databases/couchbase.md +++ b/docs/integrations/databases/couchbase.md @@ -233,7 +233,7 @@ The process to set up collection for Couchbase data is done through the followin The Sumo Logic Couchbase app supports the audit log, query log, error log, access log. For details, [refer to Couchbase logging documentation](https://docs.couchbase.com/server/current/manage/manage-logging/manage-logging.html#changing-log-file-locations). -1. **Configure logging in Couchbase**. By default, the Couchbase will write the log to the log directory that was configured during installation. For example, on Linux, the log directory would be `/opt/couchbase/var/lib/couchbase/logs`. By default, the Audit log is disabled, you must enable the audit log following these [instructions](https://docs.couchbase.com/server/current/manage/manage-security/manage-auditing.html). Query log, error log, the access log will be enabled by default. +1. **Configure logging in Couchbase**. By default, the Couchbase will write the log to the log directory that was configured during installation. For example, on Linux, the log directory would be `/opt/couchbase/var/lib/couchbase/logs`. By default, the Audit log is disabled, you must enable the audit log following [these instructions](https://docs.couchbase.com/server/current/manage/manage-security/manage-auditing.html). Query log, error log, the access log will be enabled by default. 2. **Configure a Collector**. Use one of the following Sumo Logic Collector options: 1. To collect logs directly from the Couchbase machine, configure an [Installed Collector](/docs/send-data/installed-collectors). 2. If you're using a service like Fluentd, or you would like to upload your logs manually, configure a [Hosted Collector](/docs/send-data/hosted-collectors/configure-hosted-collector). @@ -408,7 +408,7 @@ There are limits to how many alerts can be enabled - see the [Alerts FAQ](/docs/ ### Method B: Using a Terraform script method -1. **Generate a Sumo Logic access key and ID**. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using [these instructions](/docs/manage/security/access-keys#from-the-preferences-page). Identify which deployment your Sumo Logic account is in using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. **Generate a Sumo Logic access key and ID**. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Identify which deployment your Sumo Logic account is in using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. **[Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later**. 3. **Download the Sumo Logic Terraform package for Couchbase alerts**. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/SquidProxy). You can either download it through the “git clone” command or as a zip file. 4. **Alert Configuration**. After the package has been extracted, navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/Couchbase/` diff --git a/docs/integrations/databases/elasticsearch.md b/docs/integrations/databases/elasticsearch.md index ee9213ecf6..593dec59a2 100644 --- a/docs/integrations/databases/elasticsearch.md +++ b/docs/integrations/databases/elasticsearch.md @@ -389,7 +389,7 @@ To install these monitors, you must have the **Manage Monitors** role capability ### Method 2: Using a Terraform script -1. Generate a Sumo Logic access key and ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys#from-the-preferences-page). +1. Generate a Sumo Logic access key and ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys). 2. Download [Terraform 0.13](https://www.terraform.io/downloads.html) or later, and install it. 3. Download the Sumo Logic Terraform package for Elasticsearch monitors. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/Elasticsearch). You can either download it using the git clone command or as a zip file. 4. Alert Configuration. After extracting the package, navigate to the `terraform-sumologic-sumo-logic-monitor/monitor_packages/Elasticsearch/` directory. diff --git a/docs/integrations/databases/mariadb.md b/docs/integrations/databases/mariadb.md index eb266c11a0..9abb1c08ff 100644 --- a/docs/integrations/databases/mariadb.md +++ b/docs/integrations/databases/mariadb.md @@ -455,7 +455,7 @@ Sumo Logic has provided out-of-the-box alerts available through [Sumo Logic moni ### Method B: Using a Terraform script -1. **Generate a Sumo Logic access key and ID.** Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using these[ instructions](/docs/manage/security/access-keys#from-the-preferences-page). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security) +1. **Generate a Sumo Logic access key and ID.** Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security) 2. **[Download and install Terraform 0.13](https://www.terraform.io/downloads.html)** or later. 3. **Download the Sumo Logic Terraform package for MariaDB alerts.** The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/MariaDB). You can either download it through the “git clone” command or as a zip file. 4. **Alert Configuration.** After the package has been extracted, navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/MariaDB/`. Edit the **MariaDB.auto.tfvars** file and add the Sumo Logic Access Key, Access Id, and Deployment from Step 1. diff --git a/docs/integrations/databases/memcached.md b/docs/integrations/databases/memcached.md index 8942032c21..f2c984678f 100644 --- a/docs/integrations/databases/memcached.md +++ b/docs/integrations/databases/memcached.md @@ -381,7 +381,7 @@ There are limits to how many alerts can be enabled. For more information, see [M ### Method B: Using a Terraform script -1. Generate a Sumo Logic access key and ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys#from-the-preferences-page). +1. Generate a Sumo Logic access key and ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys). 2. Download [Terraform 0.13](https://www.terraform.io/downloads.html) or later, and install. 3. Download the Sumo Logic Terraform package for Memcached monitors. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/Memcached). You can either download it using the git clone command or as a zip file. 4. Alert Configuration. After extracting the package, navigate to the `terraform-sumologic-sumo-logic-monitor/monitor_packages/Memcached/` directory. diff --git a/docs/integrations/databases/mongodb.md b/docs/integrations/databases/mongodb.md index a05f932a58..233b3da29d 100644 --- a/docs/integrations/databases/mongodb.md +++ b/docs/integrations/databases/mongodb.md @@ -435,7 +435,7 @@ There are limits to how many alerts can be enabled. For more information, see [M ### Method B: Using a Terraform script -1. Generate a Sumo Logic access key and ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys#from-the-preferences-page). +1. Generate a Sumo Logic access key and ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys). 2. Download [Terraform 0.13](https://www.terraform.io/downloads.html) or later, and install it. 3. Download the Sumo Logic Terraform package for MongoDB monitors. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/MongoDB). You can either download it using the `git clone` command or as a zip file. 4. Alert Configuration. After extracting the package , navigate to the `terraform-sumologic-sumo-logic-monitor/monitor_packages/MongoDB/` directory. Edit the `MongoDB.auto.tfvars` file and add the Sumo Logic Access Key and Access ID from Step 1 and your Sumo Logic deployment. If you're not sure of your deployment, see [Sumo Logic Endpoints and Firewall Security](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). diff --git a/docs/integrations/databases/mysql.md b/docs/integrations/databases/mysql.md index edfdadf2e6..9be203eb30 100644 --- a/docs/integrations/databases/mysql.md +++ b/docs/integrations/databases/mysql.md @@ -583,7 +583,7 @@ There are limits to how many alerts can be enabled. For more information, see [M ### Method B: Using a Terraform script -1. Generate an access key and access ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys#from-the-preferences-page). +1. Generate an access key and access ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys). 2. Download [Terraform 0.13](https://www.terraform.io/downloads.html) or later, and install it. 3. Download the Sumo Logic Terraform package for MySQL monitors. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/mysql). You can either download it using the `git clone` command or as a zip file. 4. Alert Configuration: After extracting the package, navigate to the `terraform-sumologic-sumo-logic-monitor/monitor_packages/mysql/` directory. diff --git a/docs/integrations/databases/opentelemetry/couchbase-opentelemetry.md b/docs/integrations/databases/opentelemetry/couchbase-opentelemetry.md index a4d27a7cf3..8d8e559810 100644 --- a/docs/integrations/databases/opentelemetry/couchbase-opentelemetry.md +++ b/docs/integrations/databases/opentelemetry/couchbase-opentelemetry.md @@ -32,7 +32,7 @@ Following are the [Fields](/docs/manage/fields/) which will be created as part o ## Prerequisite -By default, the Couchbase will write the log to the log directory that was configured during installation. For example, on Linux, the log directory would be `/opt/couchbase/var/lib/couchbase/logs`. By default, the Audit log is disabled, you must enable the audit log following these [instructions](https://docs.couchbase.com/server/current/manage/manage-security/manage-auditing.html). Query log, error log, the access log will be enabled by default. +By default, the Couchbase will write the log to the log directory that was configured during installation. For example, on Linux, the log directory would be `/opt/couchbase/var/lib/couchbase/logs`. By default, the Audit log is disabled, you must enable the audit log following [these instructions](https://docs.couchbase.com/server/current/manage/manage-security/manage-auditing.html). Query log, error log, the access log will be enabled by default. import LogsCollectionPrereqisites from '../../../reuse/apps/logs-collection-prereqisites.md'; diff --git a/docs/integrations/databases/oracle.md b/docs/integrations/databases/oracle.md index 79f50370eb..ee930d0487 100644 --- a/docs/integrations/databases/oracle.md +++ b/docs/integrations/databases/oracle.md @@ -499,7 +499,7 @@ The monitors are disabled by default. Once you have installed the alerts using t ### Method B: Using a Terraform script -1. **Generate a Sumo Logic access key and ID**. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using these[ instructions](/docs/manage/security/access-keys#from-the-preferences-page). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. **Generate a Sumo Logic access key and ID**. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. **[Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later**. 3. **Download the Sumo Logic Terraform package for Oracle alerts**. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/Oracle). You can either download it through the “git clone” command or as a zip file. 4. **Alert Configuration**. After the package has been extracted, navigate to the package directory **terraform-sumologic-sumo-logic-monitor/monitor_packages/Oracle/**. Edit the **Oracle.auto.tfvars** file and add the Sumo Logic Access Key, Access Id and Deployment from Step 1. diff --git a/docs/integrations/databases/postgresql.md b/docs/integrations/databases/postgresql.md index 17f24e0723..d3b8a7001e 100644 --- a/docs/integrations/databases/postgresql.md +++ b/docs/integrations/databases/postgresql.md @@ -428,7 +428,7 @@ The monitors are disabled by default. Once you have installed the alerts using t ### Method B: Using a Terraform script -1. Generate a Sumo Logic access key and ID for a user that has the Manage Monitors role capability in Sumo Logic using these[ instructions](/docs/manage/security/access-keys#from-the-preferences-page). Please identify which deployment your Sumo Logic account is in, using this [ link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. Generate a Sumo Logic access key and ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Please identify which deployment your Sumo Logic account is in, using this [ link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later. 3. Download the Sumo Logic Terraform package for PostgreSQL alerts: The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/postgresql). You can either download it through the “git clone” command or as a zip file. 4. Alert Configuration: After the package has been extracted, navigate to the package directory terraform-sumologic-sumo-logic-monitor/monitor_packages/**postgresql**/ diff --git a/docs/integrations/databases/redis.md b/docs/integrations/databases/redis.md index 3933ea3880..0384642472 100644 --- a/docs/integrations/databases/redis.md +++ b/docs/integrations/databases/redis.md @@ -464,9 +464,9 @@ Monitors are disabled by default. Once you have installed the alerts via this me ### Method B: Using a Terraform script -1. Generate a Sumo Logic access key and ID for a user that has the Manage Monitors role capability in Sumo Logic using[ these](/docs/manage/security/access-keys#from-the-preferences-page) instructions. Please identify which deployment your Sumo Logic account is in,[ using](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security) this link. +1. Generate a Sumo Logic access key and ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Please identify which deployment your Sumo Logic account is in, using [this link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later. -3. Download the Sumo Logic Terraform package for Redis alerts. The alerts package is available in the Sumo Logic github[ repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/redis). You can either download it via the “git clone” command or as a zip file. +3. Download the Sumo Logic Terraform package for Redis alerts. The alerts package is available in the Sumo Logic github [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/redis). You can either download it via the “git clone” command or as a zip file. 4. Monitor Configuration. After the package has been extracted, navigate to the package directory terraform-sumologic-sumo-logic-monitor/monitor_packages/**redis**/ Edit the redis.auto.tfvars file and add the Sumo Logic Access Key, Access Id and Deployment from Step 1. diff --git a/docs/integrations/hosts-operating-systems/host-process-metrics.md b/docs/integrations/hosts-operating-systems/host-process-metrics.md index 6c55a5a72b..7386b7b715 100644 --- a/docs/integrations/hosts-operating-systems/host-process-metrics.md +++ b/docs/integrations/hosts-operating-systems/host-process-metrics.md @@ -199,7 +199,7 @@ The monitors are disabled by default. Once you have installed the alerts using t ### Method B: Using a Terraform script -1. **Generate a Sumo Logic access key and ID**. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using [these instructions](/docs/manage/security/access-keys#from-the-preferences-page). Please identify which deployment your Sumo Logic account is in, using [this link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. **Generate a Sumo Logic access key and ID**. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Please identify which deployment your Sumo Logic account is in, using [this link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 1. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later. 1. **Download the Sumo Logic Terraform package for Host and Process alerts**. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/postgresql). You can either download it through the “git clone” command or as a zip file. 1. **Alert Configuration**. After the package has been extracted, navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/host_process_metrics/`. Edit the `host_and_processes.auto.tfvars` file and add the Sumo Logic Access Key, Access Id, and Deployment from Step 1. diff --git a/docs/integrations/microsoft-azure/sql-server.md b/docs/integrations/microsoft-azure/sql-server.md index ac8ea155ba..85c082de31 100644 --- a/docs/integrations/microsoft-azure/sql-server.md +++ b/docs/integrations/microsoft-azure/sql-server.md @@ -451,7 +451,7 @@ The monitors are disabled by default. Once you have installed the alerts using t **Step 1: Generate a Sumo Logic access key and ID** -Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using these[ instructions](/docs/manage/security/access-keys#from-the-preferences-page). Please identify which deployment your Sumo Logic account is in, using this [ link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Please identify which deployment your Sumo Logic account is in, using this [ link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). **Step 2: [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later** diff --git a/docs/integrations/web-servers/apache-tomcat.md b/docs/integrations/web-servers/apache-tomcat.md index 86d5ec8f09..6802fb25a0 100644 --- a/docs/integrations/web-servers/apache-tomcat.md +++ b/docs/integrations/web-servers/apache-tomcat.md @@ -625,7 +625,7 @@ Custom filter examples: Step 1: Generate a Sumo Logic access key and ID -Generate an access key and access ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys#from-the-preferences-page). +Generate an access key and access ID for a user that has the **Manage Monitors** role capability. For instructions, see [Access Keys](/docs/manage/security/access-keys). Step 2: Download and install Terraform @@ -737,11 +737,11 @@ Locate and install the app you need from the **App Catalog**. If you want to see Version selection is not available for all apps. ::: 3. To install the app, complete the following fields. - 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
 + 1. **App Name.** You can retain the existing name, or enter a name of your choice for the app. 2. **Data Source.** * Choose **Enter a Custom Data Filter**, and enter a custom filter for Apache Tomcat webserver farm. Examples: * For all Apache Tomcat webserver farms webserver_farm=* - * For a specific webserver farms: webserver_farm=tomcat.dev.01.
 + * For a specific webserver farms: webserver_farm=tomcat.dev.01. * Clusters within a specific environment: `webserver_farm=tomcat-1 and environment=prod`. (This assumes you have set the optional environment tag while configuring collection) 4. **Advanced**. Select the **Location in Library** (the default is the Personal folder in the library), or click **New Folder** to add a new folder. 5. Click **Add to Library**. diff --git a/docs/integrations/web-servers/apache.md b/docs/integrations/web-servers/apache.md index 7915977f60..aa143f44dc 100644 --- a/docs/integrations/web-servers/apache.md +++ b/docs/integrations/web-servers/apache.md @@ -465,7 +465,7 @@ The monitors are disabled by default. Once you have installed the alerts using t ### Method B: Using a Terraform script -1. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using these[ instructions](/docs/manage/security/access-keys#from-the-preferences-page). Please identify which deployment your Sumo Logic account is in, using this[ link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Please identify which deployment your Sumo Logic account is in, using this[ link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later. 3. Download the Sumo Logic Terraform package for Apache alerts. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/apache). You can either download it through the “git clone” command or as a zip file. 4. Alert Configuration. After the package has been extracted, navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/apache/`. diff --git a/docs/integrations/web-servers/haproxy.md b/docs/integrations/web-servers/haproxy.md index 23b1555f19..f9042e3b41 100644 --- a/docs/integrations/web-servers/haproxy.md +++ b/docs/integrations/web-servers/haproxy.md @@ -455,7 +455,7 @@ However, if you would like to restrict these alerts to specific clusters or envi ### Method 2: Use a Terraform script -1. Generate an access key and access ID for a user that has the **Manage Monitors** role capability. For instructions see [Access Keys](/docs/manage/security/access-keys#from-the-preferences-page). +1. Generate an access key and access ID for a user that has the **Manage Monitors** role capability. For instructions see [Access Keys](/docs/manage/security/access-keys). 2. Download [Terraform 0.13](https://www.terraform.io/downloads.html) or later, and install it. 3. Download the Sumo Logic Terraform package for HAProxy monitors. The alerts package is available in the [Sumo Logic GitHub repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages). You can either download it using the git clone command or as a zip file. 4. Alert Configuration. After extracting the package, navigate to the terraform-sumologic-sumo-logic-monitor/monitor_packages/haproxy/ directory. Edit the haproxy.auto.tfvars file and add the Sumo Logic Access Key and Access ID from Step 1 and your Sumo Logic deployment. If you're not sure of your deployment, see [Sumo Logic Endpoints and Firewall Security](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). diff --git a/docs/integrations/web-servers/iis-10.md b/docs/integrations/web-servers/iis-10.md index 9705cacd33..7d8ed520d4 100644 --- a/docs/integrations/web-servers/iis-10.md +++ b/docs/integrations/web-servers/iis-10.md @@ -436,7 +436,7 @@ Monitors are disabled by default. Once you have installed the alerts using this ### Method B: Using a Terraform script -1. **Generate a Sumo Logic access key and ID**. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using these[ instructions](/docs/manage/security/access-keys#from-the-preferences-page). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. **Generate a Sumo Logic access key and ID**. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. **Download and install Terraform**. You'll need to [download and install Terraform](https://www.terraform.io/downloads.html), version 0.13 or later. 3. **Download the Sumo Logic Terraform package for IIS Server alerts**. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/IIS). You can either download it through the “git clone” command or as a zip file. 4. **Alert Configuration**. After the package has been extracted, navigate to the package directory **terraform-sumologic-sumo-logic-monitor/monitor_packages/IIS/**. diff --git a/docs/integrations/web-servers/nginx-ingress.md b/docs/integrations/web-servers/nginx-ingress.md index 87c6e34104..527cb3ecf0 100644 --- a/docs/integrations/web-servers/nginx-ingress.md +++ b/docs/integrations/web-servers/nginx-ingress.md @@ -115,7 +115,7 @@ The monitors are disabled by default. Once you have installed the alerts using t ### Method B: Using a Terraform script -1. Generate a Sumo Logic access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using these[ instructions](/docs/manage/security/access-keys#from-the-preferences-page). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. Generate a Sumo Logic access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later. 3. Download the Sumo Logic Terraform package for Nginx Ingress alerts: The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/Nginx%20Ingress). You can either download it through the “git clone” command or as a zip file. 4. Alert Configuration: After the package has been extracted, navigate to the package directory terraform-sumologic-sumo-logic-monitor/monitor_packages/Nginx Ingress. diff --git a/docs/integrations/web-servers/nginx-plus-ingress.md b/docs/integrations/web-servers/nginx-plus-ingress.md index c6dd8fa3c3..e16f834ec5 100644 --- a/docs/integrations/web-servers/nginx-plus-ingress.md +++ b/docs/integrations/web-servers/nginx-plus-ingress.md @@ -133,7 +133,7 @@ The monitors are disabled by default. Once you have installed the alerts via thi ### Method B: Using a Terraform script -1. Generate a Sumo Logic [access key](/docs/manage/security/access-keys#from-the-preferences-page) and access ID for a user that has the[ Manage Monitors](/docs/manage/users-roles/roles/role-capabilities) role capability in Sumo Logic using these instructions. Please identify your Sumo Logic[ deployment](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. Generate a Sumo Logic [access key](/docs/manage/security/access-keys) and access ID for a user that has the[ Manage Monitors](/docs/manage/users-roles/roles/role-capabilities) role capability in Sumo Logic using these instructions. Please identify your Sumo Logic[ deployment](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later. 3. Download the Sumo Logic Terraform package for Nginx Ingress alerts: The alerts package is available in the [Sumo Logic GitHub repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/nginx-plus-ingress). You can either download it via the `git clone` command or as a zip file. 4. Alert Configuration: After the package has been extracted, navigate to the package directory **terraform-sumologic-sumo-logic-monitor/monitor_packages/nginx-plus-ingress/**. Edit the **nginxplusingress.auto.tfvars** file as per below instructions: diff --git a/docs/integrations/web-servers/nginx-plus.md b/docs/integrations/web-servers/nginx-plus.md index 7a8b198cef..f8ed279270 100644 --- a/docs/integrations/web-servers/nginx-plus.md +++ b/docs/integrations/web-servers/nginx-plus.md @@ -311,7 +311,7 @@ The monitors are disabled by default. Once you have installed the alerts via thi ### Method B: Using a Terraform script -1. Generate a Sumo Logic [access key](/docs/manage/security/access-keys#from-the-preferences-page) and access ID for a user that has the [Manage Monitors](/docs/manage/users-roles/roles/role-capabilities) role capability in Sumo Logic using these instructions. Please identify your Sumo Logic [deployment](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. Generate a Sumo Logic [access key](/docs/manage/security/access-keys) and access ID for a user that has the [Manage Monitors](/docs/manage/users-roles/roles/role-capabilities) role capability in Sumo Logic using these instructions. Please identify your Sumo Logic [deployment](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later 3. Download the Sumo Logic Terraform package for Nginx Plus alerts. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/nginx-plus). You can either download it via the “git clone” command or as a zip file. 4. Alert Configuration: After the package has been extracted, navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/nginx-plus/`. Edit the **nginxplus.auto.tfvars** file as per the below instructions: diff --git a/docs/integrations/web-servers/nginx.md b/docs/integrations/web-servers/nginx.md index 6f9dc59059..fb3f092cc1 100644 --- a/docs/integrations/web-servers/nginx.md +++ b/docs/integrations/web-servers/nginx.md @@ -405,7 +405,7 @@ The monitors are disabled by default. Once you have installed the alerts using t ### Method B: Using a Terraform script -1. **Generate a Sumo Logic access key and ID** Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using these[ instructions](/docs/manage/security/access-keys#from-the-preferences-page). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. **Generate a Sumo Logic access key and ID** Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. **[Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later** 3. **Download the Sumo Logic Terraform package for Nginx alerts** The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/Nginx). You can either download it through the “git clone” command or as a zip file. 4. **Alert Configuration** After the package has been extracted, navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/Nginx/`. diff --git a/docs/integrations/web-servers/squid-proxy.md b/docs/integrations/web-servers/squid-proxy.md index 184be9c9ab..a7ccdd5e28 100644 --- a/docs/integrations/web-servers/squid-proxy.md +++ b/docs/integrations/web-servers/squid-proxy.md @@ -359,7 +359,7 @@ The process to set up collection for Squid Proxy data is done through the follow Squid Proxy app supports the default access logs and cache logs format. -1. **Configure logging in Squid Proxy.** By default, the squid proxy will write the access log to the log directory that was configured during installation. For example, on Linux, the log directory would be `/var/log/squid/access.log`. If the access log is disabled then you must enable the access log following these [instructions](https://wiki.squid-cache.org/SquidFaq/SquidLogs). +1. **Configure logging in Squid Proxy.** By default, the squid proxy will write the access log to the log directory that was configured during installation. For example, on Linux, the log directory would be `/var/log/squid/access.log`. If the access log is disabled then you must enable the access log following [these instructions](https://wiki.squid-cache.org/SquidFaq/SquidLogs). 2. **Configure an Installed Collector.** If you have not already done so, install and configure an installed collector for Windows by [following the documentation](/docs/send-data/installed-collectors/windows). 3. **Configure a Collector**. Use one of the following Sumo Logic Collector options: 1. To collect logs directly from the Squid Proxy machine, configure an [Installed Collector](/docs/send-data/installed-collectors). @@ -687,7 +687,7 @@ The monitors are disabled by default. Once you have installed the alerts using t ### Method 2: Install the alerts using a Terraform script -1. Generate a Sumo Logic access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using these [instructions](/docs/manage/security/access-keys#from-the-preferences-page). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). +1. Generate a Sumo Logic access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). Identify which deployment your Sumo Logic account is in, using this [link](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security). 2. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later. 3. Download the Sumo Logic Terraform package for Squid Proxy alerts: The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/SquidProxy). You can either download it through the “git clone” command or as a zip file. 4. Alert Configuration: After the package has been extracted, navigate to the package directory terraform-sumologic-sumo-logic-monitor/monitor_packages/SquidProxy/. @@ -759,7 +759,7 @@ Locate and install the app you need from the **App Catalog**. If you want to see Version selection is not available for all apps. ::: 3. To install the app, complete the following fields. - * **App Name.** You can retain the existing name, or enter a name of your choice for the app.
 + * **App Name.** You can retain the existing name, or enter a name of your choice for the app. * **Data Source.** Choose **Enter a Custom Data Filter**, and enter a custom Squid Proxy cluster filter. Examples: * For all Squid Proxy clusters: `proxy_cluster=*` * For a specific farm; `proxy_cluster=squidproxy.dev.01`. diff --git a/docs/integrations/web-servers/varnish.md b/docs/integrations/web-servers/varnish.md index e9493bf8b9..35400aa597 100644 --- a/docs/integrations/web-servers/varnish.md +++ b/docs/integrations/web-servers/varnish.md @@ -352,7 +352,7 @@ You can install monitors by importing a JSON file or using a Terraform script. ### Method B: Using a Terraform script -1. Generate an access key and access ID for a user with the **Manage Monitors** role capability; for instructions, see [Access Keys](/docs/manage/security/access-keys#from-the-preferences-page). +1. Generate an access key and access ID for a user with the **Manage Monitors** role capability; for instructions, see [Access Keys](/docs/manage/security/access-keys). 2. Download [Terraform 0.13](https://www.terraform.io/downloads.html) or later and install it. 3. Download the Sumo Logic Terraform package for MySQL monitor. The alerts package is available in the Sumo Logic GitHub [repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages). You can either download it using the git clone command or as a zip file. 4. Alert Configuration. After extracting the package, navigate to the `terraform-sumologic-sumo-logic-monitor/monitor_packages/Varnish/` directory. diff --git a/docs/manage/security/access-keys.md b/docs/manage/security/access-keys.md index ed0b2ed973..519397d590 100644 --- a/docs/manage/security/access-keys.md +++ b/docs/manage/security/access-keys.md @@ -4,43 +4,13 @@ title: Access Keys description: Access keys allow you to securely register new Collectors or access Sumo Logic APIs. --- import useBaseUrl from '@docusaurus/useBaseUrl'; +import Iframe from 'react-iframe'; In Sumo Logic, you'll need an access key to: * **Register new Collectors**. When you install a Collector, in addition to having a role that grants you the **Manage Collectors** capability, you must supply an access key. You can use a different access key for each Collector, or use the same access key for multiple Collectors. The only time a Collector uses the access key is at installation, so if a key is deleted after a Collector has been set up, the Collector isn't affected. * **Use Sumo Logic APIs**. You must supply an access key to use the Sumo Logic APIs. See [API Authentication](/docs/api/getting-started#authentication) for details. -import Iframe from 'react-iframe'; - -:::sumo Micro Lesson - -