Merge pull request #232 from logzio/updates-from-support-oct25

Updates from support oct25
logzio · Oct 25, 2023 · c931842 · c931842
2 parents 0a67370 + 029d797
commit c931842
Show file tree

Hide file tree

Showing 12 changed files with 47 additions and 25 deletions.
diff --git a/docs/user-guide/cloud-siem/dashboards.md b/docs/user-guide/cloud-siem/dashboards.md
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 9
+sidebar_position: 10
 ---
 # Dashboards & Reports
 

diff --git a/docs/user-guide/cloud-siem/integrations/_category_.json b/docs/user-guide/cloud-siem/integrations/_category_.json
@@ -1,6 +1,6 @@
 {
   "label": "Integrations",
-  "position": 10,
+  "position": 11,
   "link": {
     "type": "generated-index",
     "description": "Integrations for Logz.io's Cloud SIEM platform."

diff --git a/docs/user-guide/cloud-siem/investigate-events/_category_.json b/docs/user-guide/cloud-siem/investigate-events/_category_.json
@@ -1,6 +1,6 @@
 {
   "label": "Investigate Events",
-  "position": 4,
+  "position": 5,
   "link": {
     "type": "generated-index",
     "description": "Investigate and manage SIEM related events."

diff --git a/docs/user-guide/cloud-siem/lookup-lists/_category_.json b/docs/user-guide/cloud-siem/lookup-lists/_category_.json
@@ -1,6 +1,6 @@
 {
   "label": "Lookup Lists",
-  "position": 8,
+  "position": 9,
   "link": {
     "type": "generated-index",
     "description": "Learn about the different lookup lists available for you to use."

diff --git a/docs/user-guide/cloud-siem/malicious-IPs.md b/docs/user-guide/cloud-siem/malicious-IPs.md
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 6
+sidebar_position: 7
 ---
 
 # Investigate Malicious IPs

diff --git a/...e/cloud-siem/quick-guide/mssp-accounts.md → docs/user-guide/cloud-siem/mssp-accounts.md b/...e/cloud-siem/quick-guide/mssp-accounts.md → docs/user-guide/cloud-siem/mssp-accounts.md
@@ -1,8 +1,11 @@
 ---
-sidebar_position: 1
+sidebar_position: 3
+title: Create sub accounts as a Managed Security Service Provider (MSSP)
+image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg
+description: Create and manage sub accounts as an MSSP
+keywords: [mssp, siem, logz.io siem. security solution, Managed Security Service Provider, Security information and event management]
 ---
 
-# Create sub accounts as a Managed Security Service Provider (MSSP)
 
 As an MSSP you can create a dedicated SIEM account for each logging account. This lets your customers access their data without the risk of accidentally seeing other customers’ data.
 

diff --git a/docs/user-guide/cloud-siem/quick-guide/_category_.json b/docs/user-guide/cloud-siem/quick-guide/_category_.json
@@ -1,6 +1,6 @@
 {
   "label": "Cloud SIEM Quick Start Guide",
-  "position": 3,
+  "position": 4,
   "link": {
     "type": "generated-index",
     "description": "Cloud SIEM Quick Start Guide"

diff --git a/docs/user-guide/cloud-siem/security-rules/_category_.json b/docs/user-guide/cloud-siem/security-rules/_category_.json
@@ -1,6 +1,6 @@
 {
   "label": "Security Rules",
-  "position": 7,
+  "position": 8,
   "link": {
     "type": "generated-index",
     "description": "Configure and use Logz.io's SIEM security rules."

diff --git a/docs/user-guide/cloud-siem/threat-intelligence/_category_.json b/docs/user-guide/cloud-siem/threat-intelligence/_category_.json
@@ -1,6 +1,6 @@
 {
   "label": "Threat Intelligence",
-  "position": 5,
+  "position": 6,
   "link": {
     "type": "generated-index",
     "description": "Learn about threat intelligence feeds and how to manage them."

diff --git a/docs/user-guide/distributed-tracing/set-up-tracing/get-started-tracing.md b/docs/user-guide/distributed-tracing/set-up-tracing/get-started-tracing.md
@@ -1,11 +1,15 @@
 ---
 sidebar_position: 1
 title: Getting Started with Logz.io Distributed Tracing
+image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg
+description: Set up your Logz.io Distributed Tracing solution
+keywords: [Tracing, traces, Logz.io tracing, distributed tracing, trace]
 ---
+
 Get set and get ready: This section describes what you have to do to get set up - before you can use Distributed Tracing in Logz.io.
 
-If you already use Distributed Tracing, refer to our [guides on how to get connected to Logz.io](https://app.logz.io/#/dashboard/send-your-data/collection?tag=existing-instrumentation&collection=tracing-sources). 
-This information is also available in the [**Logz.io Docs**](https://docs.logz.io/shipping/#tracing-sources), via the **My code is instrumented** filter.
+If you already use Distributed Tracing, you can quickly send your tracing data to Logz.io through your [chosen integration](https://app.logz.io/#/dashboard/integrations/). 
+
 
 ## To set up Distributed Tracing: 
 
@@ -31,14 +35,20 @@ You must have admin permissions for the Logz.io account to view the **Manage tok
 
    1. Find the Distributed Tracing account you want to ship to in the table, and copy the token. 
 
-   *Related Links*
+###### Related Links
 
-   + For information about how to manage your tracing data sources, see the [Manage a Distributed Tracing account](https://docs.logz.io/user-guide/accounts/manage-the-main-account-and-sub-accounts.html#tracing) topic.
+For information about how to manage your tracing data sources, see the [Manage a Distributed Tracing account](https://docs.logz.io/user-guide/accounts/manage-the-main-account-and-sub-accounts.html#tracing) topic.
 
 
 
 #### Look up your Region information
 
+If you have admin user permissions, you can clarify the 2-letter code for your region in Settings > General settings > [Account settings](https://app.logz.io/#/dashboard/settings/general).
+
+![Navigate to general settings](https://dytvr9ot2sszz.cloudfront.net/logz-docs/distributed-tracing/general-settings1_sept2021.png)
+
+The list of all the region codes is available in the **Logz.io Docs**, in the **Region code** column of the [Regions and Listener Hosts table](https://docs.logz.io/user-guide/accounts/account-region.html#available-regions). The default region is US east.
+
 
 ### Set up instrumentation
 
@@ -52,9 +62,7 @@ But instrumentation doesn't *have* to be a huge all-or-nothing effort. It's not
 
 If you hit a wall, we’ll do our best to provide support to help you solve your instrumentation issues. 
 
-To determine the best instrumentation strategy for your system, start with [**Tracing > Send your traces**](https://app.logz.io/#/dashboard/send-your-data/collection?tag=all&collection=tracing-sources&accountIds=true), and then select the relevant filter in the **Tracing** tab, depending on whether or not your code is already instrumented: Either **My code is instrumented** or **My code is not instrumented**.  
-
-This information is also available in the **Logz.io Docs**, in [**Send your data > Tracing**](https://docs.logz.io/shipping/#tracing-sources).
+To determine the best instrumentation strategy for your system, start with [**Send your traces**](https://app.logz.io/#/dashboard/integrations/collectors).
 
 
 ### Install and Run the OpenTelemetry Collector

diff --git a/docs/user-guide/log-management/log-alerts/alert-shortcuts.md b/docs/user-guide/log-management/log-alerts/alert-shortcuts.md
@@ -1,11 +1,29 @@
 ---
 sidebar_position: 4
 title: How to Quickly Create Alerts
+image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg
+description: How to quickly create alerts in Logz.io
+keywords: [alerts, logz.io alerts, opendashboards alerts]
 ---
 
 
 Sometimes, you may want to take shortcuts when creating an alert. You have several options for shortening the process:
 
+### Create an alert manually
+
+These are your most standard methods for creating an alert.
+
+* From the navigation menu, select **Logs > Alerts +** (Yellow + icon).
+
+![Create an alert from navigation](https://dytvr9ot2sszz.cloudfront.net/logz-docs/alerts/alerts-from-nav.png)
+
+
+* From the alerts page. Navigate to **Logs > Alerts** and click the button **+ New alert**.
+
+
+![Create an alert from page](https://dytvr9ot2sszz.cloudfront.net/logz-docs/alerts/alerts-from-page.png)
+
+
 ### Create an alert from OpenSearch Dashboards
 
 Your easiest option is to first test out filters and a search query directly in **OpenSearch Dashboards** or reuse a saved search. When the search captures the right logs, click the button **Create alert** to copy over the search criteria and begin configuring an alert.
@@ -37,10 +55,3 @@ If an **Application Insight** or **Cognitive Insight** interests you, you can cr
 
   ![Duplicate alert](https://dytvr9ot2sszz.cloudfront.net/logz-docs/alerts/duplicate-alert.png)
 
-### Create an alert manually
-
-These are your most standard methods for creating an alert.
-
-* From the navigation menu, select **Logs > Alerts +** (Yellow + icon).
-
-* From the top menu, select **Logs > Alerts** and click the button **+ New alert**.
diff --git a/static/_redirects b/static/_redirects
@@ -107,7 +107,7 @@
 /user-guide/siem/intro/		/docs/user-guide/cloud-siem/about-siem/why-siem
 /user-guide/siem/highlights/		/docs/user-guide/cloud-siem/about-siem/highlights
 /user-guide/cloud-siem/		/docs/user-guide/cloud-siem/
-/user-guide/cloud-siem/mssp-accounts.html		/docs/user-guide/cloud-siem/quick-guide/mssp-accounts
+/user-guide/cloud-siem/mssp-accounts.html		/docs/user-guide/cloud-siem/mssp-accounts
 /user-guide/cloud-siem/send-data-options.html		/docs/user-guide/cloud-siem/quick-guide/send-data-options
 /user-guide/cloud-siem/summary-dashboard.html		/docs/user-guide/cloud-siem/quick-guide/summary-dashboard
 /user-guide/cloud-siem/investigate-events.html		/docs/user-guide/cloud-siem/quick-guide/investigate-events