Skip to content

Commit f8d3759

Browse files
committed
fix broken images in migrated blogposts
1 parent ef7646a commit f8d3759

File tree

20 files changed

+1377
-23
lines changed

20 files changed

+1377
-23
lines changed

content/en/blog/insights/2017-05-03-jaxenter_sakuli_e2e_testing_and_monitoring/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
author: Tobias Schneck
33
author_url: https://twitter.com/toschneck
44
date: '2017-05-03'
5-
featured_image: sakuli_e2e_testing_and_monitoring.png
5+
featured_image: ./sakuli_e2e_testing_and_monitoring.png
66
meta_description: End-2-End-Testing als auch -Monitoring darf die Oberflächentechnologie
77
eine Rolle spielen, genau an diesem Punkt setzt das Open-Source-Tool Sakuli an.
88
tags:
99
- Sakuli
1010
title: JAXenter - Sakuli End-2-End-Testing und -Monitoring im Container-Zeitalter
1111
---
1212

13-
<div style="position: relative; float: right; margin-right: 1em; margin-bottom: 1em;"><img src="{{page.featured_image}}"></div>
13+
<div style="position: relative; float: right; margin-right: 1em; margin-bottom: 1em;"><img src="./sakuli_e2e_testing_and_monitoring.png" style="float: right; margin: 0 1em 1em; max-width: 200px;"></div>
1414

1515
Sowohl End-2-End-Testing als auch End-2-End-Monitoring folgen dem gleichen Paradigma – sie betrachten eine Applikation aus der Sicht des End-Users. Hier darf es keine Rolle spielen, in welcher Oberflächentechnologie die Applikation geschrieben ist oder in welcher Art sie mit dem End-User in Verbindung tritt. Genau an diesem Punkt setzt das Open-Source-Tool Sakuli an.
1616

content/en/blog/insights/2017-11-17-sakuli-tutorial-docker-xfce-omd-grafana/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: Tobias Schneck
33
author_url: https://twitter.com/toschneck
44
date: '2017-11-17T17:00:00+02:00'
5-
featured_image: omd_error_grafana_small.png
5+
featured_image: ./omd_error_grafana_small.png
66
meta_description: Sakuli Tutorial of docker based E2E application monitoring with
77
Xfce UI and OMD Labs. Implemented with headless VNC environments for Ubuntu, Centos.
88
Provides Docker, Openshift, Kubernetes, Continuous Integration. Testautomation.
@@ -11,7 +11,7 @@ tags:
1111
title: Sakuli Tutorial - Docker based E2E application monitoring
1212
---
1313

14-
<div style="position: relative; float: right; margin-right: 1em; margin-bottom: 1em; width: 40%;"><img src="{{page.featured_image}}"></div>
14+
<div style="position: relative; float: right; margin-right: 1em; margin-bottom: 1em; width: 40%;"><img src="./omd_error_grafana_small.png" style="float: right; margin: 0 1em 1em; max-width: 200px;"></div>
1515

1616
The Tutorial "Docker based E2E application monitoring with Xfce UI and OMD Labs" describes how to:
1717

@@ -291,7 +291,7 @@ To add the above service configuration to the OMD, we will use the predefined Do
291291
292292
- name: Copy mod-gearman config file
293293
copy:
294-
src: "{{ item }}"
294+
src: "{{ "{{" }}item }}"
295295
dest: /opt/omd/sites/demo/etc/mod-gearman/
296296
owner: demo
297297
with_fileglob:

content/en/blog/insights/2018-01-19-openshift_application_monitoring/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
author: Olaf Meyer
33
author_url: https://twitter.com/ola_mey
44
date: '2018-01-19'
5-
featured_image: OpenShift-Logo.png
5+
featured_image: ./OpenShift-Logo.png
66
meta_description: Monitoring of applications running on OpenShift with Prometheus
77
and Grafana without cluster wide permissions.
88
tags:
99
- openshift
1010
title: Application monitoring in OpenShift with Prometheus and Grafana
1111
---
1212

13-
<div style="position: relative; float: right; margin-right: 1em; margin-bottom: 1em;"><img src="{{page.featured_image}}"></div>
13+
<div style="position: relative; float: right; margin-right: 1em; margin-bottom: 1em;"><img src="./OpenShift-Logo.png" style="float: right; margin: 0 1em 1em; max-width: 200px;"></div>
1414

1515
There are a lot of articles that show how to monitor an [OpenShift](https://www.openshift.com/) cluster (including the monitoring of Nodes and the underlying hardware) with [Prometheus](https://prometheus.io/) running in the same OpenShift cluster. This article however is based on a different scenario: You are responsible for an application on an [OpenShift](https://www.openshift.org/) cluster and want to monitor just this application, but you don't have any administrative permission on it. The reason for this can be that you are working in a big company where the operation of the OpenShift environment is outsourced or the process to introduce a new monitoring solution takes way too long or the current monitoring solution doesn't match your requirements and so on.
1616

content/en/blog/insights/2018-01-24-dynamic-icons-thruk/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
author: Simon Meggle
33
author_url: https://twitter.com/simonmeggle
44
date: '2018-01-24'
5-
featured_image: thruk_firewallcluster.png
5+
featured_image: ./thruk_firewallcluster.png
66
meta_description: Wie man mit check_nwc_health und Thruk eine visuelle Statusanzeige
77
von Firewall-Clusternodes baut
88
tags:
99
- monitoring
1010
title: Visualisierung von Firewall-Clusternodes mit Thruk und check_nwc_health
1111
---
1212

13-
<div style="position: relative; float: right; margin-right: 1em; margin-bottom: 1em;"><img src="{{page.featured_image}}"></div>
13+
<div style="position: relative; float: right; margin-right: 1em; margin-bottom: 1em;"><img src="./thruk_firewallcluster.png" style="float: right; margin: 0 1em 1em; max-width: 200px;"></div>
1414

1515
In diesem Blogartikel wird gezeigt, wie das Monitoring-Plugin [check_nwc_health](https://labs.consol.de/de/nagios/check_nwc_health/) auf eigene Bedürfnisse angepasst bzw. erweitert werden kann.
1616

30.3 KB
Loading

content/en/blog/insights/2018-03-01-database-testing-with-citrus/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@
22
author: Sven Hettwer
33
author_url: https://twitter.com/SvenHettwer
44
date: '2018-03-01'
5-
featured_image: /assets/images/citrus_logo.png
5+
featured_image: ./citrus_logo.png
66
meta_description: Learn how to test your database communication with citrus
77
tags:
88
- citrus
99
title: Database testing with Citrus
1010
---
1111

12-
<div style="position: relative; float: right; margin-right: 1em; margin-bottom: 1em;"><img src="{{page.featured_image}}"></div>
12+
<div style="position: relative; float: right; margin-right: 1em; margin-bottom: 1em;"><img src="./citrus_logo.png" style="float: right; margin: 0 1em 1em; max-width: 200px;"></div>
1313

1414
Database communication is an essential part of many applications, when persistent data storage is required. May it be orders, customer data, product recommendations or product information, if persistent storage is in place, the data contains a certain business value. Therefore it's important that your software handles your persistent storage the right way.
1515

93.9 KB
Loading
33.3 KB
Loading

0 commit comments

Comments
 (0)