-
Epic
-
Resolution: Done
-
Medium
-
None
Post linked jiras here for logging work done in OOM as a reference for developers
- blocks
-
OOM-885 Beijing oom component log messages missing in Elasticsearch
- Closed
- is blocked by
-
LOG-334 onap-log elasticsearch container memory config too low to start - fix: sysctl -w vm.max_map_count=262144 under Rancher 1.6.11+
- Closed
-
OOM-420 kibana and logstash not connecting to es
- Closed
-
OOM-427 log containers fail to create since 20171213 - using tpl template function on helm 2.3 not 2.6
- Closed
-
OOM-462 Adjust mso artifacts to latest (Amsterdam)
- Closed
-
OOM-428 Add log container healthcheck to mark failed creations - see OOM-427
- Closed
-
OOM-520 Wrong date format configuration in A&AI sparky-be logback.xml
- Closed
-
OOM-527 Wrong date format configuration in vid-server logback.xml
- Closed
-
POLICY-533 Platform Maturity Manageability L1 - Logging
- Closed
-
AAI-493 Logging bugfixes
- Closed
-
LOG-292 Rework ROBOT healthcheck reporting logs for ELK friendly CD frameworks
- Closed
-
MULTICLOUD-151 Logging Enablement
- Closed
-
OOM-109 Platform Centralized Logging
- Closed
-
OOM-324 AAF Service Container logging error
- Closed
-
OOM-390 Wrong configuration of log/elasticsearch
- Closed
-
OOM-403 Logs are not properly initialized in SDC-FE pod
- Closed
-
OOM-407 Logs - Update filebeat configuration
- Closed
-
OOM-426 Fix aai/data-router entity-event.route double quote from AAI-461
- Closed
-
OOM-596 Segregation of configuration for Log component
- Closed
- relates to
-
VFC-819 add filebeat to hwvnfmdriver and jujudriver
- Closed