Download Sumo Logic

Author: r | 2025-04-24

★★★★☆ (4.6 / 3284 reviews)

sketchup for schools

Sumo Logic QuickStart - Download as a PDF or view online for free. Sumo Logic QuickStart - Download as a PDF or view online for free. Submit Search. Sumo Logic QuickStart Download as PPTX, PDF 0 likes 2. Sumo Logic. QuickStart your Sumo Logic service with this exclusive webinar. At these monthly live events you will learn Read our blog to get a closer look at Sumo Logic’s ServiceNow Connectors. Learn more about how Sumo partners with ServiceNow. Visit the ServiceNow Store to download Sumo Logic’s Connectors . Request a demo. Sign up for a free trial of Sumo Logic. About Sumo Logic

google.earth live

Sumo Support Community - Sumo Logic

The instructions in the previous sections. However, if you would like to restrict these alerts to specific clusters or environments, update the JSON file by replacing the text db_system=mariadb with . Custom filter examples:For alerts applicable only to a specific cluster, your custom filter would be db_cluster=mariadb-prod.01.For alerts applicable to all clusters that start with Kafka-prod, your custom filter would be db_cluster=mariadb-prod*.For alerts applicable to a specific cluster within a production environment, your custom filter would be db_cluster=mariadb-1 and environment=prod. This assumes you have set the optional environment tag while configuring collection.Classic UI. In the main Sumo Logic menu, select Manage Data > Monitoring > Monitors. New UI. In the main Sumo Logic menu, select Alerts > Monitors. You can also click the Go To... menu at the top of the screen and select Monitors.Click Add.Click Import and then copy-paste the above JSON to import monitors.The monitors are disabled by default. Once you have installed the alerts using this method, navigate to the MariaDB folder under Monitors to configure them. See this document to enable monitors to send notifications to teams or connections. See the instructions detailed in Add a Monitor.Method B: Using a Terraform script​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. Identify which deployment your Sumo Logic account is in, using this linkDownload and install Terraform 0.13 or later.Download the Sumo Logic Terraform package for MariaDB alerts. The alerts package is available in the Sumo Logic GitHub repository. You can either download it through the “git clone” command or as a zip file.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.access_id = ""access_key = ""environment = ""The Terraform script installs the alerts without any scope filters, if you would like to restrict the alerts to specific clusters or environments, update the variable mariadb_data_source. Custom filter examples:For a specific cluster, your custom filter would be db_cluster=mariadb.prod.01For all clusters in an environment, your custom filter would be environment=prodFor alerts applicable to all clusters that start with mariadb-prod, your custom filter would be db_cluster=mariadb-prod*For alerts applicable to a specific cluster within a production environment, your custom filter would be db_cluster=mariadb-1 and environment=prod. This The MariaDB app is a unified logs and metrics app that helps you monitor MariaDB database cluster availability, performance, and resource utilization. Pre-configured dashboards and searches provide insight into the health of your database clusters, performance metrics, resource metrics, schema metrics, replication, error logs, slow queries, Innodb operations, failed logins, and error logs.This app is tested with the following MariaDB versions:Kubernetes: MariaDB - Version 10.5.11Non-Kubernetes: MariaDB - Version 10.7.1Collecting logs and metrics for the MariaDB app​Configuring log and metric collection for the MariaDB app includes the following tasks.Step 1: Configure Fields in Sumo Logic​Create the following fields in Sumo Logic before configuring the collection to ensure that your logs and metrics are tagged with relevant metadata, which is required by the app dashboards. For information on setting up fields, see Sumo Logic Fields.Kubernetes environmentsNon-Kubernetes environmentsIf you're using MariaDB in a Kubernetes environment, create the fields:pod_labels_componentpod_labels_environmentpod_labels_db_systempod_labels_db_clusterpod_labels_db_cluster_addresspod_labels_db_cluster_portStep 2: Configure Collection​Sumo Logic supports the collection of logs and metrics data from MariaDB in both Kubernetes and non-Kubernetes environments. Click on the appropriate links below based on the environment where your MariaDB clusters are hosted.Kubernetes environmentsNon-Kubernetes environmentsIn Kubernetes environments, we use the Telegraf Operator, which is packaged with our Kubernetes collection. You can learn more about it here. The diagram below illustrates how data is collected from MariaDB in Kubernetes environments. In the architecture shown below, there are four services that make up the metric collection pipeline:Telegraf, Telegraf Operator, Prometheus, and Sumo Logic Distribution for OpenTelemetry Collector.The first service in the metrics pipeline is Telegraf. Telegraf collects metrics from MariaDB. Note that we’re running Telegraf in each pod we want to collect metrics from as a sidecar deployment, that is Telegraf runs in the same pod as the containers it monitors. Telegraf uses the MySQL Input Plugin to obtain metrics. (For simplicity, the diagram doesn’t show the input plugins.) The injection of the Telegraf sidecar container is done by the Telegraf Operator.Prometheus pulls metrics from Telegraf and sends them to Sumo Logic Distribution for OpenTelemetry Collector which enriches metadata and sends metrics to Sumo Logic.In the logs pipeline, Sumo Logic Distribution for OpenTelemetry Collector collects logs written to standard out and forwards them to another instance of Sumo Logic Distribution for OpenTelemetry Collector, which enriches metadata and sends logs to Sumo Logic.PrerequisitesThese instructions assume that you are using the latest Helm chart version. If not, upgrade using the instructions here.Configure Metrics Collection​This section explains

