forked from Azure/azure-linux-extensions
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathChangeLogs
113 lines (92 loc) · 4.72 KB
/
ChangeLogs
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
2019-01-15: LAD-3.0.119
- Add blobEndpoint for storage accounts; bug fix for National clouds.
2017-09-05: LAD-3.0.111
- Ensure SAS storage token is supplied
- Explicitly reject deprecated use of LAD 2.3's storageAccountKey
2017-08-11: LAD-3.0.109
- Fix waagent-related issue on Debian distros
- Add additional unit tests
- Replace multiple uses of "local" with "locale"
- Improve error reporting when catching an exception
- Fix #398, #399, #340
2017-05-16: LAD-3.0.107
- Move resourceId field generation for JSON events from LAD to mdsd
2017-05-10: LAD-3.0.103
- Allow '*' in syslog spec, add more fields in syslog records for
EventHubs
2017-05-08: LAD-3.0.101
- New release of LAD 3.0. Refer to README.md
2017-01-13: LAD-2.3.9021
- Fix rsyslogd core dump issue when re-enabling the extension
- Take latest mdsd binary that fixes other issues like missing perf
counter logs when there's a race condition between mdsd and omiserver.
2016-11-30: LAD-2.3.9017
- Fix scx upgrade issue on RPM-based distros when apache or mysql is
installed.
2016-11-11: LAD-2.3.9015
- Correctly fail Enable when mdsd dependency set up fails.
- Added /etc/fstab watcher feature (logging to /dev/console so that issues
can be found on serial logs)
- Add storage account SAS token support (replacing storage account key)
- Encrypt storage secret in xmlCfg.xml
2016-10-31: LAD-2.3.9013
- Use semodule -u (upgrade) to reduce unnecessary SELinux policy
re-install time
- Use the latest scx package version (1.6.2-337)
- Issue #265: Don't remove port 1270 from omiserver.conf if omsagent is
installed.
2016-10-07: LAD-2.3.9011
- Update OpenSSL library to the latest
- Update rsyslog output modules for all versions of rsyslog (5/7/8) to use
Unix domain socket.
- Update mdsd binary to the latest (1.2.104) with various fixes
- Dependencies are now installed at Enable time, to reduce VM deployment
time.
2016-09-16: LAD-2.3.9009
- Underlying monitoring agent binary (mdsd) upgrade with many fixes and
improvements
- Fixes storage end point bug (affected Mooncake and Blackforest)
2016-07-14: LAD-2.3.9007
- Fixes install issues on some RH-based distros (e.g., OracleLinux 7) due
to lack of tar.
- Fixes duplicate logging (on /var/log/syslog) issue on fileCfg
2016-06-30: LAD-2.3.9005
- Fixes non-starting monitoring agent issue on systemd-enabled distros (#180)
- HandlerUtil unified with other extensions
- Telemetry (logging) improvement
- Remove possibility of logging some password
2016-06-21: LAD-2.3.9003
- Monitoring agent (mdsd) updates for a memory issue fix, a signal handler fix,
and a fix to avoid a spin loop under certain circumstances
- doesn't count non-quick crashes (>30 mins) towards retry limit
- OMI reconfiguration not to listen to port 1270
- Use systemd on Ubuntu 16.04 as well
- Validate mdsd XML config before starting mdsd, fails fast on invalid
config (with success)
- Small Python 2.6 bug fix (syslog.openlog())
2016-06-06: LAD-2.3.9001
- Fix issue of syslog messages not collected by default on SLES 11
- Minor config syntactic fixes
- Logging fix to show correct extension version
- Monitoring agent kill is no longer SIGKILL, but SIGTERM.
- Monitoring agent listening port is now dynamic if the specified port (29131) is in use.
- Monitoring agent core dump is enabled (dumped on its current working directory)
- Newer monitoring agent bits with added features (not available on LAD yet)
2016-05-04: LAD-2.3.9
- mdsd bits are now built as statically as possible, so that a single monolithic executable
can be used on as many distros/versions.
- OMI install result is checked and tried up to 3 times. If all fail, LAD install fails as well.
- OMI is checked periodically for its health and LAD will restart it if OMI is not up.
2016-03-26: LAD-2.3.7
- mdsd http proxy config through waagent.conf
- OpenSUSE 13 support revival
- LAD no longer (re)starts apache/mysql invasively (restarts only when they were running)
- Bundle libglibmm*.so (no longer downloaded/installed when LAD is installed)
- AppInsights configuration changes
2016-03-08: LAD-2.3.6
- mdsd http proxy support (mdsd binary change)
- Ubuntu 16.04 glibmm install issue fix
- Report success extension event for unsupported distros/versions
2016-02-25: LAD-2.3.5. Reviving SUSE 11 support and consolidating binaries of diff versions of same distro
2016-02-25: LAD-2.3.4. Hotfix for portal perf graphs not showing (xmlCfg parsing bug)
2016-02-15: LAD-2.3.3. No changes on mdsd/LAD code. Just rebuilding to take in the most recent AISDK fixes