Updated description of images (screenshots and demos) from image filenames to adequate captions.

Removed description of images from plugin articles as those are right under their respective headings.


Signed-off-by: Azeem Sajid <azeem.sajid@gmail.com>

Author: iamazeem

container-deployment/docker-logging-driver.md

@@ -100,7 +100,7 @@ By default, the Fluentd logging driver will try to find a local Fluentd instance
 (Step # 2) listening for connections on the TCP port `24224`. Note that the
 container will not start if it cannot connect to the Fluentd instance.
 
-![fluentd_docker_integrated.png](https://www.fluentd.org/assets/img/recipes/fluentd_docker_integrated.png)
+![Integration of Docker with Fluentd](https://www.fluentd.org/assets/img/recipes/fluentd_docker_integrated.png)
 
 The following command will run a base Ubuntu container and print some messages
 to the standard output:

container-deployment/kubernetes.md

@@ -1,6 +1,6 @@
 # Kubernetes Logging with Fluentd
 
-![fluentd_kubernetes.png](/images/fluentd_kubernetes.png)
+![Fluentd + Kubernetes](/images/fluentd_kubernetes.png)
 
 [Kubernetes](http://kubernetes.io) provides two logging endpoints for
 applications and cluster logs:

deployment/fluentd-ui.md

@@ -44,7 +44,7 @@ The default account credentials are:
 -   `username="admin"`
 -   `password="changeme"`
 
-![fluentd-ui.gif](/images/fluentd-ui/fluentd-ui.gif)
+![Fluentd UI](/images/fluentd-ui/fluentd-ui.gif)
 
 
 ## Screenshots
@@ -54,26 +54,32 @@ The default account credentials are:
 
 ### Dashboard
 
-![dashboard.gif](/images/fluentd-ui/dashboard.gif)
+![Fluentd UI: Dashboard](/images/fluentd-ui/dashboard.gif)
 
 
 ### Setting
 
-![setting.git](/images/fluentd-ui/setting.gif)
+![Fluentd UI: Settings](/images/fluentd-ui/setting.gif)
 
 
 ### `in_tail` setting
 
-![`in_tail`.gif](/images/fluentd-ui/in_tail.gif)
+![Fluentd UI: `in_tail` Settings](/images/fluentd-ui/in_tail.gif)
 
 
 ### Plugin
 
-![plugin.gif](/images/fluentd-ui/plugin.gif)
+![Plugin](/images/fluentd-ui/plugin.gif)
 
-![ss01](/images/fluentd-ui/01.png) ![ss02](/images/fluentd-ui/02.png)
-![ss03](/images/fluentd-ui/03.png) ![ss04](/images/fluentd-ui/04.png)
-![ss05](/images/fluentd-ui/05.png)
+![](/images/fluentd-ui/01.png)
+
+![](/images/fluentd-ui/02.png)
+
+![](/images/fluentd-ui/03.png)
+
+![](/images/fluentd-ui/04.png)
+
+![](/images/fluentd-ui/05.png)
 
 
 ------------------------------------------------------------------------

deployment/high-availability.md

@@ -39,7 +39,7 @@ describe how to set up Fluentd's topology for high-availability.
 To configure Fluentd for high-availability, we assume that your network
 consists of **log forwarders** and **log aggregators**.
 
-![fluentd_ha.png](/images/fluentd_ha.png)
+![Fluentd's High-Availability Overview](/images/fluentd_ha.png)
 
 '**log forwarders**' are typically installed on every node to receive
 local events. Once an event is received, they forward it to the 'log

deployment/monitoring-prometheus.md

@@ -205,15 +205,15 @@ Now, open this URL `http://localhost:9090/` in your browser.
 Go to `http://localhost:9090/targets` to see the list of Fluentd nodes and their
 status.
 
-![prometheus-targets.png](/images/prometheus-targets.png)
+![Prometheus Targets](/images/prometheus-targets.png)
 
 
 ### List of Fluentd Metrics
 
 Visit `http://localhost:9090/graph` to explore Fluentd's internal metrics.
 You'll see eight (8) metrics in the metric list:
 
-![prometheus-metrics.png](/images/prometheus-metrics.png)
+![Prometheus Metrics](/images/prometheus-metrics.png)
 
 -   `fluentd_input_status_num_records_total`
 -   `fluentd_output_status_buffer_queue_length`
@@ -227,7 +227,7 @@ You'll see eight (8) metrics in the metric list:
 Pick `fluentd_input_status_num_records_total` and you'll see the total incoming
 records per tag.
 
-![prometheus-graph.png](/images/prometheus-graph.png)
+![Prometheus Graph](/images/prometheus-graph.png)
 
 
 ### Example Prometheus Queries
@@ -292,7 +292,7 @@ For more advanced visualization and alerting, we recommend
 
 -   [Grafana Support for Prometheus](https://prometheus.io/docs/visualization/grafana/)
 
-![prometheus-grafana.png](/images/prometheus-grafana.png)
+![Prometheus + Grafana](/images/prometheus-grafana.png)
 
 
 ## Further Readings

deployment/multi-process-workers.md

@@ -17,7 +17,7 @@ Multi process workers feature launches multiple workers and use a separate
 process per worker. In addition, `fluentd` provides several features for multi
 process workers, so you can get multi process merits.
 
-![multi-process-workers.png](/images/multi-process-workers.png)
+![Multi-process Workers](/images/multi-process-workers.png)
 
 
 ## Configuration

guides/apache-to-minio.md

@@ -96,7 +96,7 @@ Wait until the data gets flushed from the buffer (you can adjust the
 flush interval using the `timekey` and `timekey_wait` options above).
 Then you will see the aggregated log data on Minio:
 
-![minio-screenshot.png](/images/minio-screenshot.png)
+![Minio](/images/minio-screenshot.png)
 
 
 ## Learn More

guides/apache-to-mongodb.md

@@ -26,7 +26,7 @@ import Apache logs into MongoDB.
 
 The figure below shows how things will work:
 
-![apache-to-mongodb.png](/images/apache-to-mongodb.png)
+![Apache + MongoDB](/images/apache-to-mongodb.png)
 
 Fluentd does three (3) things:
 

guides/cep-norikra.md

@@ -39,7 +39,7 @@ create a robust stream data processing platform.
 
 The figure below shows the high-level architecture:
 
-![fluentd-norikra-overview.png](/images/fluentd-norikra-overview.png)
+![Fluentd + Norikra Overview](/images/fluentd-norikra-overview.png)
 
 
 ## Installation

guides/free-alternative-to-splunk-by-fluentd.md

@@ -5,7 +5,7 @@ its high cost makes it prohibitive for many teams. In this article, we
 present a free and open source alternative to Splunk by combining three
 open source projects: Elasticsearch, Kibana, and Fluentd.
 
-![kibana6-screenshot-visualize.png](/images/kibana6-screenshot-visualize.png)
+![Kibana Visualization](/images/kibana6-screenshot-visualize.png)
 
 
 [Elasticsearch](https://www.elastic.co/products/elasticsearch) is an
@@ -18,7 +18,7 @@ By combining these three tools (Fluentd + Elasticsearch + Kibana) we get
 a scalable, flexible, easy to use log search engine with a great Web UI
 that provides an open-source Splunk alternative, all for free.
 
-![fluentd-elasticsearch-kibana.png](/images/fluentd-elasticsearch-kibana.png)
+![Fluentd + Elasticsearch + Kibana](/images/fluentd-elasticsearch-kibana.png)
 
 
 In this guide, we will go over installation, setup, and basic use of
@@ -176,7 +176,7 @@ Kibana.
 For starters, let's access `http://localhost:5601` and click the `Set
 up index patters` button in the upper-right corner of the screen.
 
-![kibana6-screenshot-topmenu.png](/images/kibana6-screenshot-topmenu.png)
+![Kibana Top Menu](/images/kibana6-screenshot-topmenu.png)
 
 Kibana will start a wizard that guides you through configuring the data
 sets to visualize. If you want a quick start, use `logstash-*` as the
@@ -185,7 +185,7 @@ index pattern, and select `@timestamp` as the time-filter field.
 After setting up an index pattern, you can view the system logs as they
 flow in:
 
-![kibana6-screenshot.png](/images/kibana6-screenshot.png)
+![Kibana: Discover](/images/kibana6-screenshot.png)
 
 For more detail on how to use Kibana, please read the official
 [manual](https://www.elastic.co/guide/en/kibana/current/index.html).

guides/graylog2.md

@@ -87,7 +87,7 @@ Then, from the dropdown, choose `GELF UDP` and click on `Launch new input`,
 which should pop up a modal dialogue, Select the `Node` and fill the `Title`.
 Then, click `Save`.
 
-![graylog2-input.png](/images/graylog2-input.png)
+![Graylog Inputs](/images/graylog2-input.png)
 
 Now, Graylog2 is ready to accept messages from Fluentd over UDP. It's time to
 configure Fluentd.
@@ -153,7 +153,7 @@ $ sudo systemctl restart td-agent
 When you log back into Graylog, you should be seeing a graph like this
 (wait for events to flow in):
 
-![graylog2-graph.png](/images/graylog2-graph.png)
+![Graylog Graph](/images/graylog2-graph.png)
 
 ------------------------------------------------------------------------
 

guides/http-to-hdfs.md

@@ -25,7 +25,7 @@ receive data from HTTP and stream it into HDFS.
 
 The figure below shows the high-level architecture:
 
-![http-to-hdfs.png](/images/http-to-hdfs.png)
+![HTTP-to-HDFS Overview](/images/http-to-hdfs.png)
 
 
 ## Install

guides/http-to-td.md

@@ -26,7 +26,7 @@ receive data from HTTP and stream it into TD.
 
 The figure below shows the high-level architecture:
 
-![treasuredata_architecture.png](/images/treasuredata_architecture.png)
+![TreasureData Architecture](/images/treasuredata_architecture.png)
 
 
 ## Install

guides/kinesis-stream.md

@@ -6,7 +6,7 @@ This article explains how to use [Fluentd](http://fluentd.org/)'s
 to aggregate semi-structured logs in real-time. Kinesis plugin is
 developed and published by Amazon Web Services officially.
 
-![fluentd-kinesis.png](/images/fluentd-kinesis.png)
+![Fluentd + Kinesis](/images/fluentd-kinesis.png)
 
 
 ## Background

guides/logs-to-sematext.md

@@ -5,7 +5,7 @@ an alternative to Splunk, but with cheaper and more flexible [pricing](https://s
 In this article, we present an alternative to Splunk by combining Fluentd with
 the Sematext open Elasticsearch API.
 
-![sematext-dashboard.png](/images/sematext-dashboard.png)
+![Sematext Dashboard](/images/sematext-dashboard.png)
 
 
 [Elasticsearch](https://www.elastic.co/products/elasticsearch) is an open source
@@ -131,7 +131,7 @@ or with Kibana.
 First of all, open up the Seamtext UI and access your App. You'll see prebuilt
 dashboards with full-text search, filters, and alerts out-of-the-box.
 
-![sematext-configure-logs.png](/images/sematext-configure-logs.png)
+![Sematext: Configure Logs](/images/sematext-configure-logs.png)
 
 Sematext will automatically figure out hosts, idents, pids, timestamps,
 and the origin of the logs. In this case the origin is Fluentd.
@@ -142,7 +142,7 @@ and alerts to fine-tune your own personal use-case.
 If you are used to Kibana, you can still use it as well.
 For more details, read [Kibana's official manual](https://www.elastic.co/guide/en/kibana/current/index.html).
 
-![sematext-logs-overview.png](/images/sematext-logs-overview.png)
+![Sematext: Logs Overview](/images/sematext-logs-overview.png)
 
 
 ### Debugging

guides/raspberrypi-cloud-data-logger.md

@@ -6,7 +6,7 @@ single-board computer. Because it is low-cost and easy to equip with
 various types of sensors, using Raspberry Pi as a cloud data logger is
 one of its ideal use cases.
 
-![raspberry-pi-cloud-data-logger.png](/images/raspberry-pi-cloud-data-logger.png)
+![Cloud Data Logger by Raspberry Pi](/images/raspberry-pi-cloud-data-logger.png)
 
 This article introduces how to transport sensor data from Raspberry Pi
 to the cloud, using Fluentd as the data collector. For the cloud side,

guides/syslog-influxdb.md

@@ -3,7 +3,7 @@
 This article shows how to collect `syslog` data into
 [InfluxDB](http://github.com/influxdb/influxdb) using Fluentd.
 
-![syslog-fluentd-influxdb.png](/images/syslog-fluentd-influxdb.png)
+![Syslog + Fluentd + InfluxDB](/images/syslog-fluentd-influxdb.png)
 
 
 ## Prerequisites
@@ -151,7 +151,7 @@ write SQL queries against your log data**.
 
 And then click `Visualization` and select line chart:
 
-![chronograf-explore-data.png](/images/chronograf-explore-data.png)
+![Chronograf: Explore Data](/images/chronograf-explore-data.png)
 
 Here, I am counting the number of lines of syslog messages per facility/priority:
 
@@ -161,11 +161,11 @@ SELECT COUNT(ident) FROM test.autogen./^system\./ GROUP BY time(1s)
 
 Click on "Submit Query" and you get a graph like this:
 
-![chronograf-query.png](/images/chronograf-query.png)
+![Chronograf: Query](/images/chronograf-query.png)
 
 Here is another screenshot just for the `system.daemon.info` series:
 
-![chronograf-query-2.png](/images/chronograf-query-2.png)
+![Chronograf: Query](/images/chronograf-query-2.png)
 
 
 ------------------------------------------------------------------------

install/install-by-msi.md

@@ -50,7 +50,7 @@ Open this Command Prompt from the Windows Start menu.
 
 Its icon looks like this on Windows Server 2012:
 
-![msi-td-agent-command-prompt.png](/images/msi-td-agent-command-prompt.png)
+![Td-agent Command Prompt](/images/msi-td-agent-command-prompt.png)
 
 Now, launch `td-agent` with the following command:
 
@@ -71,7 +71,7 @@ It is working properly if you see the following in the logs:
 test.event: {"k", "v"}
 ```
 
-[![td-agent-windows-prompt.png](/images/td-agent-windows-prompt.png)](/images/td-agent-windows-prompt.png)
+[![Td-agent Windows Prompt](/images/td-agent-windows-prompt.png)](/images/td-agent-windows-prompt.png)
 
 
 ### Step 3: Run `td-agent` as Windows service
@@ -148,7 +148,7 @@ After you have installed the .msi package, you will see the program called
 `Td-agent Command Prompt` installed. Please double click this icon in
 the Windows menu (below is how it looks like on Windows Server 2012).
 
-![msi-td-agent-command-prompt.png](/images/msi-td-agent-command-prompt.png)
+![Td-agent Command Prompt](/images/msi-td-agent-command-prompt.png)
 
 In the prompt, please execute the command below to launch `td-agent` process:
 
@@ -169,7 +169,7 @@ It's working properly if td-agent process outputs:
 test.event: {"k", "v"}
 ```
 
-[![td-agent-windows-prompt.png](/images/td-agent-windows-prompt.png)](/images/td-agent-windows-prompt.png)
+[![Td-agent Windows Prompt](/images/td-agent-windows-prompt.png)](/images/td-agent-windows-prompt.png)
 
 
 ### Step 3: Register `td-agent` to Windows Service

overview/logo.md

@@ -5,23 +5,23 @@ Feel free to use these logos on your slides, blog posts, etc.
 
 ## Square
 
-[![Fluentd_square.png](/images/logo/Fluentd_square.png)](/images/logo/Fluentd_square.png)
+[![Fluentd Square Logo](/images/logo/Fluentd_square.png)](/images/logo/Fluentd_square.png)
 
 [\[PNG\]](/images/logo/Fluentd_square.png)
 [\[SVG\]](/images/logo/Fluentd_square.svg)
 
 
 ## Horizontal
 
-[![Fluentd_horizontal.png](/images/logo/Fluentd_horizontal.png)](/images/logo/Fluentd_horizontal.png)
+[![Fluentd Horizontal Logo](/images/logo/Fluentd_horizontal.png)](/images/logo/Fluentd_horizontal.png)
 
 [\[PNG\]](/images/logo/Fluentd_horizontal.png)
 [\[SVG\]](/images/logo/Fluentd_horizontal.svg)
 
 
 ## Icon
 
-[![Fluentd_icon.png](/images/logo/Fluentd_icon.png)](/images/logo/Fluentd_icon.png)
+[![Fluentd Icon](/images/logo/Fluentd_icon.png)](/images/logo/Fluentd_icon.png)
 
 [\[PNG\]](/images/logo/Fluentd_icon.png)
 [\[SVG\]](/images/logo/Fluentd_icon.svg)

overview/quickstart.md

@@ -4,7 +4,7 @@ Let's get started with **Fluentd**! **Fluentd** is a fully free and
 fully open-source log collector that instantly enables you to have a
 '**Log Everything**' architecture with [125+ types of systems](https://www.fluentd.org/plugins).
 
-![fluentd-architecture.png](/images/fluentd-architecture.png)
+![Fluentd Architecture](/images/fluentd-architecture.png)
 
 Fluentd treats logs as JSON, a popular machine-readable format. It is
 written primarily in C with a thin-Ruby wrapper that gives users

plugins/buffer/README.md

@@ -45,7 +45,7 @@ where chunks wait before the transportation. Every newly-created chunk
 starts from *stage*, then proceeds to *queue* in time (and subsequently
 gets transferred to the destination).
 
-[![fluentd-v0.14-plugin-api-overview.png](/images/fluentd-v0.14-plugin-api-overview.png)](/images/fluentd-v0.14-plugin-api-overview.png)
+[![Fluentd-v0.14 Plugin API Overview](/images/fluentd-v0.14-plugin-api-overview.png)](/images/fluentd-v0.14-plugin-api-overview.png)
 
 
 ## Control Retry Behavior

plugins/input/dummy.md

@@ -1,6 +1,6 @@
 # `dummy` Input Plugin
 
-![dummy.png](/images/plugins/input/dummy.png)
+![](/images/plugins/input/dummy.png)
 
 The `in_dummy` input plugin generates dummy events. It is useful for
 testing, debugging, benchmarking and getting started with Fluentd.

plugins/input/exec.md

@@ -1,6 +1,6 @@
 # `exec` Input Plugin
 
-![exec.png](/images/plugins/input/exec.png)
+![](/images/plugins/input/exec.png)
 
 The `in_exec` Input plugin executes external programs to receive or pull
 event logs. It will then read TSV (tab separated values), JSON or