Sumo Logic vs Loggly - Compare Logging Tools. Sumo Logic - DNSstuff

Sidecarconfig;data:/var/opt/MariaDB/errorlogMake sure that the MariaDB pods are running and annotations are applied by using the command:kubectl describe pod MariaDB_pod_name>Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.Verify logs in Sumo Logic.Add an FER to normalize the fields in Kubernetes environments. This step is not needed if using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Proxy Application Components:Classic UI. In the main Sumo Logic menu, select Manage Data > Logs > Field Extraction Rules. New UI. In the top menu select Configuration, and then under Logs select Field Extraction Rules. You can also click the Go To... menu at the top of the screen and select Field Extraction Rules.Click the + Add button on the top right of the table.The Add Field Extraction Rule form will appear:Enter the following options:Rule Name. Enter the name as App Observability - database.Applied At. Choose Ingest TimeScope. Select Specific DataScope. Enter the following keyword search expression:pod_labels_environment=* pod_labels_component=databasepod_labels_db_cluster=* pod_labels_db_system=*Parse Expression. Enter the following parse expression:if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment | pod_labels_component as component | pod_labels_db_system as db_system | if (!isEmpty(pod_labels_db_cluster), pod_labels_db_cluster, null) as db_clusterClick Save to create the rule.Installing the MariaDB Monitors​The next few sections provide instructions for installing the MariaDB Monitors app, as well as examples of each of the app dashboards. These instructions assume you have already set up the collection as described in the Collect Logs and Metrics for the MariaDB app page.Pre-Packaged Alerts​Sumo Logic has provided out-of-the-box alerts available through Sumo Logic monitors to help you monitor your MariaDB clusters. These alerts are built based on metrics and logs datasets and include preset thresholds based on industry best practices and recommendations. See Alerts for more information.To install these alerts, you need to have the Manage Monitors role capability.Alerts can be installed by either importing a JSON file or a Terraform script.There are limits to how many alerts can be enabled - see the Alerts FAQ for details.Method A: Importing a JSON file​Download the JSON file that describes the monitors.The JSON contains the alerts that are based on Sumo Logic searches that do not have any scope filters and therefore will be applicable to all MariaDB clusters, the data for which has been collected via. Sumo Logic QuickStart - Download as a PDF or view online for free. Sumo Logic QuickStart - Download as a PDF or view online for free. Submit Search. Sumo Logic QuickStart Download as PPTX, PDF 0 likes 2. Sumo Logic. QuickStart your Sumo Logic service with this exclusive webinar. At these monthly live events you will learn Read our blog to get a closer look at Sumo Logic’s ServiceNow Connectors. Learn more about how Sumo partners with ServiceNow. Visit the ServiceNow Store to download Sumo Logic’s Connectors . Request a demo. Sign up for a free trial of Sumo Logic. About Sumo Logic

