Support Questions

Find answers, ask questions, and share your expertise
Announcements
We’ve updated our product names and community labels - click here for full details

ambari logsearch files are missing from ambari version 2.7.4

avatar

 

 

 

 

Hi all

 

On ambari 2.6.2 version we have the following logsearch files

 

 

find / -name *-logsearch-conf.xml

 

/var/lib/ambari-server/resources/common-services/ACCUMULO/1.6.1.2.2.0/configuration/accumulo-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/ATLAS/0.1.0.2.3/configuration/atlas-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/FALCON/0.5.0.2.1/configuration/falcon-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/FLUME/1.4.0.2.0/configuration/flume-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/HBASE/0.96.0.2.0/configuration/hbase-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/configuration/hdfs-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/KAFKA/0.8.1/configuration/kafka-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/KNOX/0.5.0.2.2/configuration/knox-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-custom-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/OOZIE/4.0.0.2.0/configuration/oozie-logsearch-conf.xml

/var/lib/ambari-server/resources/common-services/RANGER/0.4.0/configuration/ranger-logsearch-conf.xml

.

.

.

/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/configuration/hive-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1/configuration/kafka-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/KNOX/0.5.0.2.2/configuration/knox-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/LOGSEARCH/0.5.0/configuration/logfeeder-custom-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/configuration/oozie-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/configuration/ranger-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/RANGER_KMS/0.5.0.2.3/configuration/ranger-kms-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/configuration/spark-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/configuration/spark2-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/configuration/storm-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/configuration/yarn-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0/configuration/zeppelin-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.7.0/configuration/zeppelin-logsearch-conf.xml
/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5/configuration/zookeeper-logsearch-conf.xml

 

-----------------

 

NOW we installed the latest ambari version – 2.7.4 on other machine

 

rpm -qa | grep -i ambari

ambari-agent-2.7.4.0-118.x86_64

ambari-server-2.7.4.0-118.x86_64

 

my repo:

 

more ambari.repo
[ambari-2.7.4.0]
name=ambari-2.7.4.0
baseurl=http://master5.sys53.com/ambari/centos7/2.7.4.0-118
enabled=1
gpgcheck=0

 

But on the ambari latest version we have only that?

 

find / -name *-logsearch-conf.xml

/var/lib/ambari-server/resources/stacks/HDP/3.0/services/STORM/configuration/storm-logsearch-conf.xml

/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/STORM/configuration/storm-logsearch-conf.xml

 

 

Is it mistake? In ambari version – 2.7.4 ?

Why types of logsearch are missing from ambari 2.7.4 version

 

 

 

Capture.PNG

 

Michael-Bronson
1 ACCEPTED SOLUTION

avatar
Super Collaborator

logsearch-conf.xml files are removed as part of jira https://issues.apache.org/jira/browse/AMBARI-21212.

 

These are removed as xml files are not used for configuration. 

View solution in original post

2 REPLIES 2

avatar
Super Collaborator

logsearch-conf.xml files are removed as part of jira https://issues.apache.org/jira/browse/AMBARI-21212.

 

These are removed as xml files are not used for configuration. 

avatar

first thank you for your answer

the reason that I ask this question is because the blueprint json file is with the logsearch configuration

 

as the following example

 

},
{
"zookeeper-logsearch-conf" : {
"properties_attributes" : { },
"properties" : {
"component_mappings" : "ZOOKEEPER_SERVER:zookeeper",
"content" : "\n{\n \"input\":[\n {\n \"type\":\"zookeeper\",\n \"rowtype\":\"service\",\n \"path\":\"{{default('/configurations/zookeeper-env/zk_log_dir', '/var/log/zookeeper')}}/zookeeper*.log\"\n }\n ],\n \"filter\":[\n {\n \"filter\":\"grok\",\n \"conditions\":{\n \"fields\":{\"type\":[\"zookeeper\"]}\n },\n \"log4j_format\":\"%d{ISO8601} - %-5p [%t:%C{1}@%L] - %m%n\",\n \"multiline_pattern\":\"^(%{TIMESTAMP_ISO8601:logtime})\",\n \"message_pattern\":\"(?m)^%{TIMESTAMP_ISO8601:logtime}%{SPACE}-%{SPACE}%{LOGLEVEL:level}%{SPACE}\\\\[%{DATA:thread_name}\\\\@%{INT:line_number}\\\\]%{SPACE}-%{SPACE}%{GREEDYDATA:log_message}\",\n \"post_map_values\": {\n \"logtime\": {\n \"map_date\":{\n \"target_date_pattern\":\"yyyy-MM-dd HH:mm:ss,SSS\"\n }\n }\n }\n }\n ]\n}",
"service_name" : "Zookeeper"
}
}
},

 

can we get advice about how to remove the logsearch configuration tag's from the blueprint json file

Michael-Bronson