From 35f6f60390ac1fc4237f5f95440171921f5b5692 Mon Sep 17 00:00:00 2001 From: Michael Friedrich Date: Fri, 28 Apr 2017 17:02:13 +0200 Subject: [PATCH] Docs: Fix invalid/redirected URLs fixes #5150 --- doc/14-features.md | 12 ++++++------ lib/compat/statusdatawriter.cpp | 2 +- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/14-features.md b/doc/14-features.md index 353f20475..51584b44e 100644 --- a/doc/14-features.md +++ b/doc/14-features.md @@ -5,7 +5,7 @@ Icinga 2 supports three different types of logging: * File logging -* Syslog (on *NIX-based operating systems) +* Syslog (on Linux/UNIX) * Console logging (`STDOUT` on tty) You can enable additional loggers using the `icinga2 feature enable` @@ -340,13 +340,13 @@ More configuration details can be found [here](9-object-types.md#objecttype-infl #### GELF Writer -The `Graylog Extended Log Format` (short: [GELF](http://www.graylog2.org/resources/gelf)) +The `Graylog Extended Log Format` (short: [GELF](http://docs.graylog.org/en/latest/pages/gelf.html)) can be used to send application logs directly to a TCP socket. -While it has been specified by the [graylog2](http://www.graylog2.org/) project as their -[input resource standard](http://www.graylog2.org/resources/gelf), other tools such as -[Logstash](http://www.logstash.net) also support `GELF` as -[input type](http://logstash.net/docs/latest/inputs/gelf). +While it has been specified by the [Graylog](https://www.graylog.org) project as their +[input resource standard](http://docs.graylog.org/en/latest/pages/sending_data.html), other tools such as +[Logstash](https://www.elastic.co/products/logstash) also support `GELF` as +[input type](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-gelf.html). You can enable the feature using diff --git a/lib/compat/statusdatawriter.cpp b/lib/compat/statusdatawriter.cpp index a9b506912..080be1892 100644 --- a/lib/compat/statusdatawriter.cpp +++ b/lib/compat/statusdatawriter.cpp @@ -63,7 +63,7 @@ void StatusDataWriter::StatsFunc(const Dictionary::Ptr& status, const Array::Ptr /** * Hint: The reason why we're using "\n" rather than std::endl is because * std::endl also _flushes_ the output stream which severely degrades - * performance (see http://gcc.gnu.org/onlinedocs/libstdc++/manual/bk01pt11ch25s02.html). + * performance (see https://stackoverflow.com/questions/213907/c-stdendl-vs-n). */ /**