Installing Telegraf for Sumo Logic

As it will cause the Sumo Logic app to not function correctly.telegraf.influxdata.com/class: sumologic-prometheus. This instructs the Telegraf operator what output to use. This should not be changed.prometheus.io/scrape: "true". This ensures our Prometheus will scrape the metrics.prometheus.io/port: "9273". This tells prometheus what ports to scrape on. This should not be changed.telegraf.influxdata.com/inputsIn the tags section ([inputs.mysql.tags]):component: “database” - This value is used by Sumo Logic apps to identify application components.db_system: “mariadb” - This value identifies the database system.See this doc for more parameters that can be configured in the Telegraf agent globally.Sumo Logic Kubernetes collection will automatically start collecting metrics from the pods having the labels and annotations defined in the previous step.Verify metrics in Sumo Logic.Configure Logs Collection​This section explains the steps to collect MariaDB logs from a Kubernetes environment.(Recommended Method) Add labels on your MariaDB pods to capture logs from standard output. Make sure that the logs from MariaDB are sent to stdout. Follow the instructions below to capture MariaDB logs from stdout on Kubernetes.Apply following labels to the MariaDB pod:environment: "prod_ENV_TO_BE_CHANGED"component: "database"db_system: "mariadb"db_cluster "Cluster_ENV_TO_BE_CHANGED"db_cluster_address = "ENV_TO_BE_CHANGED"db_cluster_port = "ENV_TO_BE_CHANGED"Enter in values for the following parameters (marked in "ENV_TO_BE_CHANGED" above):environment. This is the deployment environment where the MariaDB cluster identified by the value of servers resides. For example: dev, prod, or QA. While this value is optional, we highly recommend setting it.db_cluster. Enter a name to identify this MariaDB cluster. This cluster name will be shown in the Sumo Logic dashboards. If you haven’t defined a cluster in MariaDB, then enter default for db_cluster.Do not modify the following values as it will cause the Sumo Logic apps to not function correctly.component: “database” - This value is used by Sumo Logic apps to identify application components.db_system: “mariadb” - This value identifies the database system.See this doc for more parameters that can be configured in the Telegraf agent globally.The Sumologic-Kubernetes-Collection will automatically capture the logs from stdout and will send the logs to Sumologic. For more information on deploying Sumologic-Kubernetes-Collection, visit here.Verify logs in Sumo Logic.(Optional) Collecting MariaDB Logs from a Log File. Follow the steps below to capture MariaDB logs from a log file on Kubernetes.Determine the location of the MariaDB log file on Kubernetes. This can be determined from the server.conf for your MariaDB cluster along with the mounts on the MariaDB pods.Install the Sumo Logic tailing sidecar operator.Add the following annotation in addition to the existing annotations.annotations: tailing-sidecar: sidecarconfig;>:>/>Example:annotations: tailing-sidecar: Duo provides two-factor authentication, endpoint remediation, and secure single sign-on tools. The Sumo Logic App for Duo Security helps you monitor your Duo account’s authentication logs, administrator logs, and telephony logs. The dashboards provide insight into failed and successful authentications, events breakdown by applications, factors, and users, geo-location of events, admin activities, outliers, threat analysis of authentication, and administrator events.Log types​The Duo Security App uses following logs. Refer to the Duo documentation for details of the log schema.When you generate the Duo credentials, you should do it for the Admin API application.Authentication logsAdministrator logsTelephony logsCollection configuration and app installation​Depending on the set up collection method, you can configure and install the app in three ways:Create a new collector and install the app. Create a new Sumo Logic Cloud-to-Cloud (C2C) source under a new Sumo Logic Collector and later install the app, orUse an existing collector and install the app. Create a new Sumo Logic Cloud-to-Cloud (C2C) source under an existing Sumo Logic Collector and later install the app, orUse existing source and install the app. Use your existing configured Sumo Logic Cloud-to-Cloud (C2C) source and install the app.infoUse the Cloud-to-Cloud Integration for Duo Security to create the source and use the same source category while installing the app. By following these steps, you can ensure that your Duo Security app is properly integrated and configured to collect and analyze your Duo Security data.Create a new collector and install the app​To set up collection and install the app, do the following:Select App Catalog.In the 🔎 Search Apps field, run a search for your desired app, then select it.Click Install App.noteSometimes this button says Add Integration.In the Set Up Collection section of your respective app, select Create a new Collector.Collector Name. Enter a Name to display for the Source in the Sumo Logic web application. The description is optional.Timezone. Set the default time zone when it is not extracted from the log timestamp. Time zone settings on Sources override a Collector time zone setting.(Optional) Metadata. Click the +Add Metadata link to add custom log Metadata Fields. Define the fields you want to associate, each metadata field needs a name (key) and value. A green circle with a check mark is shown when the field exists and is enabled in the Fields table schema. An orange triangle with an exclamation point is shown when the field doesn't exist, or is disabled, in the

