forked from pivotal-cf/docs-jmx-bridge
-
Notifications
You must be signed in to change notification settings - Fork 0
/
rn-ki.html.md.erb
56 lines (43 loc) · 3.26 KB
/
rn-ki.html.md.erb
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
---
title: JMX Bridge Release Notes and Known Issues
owner: Metrix
---
<p class="note"><strong>Note</strong>: Before version 1.7.X, JMX Bridge was known as Ops Metrics. For Ops Metrics release notes and known issues, see <a href="#1-6">Version 1.6.16</a>. </p>
##<a id='v1.8.4'></a>Version 1.8.4
**Release Date: September 22, 2016**
### Release Notes
* JMX Bridge 1.8.4 - now with stemcell 3263
### Known issues
* There is nothing that prevents the user from turning on the Nozzle deployment when Elastic Runtime is not present.
* Enabling the nozzle when Elastic Runtime is not deployed or enabled will produce the following error:
* "RuntimeError - unknown product 'cf' in (( ..cf.cloud\_controller.system_domain.value ))"
* To fix this, reduce the number of nozzle counts to zero until Elastic Runtime is enabled.
* Because deploying the OpenTSDB firehose nozzle is optional and disabled by default, smoke tests for Elastic Runtime have been disabled until a later release.
##<a id='v1.8.3'></a>Version 1.8.3
**Release Date: September 20, 2016**
### Major Features
* Access to the JMX endpoint is now logged to STDOUT by default. This security logging can be enabled/disabled in the JMX Bridge tile configuration by checking/unchecking "Enable Security Logging" under JMX Provider.
* Related log output is made available by initiating a JMX Provider logs download from the JMX Bridge tile configuration status tab, then fetching the download from the logs tab.
### Release Notes
* JMX Bridge 1.8.3 - BUG FIX: Corrects issue in 1.8.2 where the new security logging feature was not available to the operator in the tile config.
* Stemcell for 1.8.3 remains 3262
### Known issues
* There is nothing that prevents the user from turning on the Nozzle deployment when Elastic Runtime is not present.
* Enabling the nozzle when Elastic Runtime is not deployed or enabled will produce the following error:
* "RuntimeError - unknown product 'cf' in (( ..cf.cloud\_controller.system_domain.value ))"
* To fix this, reduce the number of nozzle counts to zero until Elastic Runtime is enabled.
* Because deploying the OpenTSDB firehose nozzle is optional and disabled by default, smoke tests for Elastic Runtime have been disabled until a later release.
##<a id='v1.8.2'></a>Version 1.8.2
**Release Date: September 16, 2016**
### Release Notes
* JMX Bridge 1.8.2 is targeted for PCF 1.8.X
* Stemcell for 1.8.2 is 3262
### Known issues
* BUG IDENTIFIED: The new security logging feature expected in JMX Bridge 1.8.X was not available to the operator in the tile config in version 1.8.2. JMX Bridge 1.8.3 corrects this.
* There is nothing that prevents the user from turning on the Nozzle deployment when Elastic Runtime is not present.
* Enabling the nozzle when Elastic Runtime is not deployed or enabled will produce the following error:
* "RuntimeError - unknown product 'cf' in (( ..cf.cloud\_controller.system_domain.value ))"
* To fix this, reduce the number of nozzle counts to zero until Elastic Runtime is enabled.
* Because deploying the OpenTSDB firehose nozzle is optional and disabled by default, smoke tests for Elastic Runtime have been disabled until a later release.
##Past Minor Version 1.7.X
Release Notes for 1.7.X releases can be found [here](http://docs.pivotal.io/jmx-bridge/1-7/rn-ki.html).