Updates

Author: amee-sumo

cid-redirects.json

@@ -2094,6 +2094,7 @@
   "/cid/22674": "/docs/integrations/google/cloud-functions",
   "/cid/22675": "/docs/integrations/google/cloud-sql",
   "/cid/23233": "/docs/integrations/saas-cloud/zendesk",
+  "/cid/23234": "/docs/integrations/saas-cloud/zimperium",
   "/cid/2323": "/docs/integrations/saas-cloud/zoom",
   "/cid/23239": "/docs/integrations/saas-cloud/lastpass",
   "/cid/2324": "/docs/integrations/saas-cloud/workday",
@@ -2926,6 +2927,7 @@
   "/cid/10999": "/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source",
   "/cid/11000": "/docs/platform-services/automation-service/automation-service-playbooks",
   "/cid/1105": "/docs/integrations/cloud-security-monitoring-analytics/aws-security-hub-ocsf",
+  "/cid/1106": "/docs/integrations/sumo-apps/opentelemetry-collector-insights",
   "/Cloud_SIEM_Enterprise": "/docs/cse",
   "/Cloud_SIEM_Enterprise/Administration": "/docs/cse/administration",
   "/Cloud_SIEM_Enterprise/Administration/Cloud_SIEM_Enterprise_Feature_Update_(2022)": "/docs/cse/administration",

docs/integrations/sumo-apps/index.md

@@ -24,6 +24,8 @@ You may upgrade your account at any time. In these instances, an admin can reque
 
 Once a request has been submitted, a support ticket is automatically opened. A representative from Sumo Logic will respond to your request as soon as possible, generally between one and two business days. Depending on the app that's been requested, Sumo Logic may need additional information, or may need to work with your organization to change the account type to enable some apps.
 
+## Guides
+
 <div className="box-wrapper" >
 <div className="box smallbox card">
   <div className="container">
@@ -79,6 +81,12 @@ Once a request has been submitted, a support ticket is automatically opened. A r
       <p>A guide to the Sumo Logic Log Analysis QuickStart app.</p>
       </div>
     </div>
+    <div className="box smallbox card">
+      <div className="container">
+      <a href="/docs/integrations/sumo-apps/opentelemetry-collector-insights"><img src={useBaseUrl('img/send-data/otel-color.svg')} alt="Thumbnail icon" width="40"/><h4>OpenTelemetry Collector Insights</h4></a>
+      <p>A guide to the Sumo Logic OpenTelemetry Collector Insights app.</p>
+      </div>
+    </div>
     <div className="box smallbox card">
       <div className="container">
       <a href="/docs/integrations/sumo-apps/security-analytics"><img src={useBaseUrl('img/integrations/sumo-apps/SecurityAnalytics.png')} alt="Thumbnail icon" width="40"/><h4>Security Analytics</h4></a>

docs/integrations/hosts-operating-systems/opentelemetry/opentelemetry-collector-insights.md renamed to docs/integrations/sumo-apps/opentelemetry-collector-insights.md

@@ -59,13 +59,13 @@ The OpenTelemetry Collector must be configured to export its own logs using the
 
 ## Collection configuration and app installation
 
-import ConfigAppInstall from '../../../reuse/apps/opentelemetry/config-app-install.md';
+import ConfigAppInstall from '../../reuse/apps/opentelemetry/config-app-install.md';
 
 <ConfigAppInstall/>
 
 ### Step 1: Set up collector
 
-import SetupColl from '../../../reuse/apps/opentelemetry/set-up-collector.md';
+import SetupColl from '../../reuse/apps/opentelemetry/set-up-collector.md';
 
 <SetupColl/>
 
@@ -109,15 +109,15 @@ service:
 
 You can add any custom fields which you want to tag along with the data ingested in Sumo.
 
-import EnvVar from '../../../reuse/apps/opentelemetry/env-var-required.md';
+import EnvVar from '../../reuse/apps/opentelemetry/env-var-required.md';
 
 <EnvVar/>
 
 <img src='https://sumologic-app-data-v2.s3.us-east-1.amazonaws.com/dashboards/OpenTelemetry-Collector-Insights/opentelemetry-collector-insights-configure-form.png' style={{border:'1px solid gray'}} alt="YAML" />
 
 ### Step 3: Send logs and metrics to Sumo Logic
 