Upgrade Collectors in Sumo Logic

Kafka App for Sumo Logic Monitor the availability, performance and resource utilization of Kafka messaging/streaming clusters with Sumo Logic dashboards and alerts Deep visibility into the operations of your Kafka clusters " data-src=" width="64" height="64" alt="Icon monitor release candidates 2 color"> Comprehensive Kafka Node monitoring Comprehensive monitoring of Kafka broker and zookeeper nodes to get insights into requests, responses, throughput connections, sessions, partitions, controllers and resource utilization Get insight into Kafka Topics Gives you insight into the throughput and partitions of Kafka topics " data-src=" width="45" height="45" alt="App and integration 2 color"> Replication Monitoring Understand the state of replicas in your Kafka cluster Kafka Broker Monitoring Get detailed and summary views of the state of your partitions, active controllers, leaders, throughput, and network across Kafka brokers. Kafka Topic Monitoring Get detailed and summary views into throughput, partition sizes and offsets across Kafka brokers, topics and clusters. Kafka Alerts Pre-packaged Sumo Logic alerts help you monitor your Kafka cluster, are based on Sumo Logic monitors, leverage metrics and logs, and include preset thresholds for high resource utilization, disk usage, errors, failed connections, under replicated and offline partitions, unavailable replicas, consumer replica lag and other critical conditions. Related applications

Navigate Kubernetes with Sumo Logic

Gain endpoint security with Carbon Black and Sumo Logic Correlate, validate and investigate Carbon Black EDR and Carbon Black Cloud Endpoint Standard alerts " data-src=" width="64" height="64" alt="Valuable Security Insights"> Monitor potential threats Monitor the state of your network infrastructure and systems with detected threats, hosts, top feeds and IOC’s, top processes, top watchlists, and alert trends " data-src=" width="64" height="64" alt="Detect"> Detect outliers See detailed information on the alerts in your environment, including alerts by mode, OS, report, and groups " data-src=" width="64" height="64" alt="Comprehensive Analytics"> Correlate processes and feeds Gain insight on total feeds, feed trends, top and recent feeds, feed comparisons, and processes related to feeds Pre-built Sumo Logic Carbon Black Dashboards Sumo Logic provides a single pane of glass to reduce the complexity of managing multiple environments, with pre-configured, user friendly and customizable dashboards that take Carbon Black data and layers-on rich graphical reporting and depictions of trends over time. Detect Spikes of Endpoint Alerts See a high-level view of the state of your endpoint security, showing the number of detected threats, alerts, indicators of compromise, devices, users, and groups. The dashboard also highlight alert trends, top users, indicators, devices, applications, and reasons. Related applications Ready to work smarter with your data? Get up and running in minutes. Start your free trial today!. Sumo Logic QuickStart - Download as a PDF or view online for free. Sumo Logic QuickStart - Download as a PDF or view online for free. Submit Search. Sumo Logic QuickStart Download as PPTX, PDF 0 likes 2. Sumo Logic. QuickStart your Sumo Logic service with this exclusive webinar. At these monthly live events you will learn Read our blog to get a closer look at Sumo Logic’s ServiceNow Connectors. Learn more about how Sumo partners with ServiceNow. Visit the ServiceNow Store to download Sumo Logic’s Connectors . Request a demo. Sign up for a free trial of Sumo Logic. About Sumo Logic

