[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Attachment: AMBARI-19618_3.patch
> Make cohosted components configurable in metainfo.xml instead of hardcoding
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png,
> after_patched_ranger1.png, after_patched_ranger2.png,
> after_patched_ranger3.png, AMBARI-19618_1.patch, AMBARI-19618_2.patch,
> AMBARI-19618_3.patch
>
>
> Cohosted components information now is hardcoded in
> stack_service_component.js as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Description:
Cohosted components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml by adding tag
in stack like following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
//https://issues.apache.org/jira/browse/AMBARI-19557
//http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.3/bk_security/content/ch03s01s03s01.html
RANGER_USERSYNC
Ranger Usersync
MASTER
1
true
RANGER_ADMIN
was:
Cohosted components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml by adding tag
in stack like following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
RANGER_USERSYNC
Ranger Usersync
MASTER
1
true
RANGER_ADMIN
> Make cohosted components configurable in metainfo.xml instead of hardcoding
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png,
> after_patched_ranger1.png, after_patched_ranger2.png,
> after_patched_ranger3.png, AMBARI-19618_1.patch, AMBARI-19618_2.patch,
> AMBARI-19618_3.patch
>
>
> Cohosted components information now is hardcoded in
> stack_service_component.js as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
> //https://issues.apache.org/jira/browse/AMBARI-19557
> //http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.3/bk_security/content/ch03s01s03s01.html
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Resolution: Duplicate
Status: Resolved (was: Patch Available)
> Make cohosted components configurable in metainfo.xml instead of hardcoding
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png,
> after_patched_ranger1.png, after_patched_ranger2.png,
> after_patched_ranger3.png, AMBARI-19618_1.patch, AMBARI-19618_2.patch,
> AMBARI-19618_3.patch
>
>
> Cohosted components information now is hardcoded in
> stack_service_component.js as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
> //https://issues.apache.org/jira/browse/AMBARI-19557
> //http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.3/bk_security/content/ch03s01s03s01.html
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Attachment: AMBARI-19618_2.patch
> Make cohosted components configurable in metainfo.xml instead of hardcoding
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png,
> after_patched_ranger1.png, after_patched_ranger2.png,
> after_patched_ranger3.png, AMBARI-19618_1.patch, AMBARI-19618_2.patch,
> AMBARI-19618.patch
>
>
> Cohosted components information now is hardcoded in
> stack_service_component.js as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Attachment: (was: AMBARI-19618.patch)
> Make cohosted components configurable in metainfo.xml instead of hardcoding
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png,
> after_patched_ranger1.png, after_patched_ranger2.png,
> after_patched_ranger3.png, AMBARI-19618_1.patch, AMBARI-19618_2.patch
>
>
> Cohosted components information now is hardcoded in
> stack_service_component.js as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Description:
Cohost components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml by tag
in stack like following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
was:
Cohost components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml in stack like
following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
> Make cohost components configurable in metainfo.xml instead of hardcoding in
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Reporter: Yao Lei
> Fix For: trunk, 2.5.0
>
>
> Cohost components information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Description:
Cohost components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml by adding tag
in stack like following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
was:
Cohost components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml by tag
in stack like following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
> Make cohost components configurable in metainfo.xml instead of hardcoding in
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Reporter: Yao Lei
> Fix For: trunk, 2.5.0
>
>
> Cohost components information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Description:
Cohost components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml in stack like
following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
was:
Cohost components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml in stack
> Make cohost components configurable in metainfo.xml instead of hardcoding in
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Reporter: Yao Lei
> Fix For: trunk, 2.5.0
>
>
> Cohost components information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml in stack like
> following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Description:
Cohost components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml by adding tag
in stack like following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
RANGER_USERSYNC
Ranger Usersync
MASTER
1
true
RANGER_ADMIN
was:
Cohost components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml by adding tag
in stack like following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
> Make cohost components configurable in metainfo.xml instead of hardcoding in
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Reporter: Yao Lei
> Fix For: trunk, 2.5.0
>
>
> Cohost components information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19618) Make cohost component configurable in metainfo.xml instead of hardcoding in javascript
Yao Lei created AMBARI-19618: Summary: Make cohost component configurable in metainfo.xml instead of hardcoding in javascript Key: AMBARI-19618 URL: https://issues.apache.org/jira/browse/AMBARI-19618 Project: Ambari Issue Type: Improvement Reporter: Yao Lei Fix For: trunk, 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Summary: Make cohost components configurable in metainfo.xml instead of
hardcoding in UI (was: Make cohost component configurable in metainfo.xml
instead of hardcoding in javascript)
> Make cohost components configurable in metainfo.xml instead of hardcoding in
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Reporter: Yao Lei
> Fix For: trunk, 2.5.0
>
>
> Cohost component information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml in stack
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost component configurable in metainfo.xml instead of hardcoding in javascript
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Description:
Cohost component information now is hardcoded in stack_service_component.js as
following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml in stack
was:
Cohost component information now is hardcoded in javascript as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
> Make cohost component configurable in metainfo.xml instead of hardcoding in
> javascript
> --
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Reporter: Yao Lei
> Fix For: trunk, 2.5.0
>
>
> Cohost component information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml in stack
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Description:
Cohost components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml in stack
was:
Cohost component information now is hardcoded in stack_service_component.js as
following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml in stack
> Make cohost components configurable in metainfo.xml instead of hardcoding in
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Reporter: Yao Lei
> Fix For: trunk, 2.5.0
>
>
> Cohost components information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml in stack
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost component configurable in metainfo.xml instead of hardcoding in javascript
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Description:
Cohost component information now is hardcoded in javascript as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
> Make cohost component configurable in metainfo.xml instead of hardcoding in
> javascript
> --
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Reporter: Yao Lei
> Fix For: trunk, 2.5.0
>
>
> Cohost component information now is hardcoded in javascript as following:
>
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Affects Version/s: trunk
> Make cohost components configurable in metainfo.xml instead of hardcoding in
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 2.5.0
>
>
> Cohost components information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Fix Version/s: trunk
> Make cohost components configurable in metainfo.xml instead of hardcoding in
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
>
> Cohost components information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Fix Version/s: (was: 2.5.0)
(was: trunk)
3.0.0
> Make cohost components configurable in metainfo.xml instead of hardcoding in
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: 3.0.0
>
>
> Cohost components information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Summary: Make cohosted components configurable in metainfo.xml instead of
hardcoding in UI (was: Make cohost components configurable in metainfo.xml
instead of hardcoding in UI)
> Make cohosted components configurable in metainfo.xml instead of hardcoding
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png,
> after_patched_ranger1.png, after_patched_ranger2.png,
> after_patched_ranger3.png
>
>
> Cohost components information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Description:
Cohosted components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml by adding tag
in stack like following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
RANGER_USERSYNC
Ranger Usersync
MASTER
1
true
RANGER_ADMIN
was:
Cohost components information now is hardcoded in stack_service_component.js
as following:
App.StackServiceComponent.coHost = {
'WEBHCAT_SERVER': 'HIVE_SERVER'
};
It's better to move them from javascript to metainfom.xml by adding tag
in stack like following:
WEBHCAT_SERVER
WebHCat Server
MASTER
1
true
true
HIVE_SERVER
RANGER_USERSYNC
Ranger Usersync
MASTER
1
true
RANGER_ADMIN
> Make cohosted components configurable in metainfo.xml instead of hardcoding
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png,
> after_patched_ranger1.png, after_patched_ranger2.png,
> after_patched_ranger3.png
>
>
> Cohosted components information now is hardcoded in
> stack_service_component.js as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Status: Patch Available (was: Open)
> Make cohosted components configurable in metainfo.xml instead of hardcoding
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png,
> after_patched_ranger1.png, after_patched_ranger2.png,
> after_patched_ranger3.png, AMBARI-19618.patch
>
>
> Cohosted components information now is hardcoded in
> stack_service_component.js as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohost components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Attachment: after_patched_ranger3.png
after_patched_ranger2.png
after_patched_ranger1.png
after_patched_hive2.png
after_patched_hive1.png
> Make cohost components configurable in metainfo.xml instead of hardcoding in
> UI
> ---
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png,
> after_patched_ranger1.png, after_patched_ranger2.png,
> after_patched_ranger3.png
>
>
> Cohost components information now is hardcoded in stack_service_component.js
> as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19618) Make cohosted components configurable in metainfo.xml instead of hardcoding in UI
[
https://issues.apache.org/jira/browse/AMBARI-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-19618:
-
Attachment: AMBARI-19618_1.patch
> Make cohosted components configurable in metainfo.xml instead of hardcoding
> in UI
> -
>
> Key: AMBARI-19618
> URL: https://issues.apache.org/jira/browse/AMBARI-19618
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
> Fix For: trunk, 3.0.0
>
> Attachments: after_patched_hive1.png, after_patched_hive2.png,
> after_patched_ranger1.png, after_patched_ranger2.png,
> after_patched_ranger3.png, AMBARI-19618_1.patch, AMBARI-19618.patch
>
>
> Cohosted components information now is hardcoded in
> stack_service_component.js as following:
> App.StackServiceComponent.coHost = {
> 'WEBHCAT_SERVER': 'HIVE_SERVER'
> };
> It's better to move them from javascript to metainfom.xml by adding tag
> in stack like following:
>
> WEBHCAT_SERVER
> WebHCat Server
> MASTER
> 1
> true
> true
> HIVE_SERVER
>
>
>RANGER_USERSYNC
>Ranger Usersync
>MASTER
>1
>true
>RANGER_ADMIN
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notifications of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari allow all notifications of all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. However, sometimes we hope to filter notification of some alert states This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL state notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notifications will be dispatched was: By default, Ambari allow all notifications of all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. However, sometimes we hope to filter notification of some alert states This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL state notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notification will be dispatched > Support dispatching notifications of assigned alert states for script-based > alert dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.1.patch, AMBARI-18292.patch > > > By default, Ambari allow all notifications of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notifications will be > dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notifications of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Resolution: Won't Fix Status: Resolved (was: Patch Available) > Support dispatching notifications of assigned alert states for script-based > alert dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.1.patch, AMBARI-18292.patch > > > By default, Ambari allow all notifications of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notifications will be > dispatched > I think making the desired notifications configurable is useful for > Ambari users -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18292) Support dispatching notifications of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15461877#comment-15461877 ] Yao Lei commented on AMBARI-18292: -- See rb. Alert states can be set when creating or editing alert target > Support dispatching notifications of assigned alert states for script-based > alert dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.1.patch, AMBARI-18292.patch > > > By default, Ambari allow all notifications of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notifications will be > dispatched > I think making the desired notifications configurable is useful for > Ambari users -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Open (was: Patch Available) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: (was: AMBARI-18292.patch) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Patch Available (was: Open) > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari allow all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL alert notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notification will be dispatched was: By default, Ambari allow all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL alert notification notification.dispatch.alert.script.states=WARNING,CRITICAL > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support to dispatch assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari allow all kinds of alert states of notification to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by configuring 'notification.dispatch.alert.script.states' in ambari.properties like following: notification.dispatch.alert.script.states=WARN,CRI was: By default, Ambari allow all kinds of alert states of notification to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by configuring 'notification.dispatch.alert.script.states' in ambari.properties > Support to dispatch assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states of notification to > dispatch in script-based alert dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by configuring > 'notification.dispatch.alert.script.states' in ambari.properties like > following: > notification.dispatch.alert.script.states=WARN,CRI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Summary: Support dispatching assigned alert states notification for script-based alert dispatcher (was: Support to dispatch assigned alert states notification for script-based alert dispatcher) > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18292) Support to dispatch assigned alerts states notification for script-based alert dispatcher
Yao Lei created AMBARI-18292: Summary: Support to dispatch assigned alerts states notification for script-based alert dispatcher Key: AMBARI-18292 URL: https://issues.apache.org/jira/browse/AMBARI-18292 Project: Ambari Issue Type: Improvement Affects Versions: trunk Reporter: Yao Lei Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support to dispatch assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari allow all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL alert notification notification.dispatch.alert.script.states=WARNING,CRITICAL was: By default, Ambari allow all kinds of alert states of notification to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by configuring 'notification.dispatch.alert.script.states' in ambari.properties like following: notification.dispatch.alert.script.states=WARN,CRI > Support to dispatch assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Open (was: Patch Available) > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support to dispatch assigned alerts states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Summary: Support to dispatch assigned alerts states notification for script-based alert dispatcher (was: Make notification 's alerts states configurable for script-based alert dispatcher ) > Support to dispatch assigned alerts states notification for script-based > alert dispatcher > - > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Make notification 's alerts states configurable for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Summary: Make notification 's alerts states configurable for script-based alert dispatcher (was: Support to dispatch assigned alerts states notification for script-based alert dispatcher ) > Make notification 's alerts states configurable for script-based alert > dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support to dispatch assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari allow all kinds of alert states of notification to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by configuring 'notification.dispatch.alert.script.states' in ambari.properties was: By default, Ambari allow all kinds of alert states of notification to dispatch in script-based alert dispatcher. However, sometimes we hope to stop some alert states notification This patch will resolve this problem by configuring 'notification.dispatch.alert.script.states' in ambari.properties > Support to dispatch assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states of notification to > dispatch in script-based alert dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by configuring > 'notification.dispatch.alert.script.states' in ambari.properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Priority: Minor (was: Major) > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Priority: Major (was: Minor) > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: (was: AMBARI-18292.patch) > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support to dispatch assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari dispatch all kinds of alert states of notification to > Support to dispatch assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari dispatch all kinds of alert states of notification to -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support to dispatch assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari allow all kinds of alert states of notification to dispatch in script-based alert dispatcher. However, sometimes we hope to stop some alert states notification This patch will resolve this problem by configuring 'notification.dispatch.alert.script.states' in ambari.properties was:By default, Ambari dispatch all kinds of alert states of notification to > Support to dispatch assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states of notification to > dispatch in script-based alert dispatcher. > However, sometimes we hope to stop some alert states notification > This patch will resolve this problem by configuring > 'notification.dispatch.alert.script.states' in ambari.properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Component/s: alerts > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: AMBARI-18292.patch > Support dispatching assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support to dispatch assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Summary: Support to dispatch assigned alert states notification for script-based alert dispatcher (was: Support to dispatch assigned alerts states notification for script-based alert dispatcher) > Support to dispatch assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support to dispatch assigned alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Patch Available (was: Open) > Support to dispatch assigned alert states notification for script-based alert > dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: (was: AMBARI-18292.patch) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: AMBARI-18292.patch > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Patch Available (was: Open) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: AMBARI-18292.patch > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch, AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Summary: Support dispatching notification of assigned alert states for script-based alert dispatcher (was: Support dispatching assigned alert states notification for script-based alert dispatcher) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert > dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari allow all notification of all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. However, sometimes we hope to filter notification of some alert states This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL state notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notification will be dispatched was: By default, Ambari allow notification of all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL alert notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notification will be dispatched > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Patch Available (was: Open) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Status: Open (was: Patch Available) > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Description: By default, Ambari allow notification of all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL alert notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notification will be dispatched was: By default, Ambari allow all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert dispatcher. However, sometimes we hope to filter some alert states notification This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following: #Only dispatch WARNING and CRITICAL alert notification notification.dispatch.alert.script.states=WARNING,CRITICAL If you don't set this property that means all notification will be dispatched > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.patch > > > By default, Ambari allow notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter some alert states notification > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL alert notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notification of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Attachment: AMBARI-18292.1.patch > Support dispatching notification of assigned alert states for script-based > alert dispatcher > --- > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.1.patch, AMBARI-18292.patch > > > By default, Ambari allow all notification of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notification will be dispatched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18292) Support dispatching notifications of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15461877#comment-15461877 ] Yao Lei edited comment on AMBARI-18292 at 9/5/16 1:16 AM: -- See https://reviews.apache.org/r/51599/. Alert states can be set when creating or editing alert target was (Author: yaolei): See rb. Alert states can be set when creating or editing alert target > Support dispatching notifications of assigned alert states for script-based > alert dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18292.1.patch, AMBARI-18292.patch > > > By default, Ambari allow all notifications of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notifications will be > dispatched > I think making the desired notifications configurable is useful for > Ambari users -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Status: Patch Available (was: Open) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Status: Open (was: Patch Available) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: AMBARI-18423.patch > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: (was: AMBARI-18423.patch) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Description: Ambari now only support creating/editing alert notifications of type EMAIL/SNMP. This patch aims to support another was: Ambari only support creating/editing alert notifications of type EMAIL/SNMP. This patch aims to create SCRIPT type > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP. > This patch aims to support another -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT
Yao Lei created AMBARI-18423: Summary: Support creating/editing alert target which notification_type is ALERT_SCRIPT Key: AMBARI-18423 URL: https://issues.apache.org/jira/browse/AMBARI-18423 Project: Ambari Issue Type: Improvement Reporter: Yao Lei Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT on web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Summary: Support creating/editing alert target which notification_type is ALERT_SCRIPT on web client (was: Support creating/editing alert target which notification_type is ALERT_SCRIPT) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT on web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement >Reporter: Yao Lei > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Summary: Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client (was: Support creating/editing alert target which notification_type is ALERT_SCRIPT on web client) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: create_alert_notification.png, > edit_alert_notification.png > > > Ambari only support creating/editing alert notifications of type EMAIL/SNMP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Description: Ambari only support creating/editing alert notifications of type EMAIL/SNMP. This patch aims to create SCRIPT type was:Ambari only support creating/editing alert notifications of type EMAIL/SNMP. > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: create_alert_notification.png, > edit_alert_notification.png > > > Ambari only support creating/editing alert notifications of type EMAIL/SNMP. > This patch aims to create SCRIPT type -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Description: Ambari now only support creating/editing alert notifications of type EMAIL/SNMP in web client. This patch aims to support another notification type:ALERT_SCRIPT was: Ambari now only support creating/editing alert notifications of type EMAIL/SNMP. This patch aims to support another > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT on web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: edit_alert_notification.png create_alert_notification.png > Support creating/editing alert target which notification_type is > ALERT_SCRIPT on web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: create_alert_notification.png, > edit_alert_notification.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT on web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Description: Ambari only support creating/editing alert notifications of type EMAIL/SNMP. > Support creating/editing alert target which notification_type is > ALERT_SCRIPT on web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: create_alert_notification.png, > edit_alert_notification.png > > > Ambari only support creating/editing alert notifications of type EMAIL/SNMP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Status: Patch Available (was: Open) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Status: Open (was: Patch Available) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_2.patch, > create_alert_notification.png, edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-18292) Support dispatching notifications of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Comment: was deleted (was: See https://reviews.apache.org/r/51599/. Alert states can be set when creating or editing alert target ) > Support dispatching notifications of assigned alert states for script-based > alert dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Attachments: AMBARI-18292.1.patch, AMBARI-18292.patch > > > By default, Ambari allow all notifications of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notifications will be > dispatched > I think making the desired notifications configurable is useful for > Ambari users -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: (was: AMBARI-18423.patch) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: (was: AMBARI-18423_2.patch) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14536) Enhance the function of HdfsResource to copy matching wildcard files to hdfs
[ https://issues.apache.org/jira/browse/AMBARI-14536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-14536: - Status: Open (was: Patch Available) > Enhance the function of HdfsResource to copy matching wildcard files to hdfs > > > Key: AMBARI-14536 > URL: https://issues.apache.org/jira/browse/AMBARI-14536 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei >Priority: Minor > Attachments: AMBARI-14536.patch > > > In some cases,we need to copy local matching wildcard files to hdfs. > eg. we'd like to copy /usr/lib/spark*.jar to hdfs by following codes in > Python: > params.HdfsResource(hdfs_dir_path, > type="file", > action="create_on_execute", > source="/usr/lib/spark*.jar", > group=params.user_group, > owner=params.pdm_user, > mode=0755 > ) > params.HdfsResource(None, action="execute") -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Component/s: ambari-web alerts > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: AMBARI-18423.patch > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Affects Version/s: trunk Status: Patch Available (was: Open) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18292) Support dispatching notifications of assigned alert states for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18292: - Fix Version/s: (was: 2.5.0) > Support dispatching notifications of assigned alert states for script-based > alert dispatcher > > > Key: AMBARI-18292 > URL: https://issues.apache.org/jira/browse/AMBARI-18292 > Project: Ambari > Issue Type: Improvement > Components: alerts >Affects Versions: trunk >Reporter: Yao Lei > Attachments: AMBARI-18292.1.patch, AMBARI-18292.patch > > > By default, Ambari allow all notifications of all kinds of alert states > (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher. > However, sometimes we hope to filter notification of some alert states > This patch will resolve this by setting > 'notification.dispatch.alert.script.states' in ambari.properties as > following: > #Only dispatch WARNING and CRITICAL state notification > notification.dispatch.alert.script.states=WARNING,CRITICAL > If you don't set this property that means all notifications will be > dispatched > I think making the desired notifications configurable is useful for > Ambari users -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: AMBARI-18423_2.patch > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_2.patch, > create_alert_notification.png, edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-14536) Enhance the function of HdfsResource to copy matching wildcard files to hdfs
[ https://issues.apache.org/jira/browse/AMBARI-14536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei resolved AMBARI-14536. -- Resolution: Won't Fix > Enhance the function of HdfsResource to copy matching wildcard files to hdfs > > > Key: AMBARI-14536 > URL: https://issues.apache.org/jira/browse/AMBARI-14536 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei >Priority: Minor > Attachments: AMBARI-14536.patch > > > In some cases,we need to copy local matching wildcard files to hdfs. > eg. we'd like to copy /usr/lib/spark*.jar to hdfs by following codes in > Python: > params.HdfsResource(hdfs_dir_path, > type="file", > action="create_on_execute", > source="/usr/lib/spark*.jar", > group=params.user_group, > owner=params.pdm_user, > mode=0755 > ) > params.HdfsResource(None, action="execute") -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15676062#comment-15676062 ] Yao Lei commented on AMBARI-18423: -- Discarded See AMBARI-18912 > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png, enabled_alert_scirpt_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Resolution: Won't Fix Status: Resolved (was: Patch Available) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png, enabled_alert_scirpt_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Comment: was deleted (was: Please see the attached pictures that have shown the Web UI after applying this patch to Ambari) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png, enabled_alert_scirpt_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Comment: was deleted (was: Discarded See AMBARI-18912) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png, enabled_alert_scirpt_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: (was: AMBARI-18423_1.patch) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png, enabled_alert_scirpt_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: AMBARI-18423_1.patch > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png, enabled_alert_scirpt_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: (was: disabled_alert_scirpt_notification.png) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png, enabled_alert_scirpt_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: disabled_alert_scirpt_notification.png > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png, enabled_alert_scirpt_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: disabled_alert_scirpt_notification.png > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: enabled_alert_scirpt_notification.png > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png, enabled_alert_scirpt_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: AMBARI-18423_1.patch > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15571369#comment-15571369 ] Yao Lei commented on AMBARI-18423: -- Please see the attached pictures that have shown the Web UI after applying this patch to Ambari > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_1.patch, > create_alert_notification.png, disabled_alert_scirpt_notification.png, > edit_alert_notification.png, enabled_alert_scirpt_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: AMBARI-18423_01.patch > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, AMBARI-18423_01.patch, > create_alert_notification.png, edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert target which notification_type is ALERT_SCRIPT in web client
[ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-18423: - Attachment: (was: AMBARI-18423_01.patch) > Support creating/editing alert target which notification_type is > ALERT_SCRIPT in web client > > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei > Fix For: 2.5.0 > > Attachments: AMBARI-18423.patch, create_alert_notification.png, > edit_alert_notification.png > > > Ambari now only support creating/editing alert notifications of type > EMAIL/SNMP in web client. > This patch aims to support another notification type:ALERT_SCRIPT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally for the reason that hostnames are displayed in Ambari is was:If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally for the reason that hostnames are displayed in > Ambari is -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase,so we will not get any record. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally for the reason that hostnames are displayed in Ambari is > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase,so we will not get > any record. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Attachment: uppercase agent hostname .png > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any record. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record. This patch amis to convert hostname of metric record to lowcase before inserting into ams hbase. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any record. > This patch amis to convert hostname of metric record to lowcase before > inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19357) Flume metrics can't show if hostname of flume agent is not lowercase
[ https://issues.apache.org/jira/browse/AMBARI-19357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-19357: - Description: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record.This patch amis to convert hostname of metric record to lowcase before inserting into ams hbase. was: If hostname of flume agent is uppercase or mixed-case，web client will not show flume metrics normally. This is because we will query metric records by lowcase hostname displayed in ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached picture),so we will not get any record. This patch amis to convert hostname of metric record to lowcase before inserting into ams hbase. > Flume metrics can't show if hostname of flume agent is not lowercase > - > > Key: AMBARI-19357 > URL: https://issues.apache.org/jira/browse/AMBARI-19357 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Yao Lei > Attachments: uppercase agent hostname .png > > > If hostname of flume agent is uppercase or mixed-case，web client will not > show flume metrics normally. > This is because we will query metric records by lowcase hostname displayed in > ambari ,but the hostname in METRIC_RECORD is not lowcase (see attached > picture),so we will not get any record.This patch amis to convert hostname of > metric record to lowcase before inserting into ams hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