-import LogsIntro from '../../../reuse/apps/opentelemetry/send-logs-intro.md';
+import LogsIntro from '../../reuse/apps/opentelemetry/send-logs-intro.md';
 
 <LogsIntro/>
 
@@ -166,30 +166,30 @@ import LogsIntro from '../../../reuse/apps/opentelemetry/send-logs-intro.md';
 </TabItem>
 <TabItem value="Chef">
 
-import ChefEnv from '../../../reuse/apps/opentelemetry/chef-with-env.md';
+import ChefEnv from '../../reuse/apps/opentelemetry/chef-with-env.md';
 
 <ChefEnv/>
 
 </TabItem>
 
 <TabItem value="Ansible">
 
-import AnsEnv from '../../../reuse/apps/opentelemetry/ansible-with-env.md';
+import AnsEnv from '../../reuse/apps/opentelemetry/ansible-with-env.md';
 
 <AnsEnv/>
 
 </TabItem>
 
 <TabItem value="Puppet">
 
-import PuppetEnv from '../../../reuse/apps/opentelemetry/puppet-with-env.md';
+import PuppetEnv from '../../reuse/apps/opentelemetry/puppet-with-env.md';
 
 <PuppetEnv/>
 
 </TabItem>
 </Tabs>
 
-import LogsOutro from '../../../reuse/apps/opentelemetry/send-logs-outro.md';
+import LogsOutro from '../../reuse/apps/opentelemetry/send-logs-outro.md';
 
 <LogsOutro/>
 
@@ -408,7 +408,7 @@ Configure different log levels for troubleshooting:
 
 ## Create monitors for OpenTelemetry Collector Insights app
 
-import CreateMonitors from '../../../reuse/apps/create-monitors.md';
+import CreateMonitors from '../../reuse/apps/create-monitors.md';
 
 <CreateMonitors/>
 
@@ -419,4 +419,4 @@ import CreateMonitors from '../../../reuse/apps/create-monitors.md';
 | `OpenTelemetry Collector Insights - Collector Instance is Down` | This alert fires when a Collector instance stops sending telemetry for more than 10 minutes, indicating it is down or has a connectivity issue. | Missing Data | Data Found |
 | `OpenTelemetry Collector Insights - Exporter Queue Nearing Capacity` | This alert fires when an exporter's sending queue is over 90% full. This is a strong leading indicator of back pressure and imminent data loss. | Count > = 90 | Count < 90 |
 | `OpenTelemetry Collector Insights - High Memory Usage (RSS)` | This alert fires when a Collector's memory usage (RSS) exceeds 2GB. This could be an early indicator of a memory leak or an under-provisioned host. | Count > 2000000000 | Count < = 2000000000 |
-| `OpenTelemetry Collector Insights  - High Metadata Cardinality` | This alert fires when the batch processor is handling more than 1000 unique combinations of metadata. This is a known cause of performance degradation, high CPU, and high memory usage. | Count > 1000 | Count < = 1000 |
+| `OpenTelemetry Collector Insights  - High Metadata Cardinality` | This alert fires when the batch processor is handling more than 1000 unique combinations of metadata. This is a known cause of performance degradation, high CPU, and high memory usage. | Count > 1000 | Count < = 1000 |

sidebars.ts

@@ -2494,7 +2494,6 @@ integrations: [
               'integrations/hosts-operating-systems/opentelemetry/linux-opentelemetry',
               'integrations/hosts-operating-systems/opentelemetry/macos-opentelemetry',
               'integrations/hosts-operating-systems/opentelemetry/windows-opentelemetry',
-              'integrations/hosts-operating-systems/opentelemetry/opentelemetry-collector-insights',
             ],
           },
           'integrations/hosts-operating-systems/host-metrics',
@@ -2675,6 +2674,7 @@ integrations: [
           'integrations/sumo-apps/infrequent-data-tier',
           'integrations/sumo-apps/kickstart-data',
           'integrations/sumo-apps/log-analysis-quickstart',
+          'integrations/sumo-apps/opentelemetry-collector-insights',
           'integrations/sumo-apps/security-analytics',
         ],
       },