- Sep 29, 2020
-
-
Mussab Abdalla authored
-
Fabian Schindler authored
- proper escaping - wrong XML tag
-
Mussab Abdalla authored
-
- Sep 28, 2020
-
-
Fabian Schindler authored
-
- Sep 24, 2020
-
-
Fabian Schindler authored
-
Fabian Schindler authored
-
- Sep 16, 2020
-
-
Fabian Schindler authored
-
- Sep 14, 2020
-
-
Lubomir Dolezal authored
-
Fabian Schindler authored
-
Fabian Schindler authored
-
Lubomir Dolezal authored
-
- Sep 09, 2020
-
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
The current production docker verison or configuration only allows to forward a port either by using udp or tcp, not both (even though that's what is suggested by fluentd). docker will use the last entry and silently delete the former. This is not a problem for us since we only talk to fluentd via tcp.
-
Bernhard Mallinger authored
(for consistency, it's not strictly necessary)
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
This would only be a problem if fluentd wasn't running, but since fluentd doesn't log to fluentd, kibana wouldn't help anyway.
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
- Sep 08, 2020
-
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
It didn't include pdas before
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
Resolve "Integrate ELK stack with Fluentd" Closes #9 See merge request !17
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
-
Bernhard Mallinger authored
It's still very similar to dev, common configs could be extracted
-
Bernhard Mallinger authored
-