Fixing image rendering and centering
This commit is contained in:
Holger Reinhardt
parent
fa5cad8c49
commit
a86815baba
|
|
@ -51,10 +51,9 @@ Many of the more technical talks dealt with the usual suspects [Microservices an
|
|||
|
||||
The return to more serious topics, *Hypermedia* was an astonishingly big topic at the conference. Not that it's not a seriously good idea, but now adoption seems to find its way into real world scenarios, with practical and working specifications popping up, which are being adopted at an increasing rate. As Hypermedia leaves the state of a research topic (see below picture on [HATEOAS](https://en.wikipedia.org/wiki/HATEOAS) - Bless you!) and is actually being used.
|
||||
|
||||
<center>
|
||||
|
||||
{:.center}
|
||||
{:style="margin:auto"}
|
||||
<small>(Courtesy of [CommitStrip](http://www.commitstrip.com/en/2015/12/03/apiception/))</small>
|
||||
</center>
|
||||
|
||||
Many people are perhaps scared of the seemingly intransparent topic, but there are a lot of really good use cases for hypermedia. Jason Harmon of PayPal/Braintree ([@jharmn](http://twitter.com/jharmn)) pointed to some of the most prominent ones in his talk:
|
||||
|
||||
|
|
|
|||
|
|
@ -27,15 +27,13 @@ You will need the following things, which this how-to does not provide you with:
|
|||
|
||||
To start things, open up the [Azure Portal](https://portal.azure.com) using your favorite web browser, and log in so that you have access to the Azure portal. Then click *Virtual machines (Classic)*, then *Add +*.
|
||||
|
||||
<center>
|
||||
|
||||
</center>
|
||||
{:.center}
|
||||
{:style="margin:auto"}
|
||||
|
||||
Then, search for `ubuntu` and select *Ubuntu Server 14.04 LTS* (I think you can choose a regular Ubuntu, too, but this one definitely works).
|
||||
|
||||
<center>
|
||||
|
||||
</center>
|
||||
{:.center}
|
||||
{:style="margin:auto"}
|
||||
|
||||
Specify the correct settings for the VM. I chose the following specs for the VM:
|
||||
|
||||
|
|
@ -46,9 +44,8 @@ Specify the correct settings for the VM. I chose the following specs for the VM:
|
|||
* Add two endpoints: http (tunnel port 80) and https (tunnel port 443). See image below.
|
||||
* Leave the rest of the setting to the defaults
|
||||
|
||||
<center>
|
||||
|
||||
</center>
|
||||
{:.center}
|
||||
{:style="margin:auto"}
|
||||
|
||||
When you're done and all your settings have been confirmed (*OK*), click the *Create* button to provision your VM.
|
||||
|
||||
|
|
@ -56,9 +53,8 @@ When you're done and all your settings have been confirmed (*OK*), click the *Cr
|
|||
|
||||
This will take some time (around 5 minutes), but after that, you will find the information on your machine in the following way:
|
||||
|
||||
<center>
|
||||
|
||||
</center>
|
||||
{:.center}
|
||||
{:style="margin:auto"}
|
||||
|
||||
The automatically created DNS entry for your machine is displayed there, and this is the name you can use to connect to the machine using your favorite SSH tool (`ssh` if you're on Linux or Mac OS X, e.g PuTTY if you're on Windows).
|
||||
|
||||
|
|
@ -101,15 +97,13 @@ In the first step, Let's Encrypt will ask for an administration email address; t
|
|||
|
||||
After that, you will have to accept the license terms:
|
||||
|
||||
<center>
|
||||
|
||||
</center>
|
||||
{:.center}
|
||||
{:style="margin:auto"}
|
||||
|
||||
In the next step, enter the domain name(s) you want to create the certificate for:
|
||||
|
||||
<center>
|
||||
|
||||
</center>
|
||||
{:.center}
|
||||
{:style="margin:auto"}
|
||||
|
||||
Usually, you will create one certificate per domain you will use. Exceptions will be for example when creating a certificate which is both valid for `www.contoso.com` and `contoso.com`, if your web server answers to both. In this case, we will just provide `myserver.contoso.com` (this might be a web service or similar).
|
||||
|
||||
|
|
|
|||
|
|
@ -19,17 +19,17 @@ The problems it tackles are:
|
|||
- Support for a great number of event sources and outputs
|
||||
|
||||
One of the most prolific open source solutions on the market is the [ELK stack](https://www.elastic.co/videos/introduction-to-the-elk-stack) created by Elastic.
|
||||
<center>
|
||||
<img src="/images/logaggregation-elk.png" width=50% align="middle"/>
|
||||
</center>
|
||||
|
||||
<{:.center}>
|
||||
<img src="/images/logaggregation-elk.png" width=50% align="middle"/>
|
||||
|
||||
ELK stands for Elasticsearch – Logstash – Kibana and they are respectively their Search engine, Log Shipper and Visualization frontend solutions.
|
||||
Elasticsearch becomes the nexus for gathering and storing the log data and it is not exclusive to Logstash.
|
||||
|
||||
Another very good data collection solution on the market is Fluentd, and it also supports Elasticsearch (amongst others) as the destination for it’s gathered data. So using the same data repository and frontend solutions, this becomes the EFK stack and if you do a bit of searching you will discover many people have chosen to substitute Elastic's logstash with FluentD and we will talk about why that is in a minute.
|
||||
<center>
|
||||
<img src="/images/logaggregation-efk.png" width=20% align="middle"/>
|
||||
</center>
|
||||
|
||||
{:.center}
|
||||
<img src="/images/logaggregation-efk.png" width=20% align="middle"/>
|
||||
|
||||
# Logstash vs FluentD
|
||||
Both of them are very capable, have [hundreds](https://www.elastic.co/guide/en/logstash/current/input-plugins.html) and [hundreds](http://www.fluentd.org/plugins) of plugins available and are being maintained actively by corporation backed support.
|
||||
|
|
@ -156,9 +156,8 @@ Sample output from stdout:
|
|||
~~~
|
||||
|
||||
And here is the result of trying to use it in a visualization:
|
||||
<center>
|
||||
<img src="/images/logaggregation-analyzed-field.png" width=35% align="middle"/>
|
||||
</center>
|
||||
{:.center}
|
||||
<img src="/images/logaggregation-analyzed-field.png" width=35% align="middle"/>
|
||||
|
||||
I should mention, what you are seeing is the result of 6 messages that all have the field sourceProject set to the value "Test-Analyzed-Field".
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue