blob: e64d8ca2febcd1b55138df6db279af1c111b6cdb (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
Log Enhancements Release Notes
==============================
Version: 1.2.2 Casablanca
--------------
:Release Date: 2018-11-15
**New Features**
- Demo slf4j library with marker/mdc support along with kubernetes, docker, war support projects.
**Bug Fixes**
**Known Issues**
- `Logstash load balancing is asymmetric wherever AAI is run - https://jira.onap.org/browse/LOG-376`_
**Security Notes**
None
LOG code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The LOG open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=28378692>`_.
Quick Links:
- `LOG project page <https://wiki.onap.org/display/DW/Logging+Enhancements+Project>`_
- `Passing Badge information for LOG <https://bestpractices.coreinfrastructure.org/en/projects/1578>`_
- `Project Vulnerability Review Table for LOG <https://wiki.onap.org/pages/viewpage.action?pageId=43385152>`_
**Upgrade Notes**
None
**Deprecation Notes**
None
**Other**
None
Version: Beijing
--------------
:Release Date: 2018-06-07
**New Features**
- Logstash is a daemonset (clustered at 1 container per VM)
- `The following applications send logs to the ELK stack - <https://jira.onap.org/browse/LOG-230>`_
**Bug Fixes**
**Known Issues**
- Logstash load balancing is asymmetric
**Security Notes**
- all three nodeports for logstash, elasticsearch and kibana are open by default for now
LOG code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The LOG open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=28378692>`_.
Quick Links:
- `LOG project page <https://wiki.onap.org/display/DW/Logging+Enhancements+Project>`_
- `Passing Badge information for LOG <https://bestpractices.coreinfrastructure.org/en/projects/1578>`_
- `Project Vulnerability Review Table for LOG <https://wiki.onap.org/pages/viewpage.action?pageId=28378692>`_
**Upgrade Notes**
None
**Deprecation Notes**
None
**Other**
Note: there was no released artifacts under 1.2.2 for Beijing - release was pushed to Casablanca
Version: 1.0.0
--------------
:Release Date: 2017-11-16
**New Features**
This release adds Elastic Stack analytics deployment to OOM, aligns logging provider configurations, and fixes issues with the propagation of transaction IDs and other contextual information.
- `LOG-1 <https://jira.onap.org/browse/LOG-1>`_ Transaction ID propagation.
- `LOG-2 <https://jira.onap.org/browse/LOG-2>`_ Standardized logging provider configuration.
- `LOG-3 <https://jira.onap.org/browse/LOG-3>`_ Elastic Stack reference analytics pipeline.
- `LOG-4 <https://jira.onap.org/browse/LOG-4>`_ Transaction ID conventions.
**Bug Fixes**
- `LOG-64 <https://jira.onap.org/browse/LOG-64>`_ Logger field has a length restriction of 36 which needs a fix.
- `LOG-74 <https://jira.onap.org/browse/LOG-74>`_ Extract componentName from the source path of log files.
**Known Issues**
- `LOG-43 <https://jira.onap.org/browse/LOG-43>`_
Unable to find logback xml for DMaaP component.
Logging file for DMaaP is available in this jar "eelf-core-0.0.1.jar".
- `LOG-65 <https://jira.onap.org/browse/LOG-65>`_
SO Logging Provider Config File need correction in Timestamp MDC.
Logging provider configuration file for SO i.e. logback files requires correction in Timestamp MDC for correct MDC generation in log.
The current pattern prints Timestamp as 2017-09-25 05:30:07,832. Expected pattern is - 2017-09-25T05:30:07.832Z.
- `LOG-80 <https://jira.onap.org/browse/LOG-80>`_ Kibana does not seem to show all the logs from application pods.
The content of the log directories (/var/log/onap/mso) are not 100% reflected in Kibana.
- `LOG-88 <https://jira.onap.org/browse/LOG-88>`_
SO log format error during Health Check - blocking tracking jira for SO-246.
**Security Issues**
None
**Upgrade Notes**
None
**Deprecation Notes**
None
**Other**
None
===========
End of Release Notes
|
