Download 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

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

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: