Skip to main content
Sumo Logic

Collect MariaDB Logs and Metrics for Kubernetes environments

Collection of MariaDB Logs and Metrics for Kubernetes environments.

In a Kubernetes environment, 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
  • Prometheus
  • Fluentd
  • FluentBit

The first service in the 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. We also have Fluentbit that collects logs written to standard out and forwards them to FluentD, which in turn sends all the logs and metrics data to a Sumo Logic HTTP Source.

 

Follow the below instructions to set up the metric collection:

  1. Configure Metrics Collection
    1. Setup Kubernetes Collection with the Telegraf operator
    2. Add annotations on your MariaDB pods
  2. Configure Logs Collection
    1. Configure logging in MariaDB.
    2. Add labels on your MariaDB pods to capture logs from standard output.
    3. Collecting MariaDB Logs from a Log file.

Prerequisites

These instructions assume that you are using the latest Helm chart version. If not, upgrade using the instructions here.

Configure Metrics Collection

This section explains the steps to collect MariaDB metrics from a Kubernetes environment.

In a Kubernetes environment, we use the Telegraf Operator, which is packaged with our Kubernetes collection. You can learn more on this here. Follow the steps listed below to collect metrics from a Kubernetes environment:

  1. Setup Kubernetes Collection with the Telegraf Operator.

  2. Add annotations on your MariaDB pods

On your MariaDB Pods, add the following annotations:

annotations:
    telegraf.influxdata.com/class: sumologic-prometheus
    prometheus.io/scrape: "true"
    prometheus.io/port: "9273"
    telegraf.influxdata.com/inputs: |+

[[inputs.mysql]]
  servers = ["user_TO_BE_CHANGED:password_TO_BE_CHANGED@tcp(IP_ADDRESS_MARIADB_TO_BE_CHANGED:PORT_MARIADB_TO_BE_CHANGED)/?tls=false"]
  metric_version = 2
  table_schema_databases = []
  perf_summary_events = []
  gather_table_schema                       = true
  gather_process_list                       = true
  gather_info_schema_auto_inc               = true
  gather_user_statistics = true
  gather_slave_status = true
  gather_table_io_waits = true
  gather_table_lock_waits = true
  gather_index_io_waits = true
  gather_event_waits = true
  gather_file_events_stats = true
  gather_perf_events_statements = true 
  interval_slow = "30m"
[inputs.mysql.tags]
    environment="TO_BE_CHANGED"
    component="database"
    db_system="mariadb"
    db_cluster="TO_BE_CHANGED"

Enter in values for the following parameters (marked in bold above):

  • telegraf.influxdata.com/inputs - This contains the required configuration for the Telegraf exec Input plugin. Please refer to this doc for more information on configuring the MySQL input plugin for Telegraf. Note: As telegraf will be run as a sidecar the host should always be localhost.
    • In the input plugins section, that is: 
      • servers - The URL of your MariaDB server. For information about additional input plugin configuration options, see the Readme for the MySQL input plugin.
    • In the tags section, that is  [inputs.mysql.tags]
      • 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.  

Here’s an explanation for additional values set by this configuration that we request you to please do not modify as they will cause the Sumo Logic apps 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/inputs
    • In the tags section i.e.  [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.

For all other parameters, please see this doc for more properties that can be configured in the Telegraf agent globally.

  1. Sumo Logic Kubernetes collection will automatically start collecting metrics from the pods having the labels and annotations defined in the previous step. 

  2. Verify metrics in Sumo Logic.

Configure Logs Collection

This section explains the steps to collect MariaDB logs from a Kubernetes environment.

  1. (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 MariaDBlogs from stdout on Kubernetes.

  1. Apply following labels to the MariaDBpod:

labels:
    environment: "prod_CHANGEME"
    component: "database"
    db_system: "mariadb"
    db_cluster "Cluster_CHANGEME”

Enter in values for the following parameters (marked in bold and CHANGE_ME 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.

Here’s an explanation for additional values set by this configuration, but do not modify them as changes 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.

For all other parameters, please see this doc for more properties that can be configured in the Telegraf agent globally.

  1. 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.

  2. Verify logs in Sumo Logic.

  1. (Optional) Collecting MariaDB Logs from a Log File
    Follow the steps below to capture MariaDB logs from a log file on Kubernetes.

  1. 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.

  2. Install the Sumo Logic tailing sidecar operator.

  3. Add the following annotation in addition to the existing annotations.

annotations:
  tailing-sidecar: sidecarconfig;<mount>:<path_of_MariaDB_log_file>/<MariaDB_log_file_name>

Example:

annotations:
  tailing-sidecar: sidecarconfig;data:/var/opt/MariaDB/errorlog
  1. Make sure that the MariaDB pods are running and annotations are applied by using the command: kubectl describe pod <MariaDB_pod_name>

  2. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above. 

  3. Verify logs in Sumo Logic.

  1. Add an FER to normalize the fields in Kubernetes environments
    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:

  1. Go to Manage Data > Logs > Field Extraction Rules.

  2. Click the + Add button on the top right of the table.

  3. The following form appears:

  1. Enter the following options:

  1. Rule Name. Enter the name as App Observability - database.

  2. Applied At. Choose Ingest Time

  3. Scope. Select Specific Data

  4. Scope: Enter the following keyword search expression: 

pod_labels_environment=* pod_labels_component=database pod_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
| pod_labels_db_cluster as db_cluster
  1. Click Save to create the rule.