What's New - Sumo Logic

Remote workforce? Get full visibility, management, and security for your VPN & SaaS services Try it free for 30 days. No credit card required. Please enter a valid email address. Start free trial No credit card required " data-src="/page/img/email.svg" width="512" height="512" role="presentation"> Please check your inbox To start using Sumo Logic, please click the activation link in the email sent from us. We sent an email to: [email protected]@[email protected] " data-src="/page/img/logo.svg" width="570" height="107" alt="Sumo Logic"> Remote workforce? No credit card required. Up and running in minutes. You're in good companyMore than 2,100 enterprises around the world rely on Sumo Logic to build, run, and secure their modern applications and cloud infrastructures. Apps Remote Access VPNs SSO Your enterprise depends on many services to keep your employees productive and engaged. Keep these services reliable and secure. " data-src=" width="64" height="64" alt="Icon Saa S service 2 color"> Zoom and SaaS Apps Ensure visibility, reliability, and security for Zoom, Github, G Suite, Jira , Office 365, Salesforce, Slack " data-src=" width="64" height="64" alt="Icon parsing data 2 color"> VPN Services Ensure visibility, reliability, and security for Cisco Meraki, Zscaler, Palo Alto Networks solutions " data-src=" width="64" height="64" alt="Icon role based 2 color"> Remote Access and SSO Ensure visibility, reliability, and security for Auth0, Duo, Okta, One Login, Azure AD " data-src=" width="42" height="64" alt="Icon security 2 color"> Endpoint Security Get analytics for remote endpoints security solutions like Crowdstrike Falcon, VMware Carbon Black, Cylance

Comments

User5701

The instructions in the previous sections. However, if you would like to restrict these alerts to specific clusters or environments, update the JSON file by replacing the text db_system=mariadb with . Custom filter examples:For alerts applicable only to a specific cluster, your custom filter would be db_cluster=mariadb-prod.01.For alerts applicable to all clusters that start with Kafka-prod, your custom filter would be db_cluster=mariadb-prod*.For alerts applicable to a specific cluster within a production environment, your custom filter would be db_cluster=mariadb-1 and environment=prod. This assumes you have set the optional environment tag while configuring collection.Classic UI. In the main Sumo Logic menu, select Manage Data > Monitoring > Monitors. New UI. In the main Sumo Logic menu, select Alerts > Monitors. You can also click the Go To... menu at the top of the screen and select Monitors.Click Add.Click Import and then copy-paste the above JSON to import monitors.The monitors are disabled by default. Once you have installed the alerts using this method, navigate to the MariaDB folder under Monitors to configure them. See this document to enable monitors to send notifications to teams or connections. See the instructions detailed in Add a Monitor.Method B: Using a Terraform script​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. Identify which deployment your Sumo Logic account is in, using this linkDownload and install Terraform 0.13 or later.Download the Sumo Logic Terraform package for MariaDB alerts. The alerts package is available in the Sumo Logic GitHub repository. You can either download it through the “git clone” command or as a zip file.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.access_id = ""access_key = ""environment = ""The Terraform script installs the alerts without any scope filters, if you would like to restrict the alerts to specific clusters or environments, update the variable mariadb_data_source. Custom filter examples:For a specific cluster, your custom filter would be db_cluster=mariadb.prod.01For all clusters in an environment, your custom filter would be environment=prodFor alerts applicable to all clusters that start with mariadb-prod, your custom filter would be db_cluster=mariadb-prod*For alerts applicable to a specific cluster within a production environment, your custom filter would be db_cluster=mariadb-1 and environment=prod. This

