Filtering Logs with Splunk

Filtering system paths of logs with Splunk

The file system paths of DC/OS task logs contain information such as the agent ID, framework ID, and executor ID. You can use this information to filter the log output for specific tasks, applications, or agents.

Prerequisite

Configuration

You can configure Splunk either by using the Splunk Web interface or by editing the props.conf file.

Splunk web interface

  1. Navigate to Settings -> Fields -> Field Extractions -> New.

  2. Fill out the form with the following:

    • Destination app: search
    • Name: dcos_task (or any unique, meaningful name for the extraction)
    • Apply to source named /var/lib/mesos/slave/...
    • Type: Inline

    • Extraction/Transform:

      1. /var/lib/mesos/slave/slaves/(?<agent>[^/]+)/frameworks/(?<framework>[^/]+)/executors/(?<executor>[^/]+)/runs/(?<run>[^/]+)/.* in source

  3. Click Save.

  4. In the Field Extractions view, find the extraction you just created and set the permissions appropriately. The agent, framework, executor, and run fields should now be available to use in search queries and appear in the fields associated with Mesos task log events.

props.conf

  1. Add the following entry to props.conf (see the Splunk documentation for details):

    1. [source::/var/lib/mesos/slave/...]
    2. EXTRACT = /var/lib/mesos/slave/slaves/(?<agent>[^/]+)/frameworks/(?<framework>[^/]+)/executors/(?<executor>[^/]+)/runs/(?<run>[^/]+)/.* in source

  2. Run the following search in the Splunk Web interface to ensure the changes take effect:

    1. extract reload=true

The agent, framework, executor, and run fields should now be available to use in search queries and appear in the fields associated with Mesos task log events.

Usage example

  1. In the Splunk web interface, type framework=* into the Search field. This will show all of the events where the framework field is defined:

    Splunk Framework Exists

    Figure 1. Splunk events screen

  2. Click the disclosure triangle next to one of these events to view the details. This will show all of the fields extracted from the task log file path:

    Splunk Fields

    Figure 2. Fields in the task log file path

  3. Search for all of the events that reference the framework ID of the event shown in the screenshot above, but that do not contain the chosen framework field. This will show us only non-task results:

    Splunk Framework Search

    Figure 3. Search results

Template examples

Here are example query templates for aggregating the DC/OS logs with Splunk. Replace the template parameters $executor1, $framework2, and any others with actual values from your cluster.

IMPORTANT: Do not change the quotation marks in these examples or the queries will not work. If you create custom queries, be careful with the placement of quotation marks.

  • Logs related to a specific executor $executor1, including logs for tasks run from that executor:

    1. "$executor1"

  • Non-task logs related to a specific executor $executor1:

    1. "$executor1" AND NOT executor=$executor1

  • Logs (including task logs) for a framework $framework1, if $executor1 and $executor2 are that framework’s executors:

    1. "$framework1" OR "$executor1" OR "$executor2"

  • Non-task logs for a framework $framework1, if $executor1 and $executor2 are that framework’s executors:

    1. ("$framework1" OR "$executor1" OR "$executor2") AND NOT (framework=$framework1 OR executor=$executor1 OR executor=$executor2)

  • Logs for a framework $framework1 on a specific agent host $agent_host1:

    1. host=$agent_host1 AND ("$framework1" OR "$executor1" OR "$executor2")

  • Non-task logs for a framework $framework1 on a specific agent $agent1 with host $agent_host1:

    1. host=$agent_host1 AND ("$framework1" OR "$executor1" OR "$executor2") AND NOT agent=$agent