Örjan Sjöholm orjan

One week of azure

A small wrap up of the AZ400

TL;DR;

Azure devops is a really good service on pair with GitLab CI/CD
Infra as code should be required for any production cases
Really good hosting alternatives for docker images
Check out application insights, compare the apm part with NewRelic in production
Check out immutable VM:s with out ssh access

Gradle

TBD!

gradle dependencies --write-locks

build.gradle.kts

dependencyLocking {

ansible 2.9.3@osx with curl

netcat -l -p 8888
netcat -l -p 9999

export HTTPS_PROXY=http://127.0.0.1:8888
ansible-playbook -i localhost, proxy.yml
# Connecting to 9999

Mina egna tankar

Första frågan är varför har vi stories?

Att de har ett förväntat värde så att de kan prioriteras gentemot andra?
Så att vi inte glömmer dem?
Att vi har ett hum om vad som bör göras?
För att kunna göra en prognos över vad som kommer att göra inom nästa iteration

Personligen så är en bra "story" något som förmedlar värdeskapande, något som teamet kan relatera till och bör kunna leverera som ett team.

	###################### Filebeat Configuration Example #########################

	# This file is an example configuration file highlighting only the most common
	# options. The filebeat.reference.yml file from the same directory contains all the
	# supported options with more comments. You can use it as a reference.
	#
	# You can find the full configuration reference here:
	# https://www.elastic.co/guide/en/beats/filebeat/index.html

	# For more available modules and options, please see the filebeat.reference.yml sample

	## JVM configuration

	# Xms represents the initial size of total heap space
	# Xmx represents the maximum size of total heap space

	-Xms1g
	-Xmx1g

	################################################################
	## Expert settings

	# ======================== Elasticsearch Configuration =========================
	#
	# NOTE: Elasticsearch comes with reasonable defaults for most settings.
	# Before you set out to tweak and tune the configuration, make sure you
	# understand what are you trying to accomplish and the consequences.
	#
	# The primary way of configuring a node is via this file. This template lists
	# the most important settings you may want to configure for a production cluster.
	#
	# Please consult the documentation for further information on configuration options:

	status = error

	appender.console.type = Console
	appender.console.name = console
	appender.console.layout.type = PatternLayout
	appender.console.layout.pattern = [%d{ISO8601}][%-5p][%-25c{1.}] [%node_name]%marker %m%n

	######## Server JSON ############################
	appender.rolling.type = RollingFile
	appender.rolling.name = rolling

	{
	"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
	"contentVersion": "1.0.0.0",
	"parameters": {
	"registryResourceGroupName": {
	"type": "string",
	"defaultValue": "DockerRG",
	"metadata": {
	"description": "The resource group for the docker registry"
	}

	---
	- hosts: all
	vars:
	backup_dir: /Users/orjan/Code/ica/elk/backup
	tasks:
	- name: Create fake backup # With a human reable name e.g. 20200420T215229
	file:
	path: "{{ backup_dir }}/{{ ansible_date_time.iso8601_basic_short }}"
	state: directory
	# An extra thing would be to write, ansible_date_time.iso8601_basic_short to a file in the,