2025-04-17
User1613

The MariaDB app is a unified logs and metrics app that helps you monitor MariaDB database cluster availability, performance, and resource utilization. Pre-configured dashboards and searches provide insight into the health of your database clusters, performance metrics, resource metrics, schema metrics, replication, error logs, slow queries, Innodb operations, failed logins, and error logs.This app is tested with the following MariaDB versions:Kubernetes: MariaDB - Version 10.5.11Non-Kubernetes: MariaDB - Version 10.7.1Collecting logs and metrics for the MariaDB app​Configuring log and metric collection for the MariaDB app includes the following tasks.Step 1: Configure Fields in Sumo Logic​Create the following fields in Sumo Logic before configuring the collection to ensure that your logs and metrics are tagged with relevant metadata, which is required by the app dashboards. For information on setting up fields, see Sumo Logic Fields.Kubernetes environmentsNon-Kubernetes environmentsIf you're using MariaDB in a Kubernetes environment, create the fields:pod_labels_componentpod_labels_environmentpod_labels_db_systempod_labels_db_clusterpod_labels_db_cluster_addresspod_labels_db_cluster_portStep 2: Configure Collection​Sumo Logic supports the collection of logs and metrics data from MariaDB in both Kubernetes and non-Kubernetes environments. Click on the appropriate links below based on the environment where your MariaDB clusters are hosted.Kubernetes environmentsNon-Kubernetes environmentsIn Kubernetes environments, we use the Telegraf Operator, which is packaged with our Kubernetes collection. You can learn more about it here. The diagram below illustrates how data is collected from MariaDB in Kubernetes environments. In the architecture shown below, there are four services that make up the metric collection pipeline:Telegraf, Telegraf Operator, Prometheus, and Sumo Logic Distribution for OpenTelemetry Collector.The first service in the metrics pipeline is Telegraf. Telegraf collects metrics from MariaDB. Note that we’re running Telegraf in each pod we want to collect metrics from as a sidecar deployment, that is Telegraf runs in the same pod as the containers it monitors. Telegraf uses the MySQL Input Plugin to obtain metrics. (For simplicity, the diagram doesn’t show the input plugins.) The injection of the Telegraf sidecar container is done by the Telegraf Operator.Prometheus pulls metrics from Telegraf and sends them to Sumo Logic Distribution for OpenTelemetry Collector which enriches metadata and sends metrics to Sumo Logic.In the logs pipeline, Sumo Logic Distribution for OpenTelemetry Collector collects logs written to standard out and forwards them to another instance of Sumo Logic Distribution for OpenTelemetry Collector, which enriches metadata and sends logs to Sumo Logic.PrerequisitesThese instructions assume that you are using the latest Helm chart version. If not, upgrade using the instructions here.Configure Metrics Collection​This section explains

2025-04-18
User2961

