Ahmed viztastic

Need to overwrite remote codebase with new git folder.

Git global setup

git config --global user.name "Ahmed"
git config --global user.email "[email protected]"

Create a new repository

Node wasn't letting me install new modules throwing at me an EACCESS: permission denied error every time.

This did it, it can work in other use cases as well, this one lets you install global packages, but you can change the directory to whichever:

$ sudo chown -R $(whoami) $(npm config get prefix)/{lib/node_modules,bin,share}

Bindings

<input type="text" [(ngModel)] = "componentPropertyName" placeholder="name">

The [(ngModel)] basically means that if I update the textbox, it will update the target variable (in this case componentPropertyName) and reflect it back in the screen.

Looping

SysLog

HL

Based on RFC 3164 UDP: 514 (TCP creates unecessary overhead)

Levels

Emergency
Alert

Elasticsearch

Cluster

Cluster Health

GET /_cat/health?v

Indices

Switching from HTTPS to SSH

Suppose you clone in https mode and then decide to switch to SSH:

$ git remote set-url origin [email protected]:{GIT_PROFILE}/{REPO_NAME}.git

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

Aggregations

Really should checkout the Elastic Aggregations documentation, it's great:

In short, the format is something like this

  "aggregations" : {
      "<aggregation_name>" : {
 "" : {

	Africa/Abidjan
	Africa/Accra
	Africa/Addis_Ababa
	Africa/Algiers
	Africa/Asmara
	Africa/Bamako
	Africa/Bangui
	Africa/Banjul
	Africa/Bissau
	Africa/Blantyre

	[api]: New apis / changes to apis
	[test]: Update test/* files
	[dist]: Changes to submodules, version bumps, updates to package.json
	[minor]: Small changes
	[doc]: Updates to documentation
	[ux]: Updates to UX
	[fix]: Bug fixes
	[bin]: Update binary scripts associated with the project
	[merge]: Resolved git merge from upstream or otherwise
	[refactor]: Refactor of existing code with no external API changes