aboutsummaryrefslogtreecommitdiffstats
path: root/feature-controller-logging/src/main/feature/install/enable
AgeCommit message (Collapse)AuthorFilesLines
2022-03-08remove init, mdc, and controller logging featuresjhh1-29/+0
Issue-ID: POLICY-3922 Signed-off-by: jhh <jorge.hernandez-herrero@att.com> Change-Id: I8267ea17c3340e47f85b54c641ddb14672776f70
2021-04-07Use sh instead of ash in drools-pdpJim Hahn1-2/+2
Issue-ID: POLICY-3160 Change-Id: I37b2b75d010781108e40ae39d3742bc2c2e2fd7e Signed-off-by: Jim Hahn <jrh3@att.com>
2020-11-30move all bash to ash shell scriptsTaka Cho1-5/+5
this gerrit would be the first step to not to use any GPL-3.0 and plus license Issue-ID: POLICY-2847 Change-Id: I09a571f14ef8c6983f9051068c2bad5acc173787 Signed-off-by: Taka Cho <takamune.cho@att.com>
2019-03-01Add Controller Logging FeatureDaniel Cruz1-0/+29
This features provides a mechanism to extend the logback.xml properties to add controller specific loggers. The controller's logger will log messages from topics that the controller listens to in a controller specific network log. The original network log is preserved and still logs every message from every controller. Note that the way a logger is associated with a controller is by having the logger name match the controller's name. Any configuration file that has "logback-include-" prepended and a ".xml" extension will be added to the logback.xml and logback-eelf.xml files as extensions to the base configuration. Issue-ID: POLICY-1427 Change-Id: Iaeb823421eadb7ee413b6b03ae3dfe862f230612 Signed-off-by: Daniel Cruz <dc443y@att.com>