You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Juanjo Marron (JIRA)" <ji...@apache.org> on 2017/10/05 16:39:00 UTC

[jira] [Created] (AMBARI-22149) SmartSense pluggable architecture for third party services

Juanjo Marron created AMBARI-22149:
--------------------------------------

             Summary: SmartSense pluggable architecture for third party services
                 Key: AMBARI-22149
                 URL: https://issues.apache.org/jira/browse/AMBARI-22149
             Project: Ambari
          Issue Type: Improvement
          Components: ambari-server
    Affects Versions: 2.5.2
            Reporter: Juanjo Marron


 In the current SmartSense design, a third party service targeting to be integrated into the SmartSense collection scripts framework needs to deploy its own specification file under the SmartSense expected path. The scripts_dir by default is: /var/lib/smartsense/hst-agent/resources/collection-scripts but it accepts customization in the configuration file /etc/hst/conf/hst-agent.ini, so it could be different. 
 Similar to other frameworks and features in Ambari (service advisor, kerberos, quicklinks, extensions, role_command_order,  metrics, widgets, alerts or Ambari Log Search...) services should be self-described and easily pluggable on the SmartSense framework just by adding their own definition in the service directories itself.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)