1. Create canonical path /etc/onap/logstash/conf.d/ on the host on which the logstash has to be installed.
2. Save the logstash.yml at location created in step 1.
3. Create canonical path /etc/onap/logstash/conf.d/pipeline/ on the host.
-4. The onap-pipeline.conf is parameterized and has tokens instead of values for certain deployment specific parameteres (like port, elastic host etc.). These tokens has a syntax as '$[a-zA-Z_]+'.
+4. The onap-pipeline.conf is parameterized and has tokens instead of values for certain deployment specific parameters (like port, elastic host etc.). These tokens has a syntax as '$[a-zA-Z_]+'.
5. These tokens are listed in another file onap-pipeline.properties. These properties are also provided with commented description about them in the file itself. These tokens have to be replaced with the appropriate values as per the deployment environment before deployment.
6. Now, save the final onap-pipeline.conf at location created in step 3.
7. Following is the list of specifications for logstash container creation-
2. Host path - /etc/onap/logstash/conf.d/pipeline/ mapped to
Container path - /usr/share/logstash/pipeline/
-8. onap-pipeline.properties need not be deployed after the values from it are used.
\ No newline at end of file
+8. onap-pipeline.properties need not be deployed after the values from it are used.
It doesn't:
1. Provide appender-specific logger-to-level mappings. Each logger gets the same level for each appender.
-2. Define globals, or nececssarily fit into the nascent scheme for OOM helm chart parameterization.
+2. Define globals, or necessarily fit into the nascent scheme for OOM helm chart parameterization.