Sidecarconfig;data:/var/opt/MariaDB/errorlogMake sure that the MariaDB pods are running and annotations are applied by using the command:kubectl describe pod MariaDB_pod_name>Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.Verify logs in Sumo Logic.Add an FER to normalize the fields in Kubernetes environments. This step is not needed if using application components solution terraform script. Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Proxy Application Components:Classic UI. In the main Sumo Logic menu, select Manage Data > Logs > Field Extraction Rules. New UI. In the top menu select Configuration, and then under Logs select Field Extraction Rules. You can also click the Go To... menu at the top of the screen and select Field Extraction Rules.Click the + Add button on the top right of the table.The Add Field Extraction Rule form will appear:Enter the following options:Rule Name. Enter the name as App Observability - database.Applied At. Choose Ingest TimeScope. Select Specific DataScope. Enter the following keyword search expression:pod_labels_environment=* pod_labels_component=databasepod_labels_db_cluster=* pod_labels_db_system=*Parse Expression. Enter the following parse expression:if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment | pod_labels_component as component | pod_labels_db_system as db_system | if (!isEmpty(pod_labels_db_cluster), pod_labels_db_cluster, null) as db_clusterClick Save to create the rule.Installing the MariaDB Monitors​The next few sections provide instructions for installing the MariaDB Monitors app, as well as examples of each of the app dashboards. These instructions assume you have already set up the collection as described in the Collect Logs and Metrics for the MariaDB app page.Pre-Packaged Alerts​Sumo Logic has provided out-of-the-box alerts available through Sumo Logic monitors to help you monitor your MariaDB clusters. These alerts are built based on metrics and logs datasets and include preset thresholds based on industry best practices and recommendations. See Alerts for more information.To install these alerts, you need to have the Manage Monitors role capability.Alerts can be installed by either importing a JSON file or a Terraform script.There are limits to how many alerts can be enabled - see the Alerts FAQ for details.Method A: Importing a JSON file​Download the JSON file that describes the monitors.The JSON contains the alerts that are based on Sumo Logic searches that do not have any scope filters and therefore will be applicable to all MariaDB clusters, the data for which has been collected via

2025-04-16
User2436

As it will cause the Sumo Logic app to not function correctly.telegraf.influxdata.com/class: sumologic-prometheus. This instructs the Telegraf operator what output to use. This should not be changed.prometheus.io/scrape: "true". This ensures our Prometheus will scrape the metrics.prometheus.io/port: "9273". This tells prometheus what ports to scrape on. This should not be changed.telegraf.influxdata.com/inputsIn the tags section ([inputs.mysql.tags]):component: “database” - This value is used by Sumo Logic apps to identify application components.db_system: “mariadb” - This value identifies the database system.See this doc for more parameters that can be configured in the Telegraf agent globally.Sumo Logic Kubernetes collection will automatically start collecting metrics from the pods having the labels and annotations defined in the previous step.Verify metrics in Sumo Logic.Configure Logs Collection​This section explains the steps to collect MariaDB logs from a Kubernetes environment.(Recommended Method) Add labels on your MariaDB pods to capture logs from standard output. Make sure that the logs from MariaDB are sent to stdout. Follow the instructions below to capture MariaDB logs from stdout on Kubernetes.Apply following labels to the MariaDB pod:environment: "prod_ENV_TO_BE_CHANGED"component: "database"db_system: "mariadb"db_cluster "Cluster_ENV_TO_BE_CHANGED"db_cluster_address = "ENV_TO_BE_CHANGED"db_cluster_port = "ENV_TO_BE_CHANGED"Enter in values for the following parameters (marked in "ENV_TO_BE_CHANGED" above):environment. This is the deployment environment where the MariaDB cluster identified by the value of servers resides. For example: dev, prod, or QA. While this value is optional, we highly recommend setting it.db_cluster. Enter a name to identify this MariaDB cluster. This cluster name will be shown in the Sumo Logic dashboards. If you haven’t defined a cluster in MariaDB, then enter default for db_cluster.Do not modify the following values as it will cause the Sumo Logic apps to not function correctly.component: “database” - This value is used by Sumo Logic apps to identify application components.db_system: “mariadb” - This value identifies the database system.See this doc for more parameters that can be configured in the Telegraf agent globally.The Sumologic-Kubernetes-Collection will automatically capture the logs from stdout and will send the logs to Sumologic. For more information on deploying Sumologic-Kubernetes-Collection, visit here.Verify logs in Sumo Logic.(Optional) Collecting MariaDB Logs from a Log File. Follow the steps below to capture MariaDB logs from a log file on Kubernetes.Determine the location of the MariaDB log file on Kubernetes. This can be determined from the server.conf for your MariaDB cluster along with the mounts on the MariaDB pods.Install the Sumo Logic tailing sidecar operator.Add the following annotation in addition to the existing annotations.annotations: tailing-sidecar: sidecarconfig;>:>/>Example:annotations: tailing-sidecar:

