portante

file:
    type: dailyRollingFile
    file: ${path.logs}/${cluster.name}.log
    datePattern: "'.'yyyy-MM-dd"
    layout:
      type: pattern
      conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %.10000m%n"

portante

#!/usr/bin/env python

import os, sys, json
from operator import itemgetter

lines = []
try:
    with open(sys.argv[1], "r") as fp:
        for line in fp.readlines():
            doc = json.loads(line)

portante

$ git co -b update-class-master class/master
Branch update-class-master set up to track remote branch master from class.
Switched to a new branch 'update-class-master'
$ git branch --set-upstream-to=upstream/master
Branch update-class-master set up to track remote branch master from upstream.
$ git status
On branch update-class-master
Your branch is behind 'upstream/master' by 2 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
nothing to commit, working tree clean

portante

GTIMESTAMP %{YEAR}-%{MONTHNUM}-%{MONTHDAY} %{TIME}
GMESSAGEID \[MSGID: %{INT:msgid}\]
GSRCINFO \[%{NOTSPACE:srcfile}:%{INT:linenum}:%{NOTSPACE:funcname}\]

GLOGMSGID \[%{GTIMESTAMP:timestamp}\] %{NOTSPACE:level}%{SPACE}%{GMESSAGEID}%{SPACE}%{GSRCINFO}%{SPACE}%{NOTSPACE:subvol}:%{SPACE}%{GREEDYDATA:message}
GLOGNOMSGID \[%{GTIMESTAMP:timestamp}\] %{NOTSPACE:level} %{GSRCINFO} %{NOTSPACE:subvol}:%{SPACE}%{GREEDYDATA:message}
GLOGREPEAT The message \"%{NOTSPACE:level}%{SPACE}%{GMESSAGEID}%{SPACE}%{GSRCINFO}%{SPACE}%{NOTSPACE:subvol}:%{SPACE}%{GREEDYDATA:message}\" repeated %{INT:repeat_count} times between \[%{GTIMESTAMP:timestamp}\] and \[%{GTIMESTAMP:repeat_end}\]

GLUSTERSTACK \[%{GTIMESTAMP:timestamp}\] %{NOTSPACE:level} %{GSRCINFO} \((?'traceback'-->%{SPACE}?%{PATH}%{SPACE}?\(%{NOTSPACE}\) \[%{NOTSPACE}\](%{SPACE}|%{SPACE}\g'traceback'))%{SPACE}\)%{SPACE}%{GREEDYDATA:message}
GLUSTERASSERT \[%{GTIMESTAMP:timestamp}\] %{NOTSPACE:level} %{GSRCINFO} \(--> %{INT}-%{NOTSPACE:component}?: %{GREEDYDATA:message}

portante

#!/bin/bash
function getparent {
    #echo $1 $2
    local link=$(readlink -n -v $1/$2)
    if [ "x$link" == "x" ]; then
        return
    fi
    p_gfid_dn=$(dirname $1/$link) 
    p_gfid=$(basename $p_gfid_dn)
    if [ "$p_gfid" != "00000000-0000-0000-0000-000000000001" ]; then

portante

cluster.name: elasticsearch.patriots

action.disable_delete_all_indices: true

bootstrap.mlockall: true

node.name: "brady"
node.master: true
node.data: true

portante

#!/usr/bin/env python3
#
# es-create-index-aliases
#
# Create the index aliases, making it easier to reference groupings of the
# time series data found there-in.
#

from __future__ import print_function

portante

# Nova compute
<source>
  @type tail
  path /var/log/nova/nova-compute.log
  tag nova.compute

  # The first line of a multiline log entry begins with a timestamp, YYYY-MM-DD
  # HH:MM:SS, and an optional sub-second value using 3 or 6 digits, followed by
  # pid, level, and class. To determine a "first line" we only need to match
  # the beginning part of it, so for OpenStack log lines, those four fields are

portante

 > I like where this is going.  Perhaps we could consider the steps an
 > admin has to take and orient the commands to address what they need
 > to do.
 > 
 > First, having to "kill -9" a process as an interface to stopping a
 > brick seems dicey.
 > 
 > So to that end, perhaps we could two sets of commands, the first to
 > tell gluster to take the brick out of service, allowing the admin
 > to then replace it, and a second command to brick the brick back

portante

# LIVES in /etc/rsyslog.d/ ***
#
# A simple string of "tags" that system administrators can use to identify the
# various roles a system can take on, or categories to consider it under. Use
# whitespace to separate the tags.
set $!tags = "EXAMPLETAG EXAMPLETAGTWO EXAMPLETAGTHREE";