brew install gpg-suite
brew install yubico-piv-tool
brew install pinentry-mac
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cfg, err := external.LoadDefaultAWSConfig() | |
if err != nil { | |
panic(err) | |
} | |
esCfg := elasticsearch.Config{ | |
Transport: &awssigner.V4Signer{ | |
RoundTripper: http.DefaultTransport, | |
Credentials: cfg.Credentials, | |
Region: cfg.Region, | |
}, |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
package esi | |
import ( | |
"context" | |
"github.com/olivere/elastic" | |
) | |
type BusinessLogic struct { | |
s Searcher |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
set -e | |
# Those should be JENKINS vars | |
NAME=nginx-deployment-3 | |
PODS_COUNT=3 | |
CONTAINER_NAME=nginx | |
DOCKER_IMAGE='nginx:1.8' | |
# Template can be copied from deploy.tmp.yaml to update jenkins var |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
include ::profile::icinga2_global | |
# endpoints will be generated from zone | |
# no host value, so the agent will connect to the master | |
@@::icinga2::object::zone { $::fqdn: | |
parent => 'master', | |
endpoints => { | |
$::fqdn => { | |
}, |
- With Docker 1.8.0 shipped new log-driver for GELF via UDP, this means that the logs from Docker Container(s) can be shipped directly to the ELK stack for further analysis.
- This tutorial will illustrate how to use the GELF log-driver with Docker engine.
- Step 1: Setup ELK Stack:
docker run -d --name es elasticsearch
docker run -d --name logstash --link es:elasticsearch logstash -v /tmp/logstash.conf:/config-dir/logstash.conf logstash logstash -f /config-dir/logstash.conf
- Note the config for Logstash can be found at this link
docker run --link es:elasticsearch -d kibana
- Once the ELK stack is up now let's fire up our nginx container which ships its logs to ELK stack.
LOGSTASH_ADDRESS=$(docker inspect --format '{{ .NetworkSettings.IPAddress }}' logstash)
- `docker run -d --net=host --log-driver=gelf --log-opt gelf-address=u
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
msimmons@nagios:/opt/collectd/etc$ cat collectd.conf | |
# Generated by Puppet | |
#Hostname localhost | |
FQDNLookup true | |
#BaseDir "/var/lib/collectd" | |
#PluginDir "/usr/lib/collectd" | |
#TypesDB "/usr/share/collectd/types.db" "/etc/collectd/my_types.db" | |
Interval 10 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
use GuzzleHttp\Client; | |
trait MailTestHelper | |
{ | |
/** | |
* @var \GuzzleHttp\Client | |
*/ | |
protected $client; |
NewerOlder