2025-04-07
User3980

Duo provides two-factor authentication, endpoint remediation, and secure single sign-on tools. The Sumo Logic App for Duo Security helps you monitor your Duo account’s authentication logs, administrator logs, and telephony logs. The dashboards provide insight into failed and successful authentications, events breakdown by applications, factors, and users, geo-location of events, admin activities, outliers, threat analysis of authentication, and administrator events.Log types​The Duo Security App uses following logs. Refer to the Duo documentation for details of the log schema.When you generate the Duo credentials, you should do it for the Admin API application.Authentication logsAdministrator logsTelephony logsCollection configuration and app installation​Depending on the set up collection method, you can configure and install the app in three ways:Create a new collector and install the app. Create a new Sumo Logic Cloud-to-Cloud (C2C) source under a new Sumo Logic Collector and later install the app, orUse an existing collector and install the app. Create a new Sumo Logic Cloud-to-Cloud (C2C) source under an existing Sumo Logic Collector and later install the app, orUse existing source and install the app. Use your existing configured Sumo Logic Cloud-to-Cloud (C2C) source and install the app.infoUse the Cloud-to-Cloud Integration for Duo Security to create the source and use the same source category while installing the app. By following these steps, you can ensure that your Duo Security app is properly integrated and configured to collect and analyze your Duo Security data.Create a new collector and install the app​To set up collection and install the app, do the following:Select App Catalog.In the 🔎 Search Apps field, run a search for your desired app, then select it.Click Install App.noteSometimes this button says Add Integration.In the Set Up Collection section of your respective app, select Create a new Collector.Collector Name. Enter a Name to display for the Source in the Sumo Logic web application. The description is optional.Timezone. Set the default time zone when it is not extracted from the log timestamp. Time zone settings on Sources override a Collector time zone setting.(Optional) Metadata. Click the +Add Metadata link to add custom log Metadata Fields. Define the fields you want to associate, each metadata field needs a name (key) and value. A green circle with a check mark is shown when the field exists and is enabled in the Fields table schema. An orange triangle with an exclamation point is shown when the field doesn't exist, or is disabled, in the

2025-04-03
User3126

Kafka App for Sumo Logic Monitor the availability, performance and resource utilization of Kafka messaging/streaming clusters with Sumo Logic dashboards and alerts Deep visibility into the operations of your Kafka clusters " data-src=" width="64" height="64" alt="Icon monitor release candidates 2 color"> Comprehensive Kafka Node monitoring Comprehensive monitoring of Kafka broker and zookeeper nodes to get insights into requests, responses, throughput connections, sessions, partitions, controllers and resource utilization Get insight into Kafka Topics Gives you insight into the throughput and partitions of Kafka topics " data-src=" width="45" height="45" alt="App and integration 2 color"> Replication Monitoring Understand the state of replicas in your Kafka cluster Kafka Broker Monitoring Get detailed and summary views of the state of your partitions, active controllers, leaders, throughput, and network across Kafka brokers. Kafka Topic Monitoring Get detailed and summary views into throughput, partition sizes and offsets across Kafka brokers, topics and clusters. Kafka Alerts Pre-packaged Sumo Logic alerts help you monitor your Kafka cluster, are based on Sumo Logic monitors, leverage metrics and logs, and include preset thresholds for high resource utilization, disk usage, errors, failed connections, under replicated and offline partitions, unavailable replicas, consumer replica lag and other critical conditions. Related applications

2025-04-12

Add Comment