Skip to content
This repository was archived by the owner on Nov 22, 2024. It is now read-only.

Document logback-config option #955

Merged
andreaTP merged 1 commit into from
Jan 19, 2021
Merged

Document logback-config option #955

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions docs/shared-content-source/docs/modules/develop/pages/cloudflow-configuration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -559,6 +559,40 @@ $ {cli-plugin} cloudflow deploy target/swiss-knife.json \

The arguments passed with `[config-key]=[value]` pairs take precedence over the files passed through with the `--conf` flags.

=== Configuring a Streamlet logging configuration

The streamlet logging configuration can be tweaked for all of the pods with a simple command.

You need first to craft a proper `logback.xml` logging configuration file e.g.:
[source, xml]
----
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<statusListener class="ch.qos.logback.core.status.NopStatusListener" />

<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%msg\n</pattern>
</encoder>
</appender>

<root level="DEBUG">
<appender-ref ref="STDOUT"/>
</root>
</configuration>
----

And you can pass it to the relevant option in the `deploy` and `configure` sub-commands:
[source, bash]
----
$ {cli-plugin} cloudflow deploy cr.json --logback-config logback.xml
----

[source, bash]
----
$ {cli-plugin} cloudflow configure app-name --logback-config logback.xml
----

== What's Next

Now that we have mastered the configuration options in Cloudflow, we should learn about xref:develop:blueprints.adoc[] and how they help us to assemble streamlets into end-to-end applications.