# Unable to execute metric beat command & unable to view on kibana **URL:** \ **Category:** Beats\ **Created:** [September 5, 2018, 9:01am UTC](https://discuss.elastic.co/t/unable-to-execute-metric-beat-command-unable-to-view-on-kibana/147349 "2018-09-05T09:01:44Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![kranthi\_851](https://avatars.discourse-cdn.com/v4/letter/k/67e7ee/32.png) [@kranthi\_851](https://discuss.elastic.co/u/kranthi_851)\ **Post date:** [September 5, 2018, 9:01am UTC](https://discuss.elastic.co/t/unable-to-execute-metric-beat-command-unable-to-view-on-kibana/147349/1 "2018-09-05T09:01:44Z")
Hi All, Two problems I am facing currently with the metric beat I have installed metricbeat on pc successfully but now I am unable to enable the modules. Its showing as apache not exist. Current my working directory is /usr/share/metricbeat/modules.d [root@Sibin modules.d]# metricbeat modules enable mysql Module mysql doesn't exist! Log file of metricbeat after starting the service 2018-09-05T14:15:18.327+0530 INFO instance/beat.go:273 Setup Beat: metricbeat; Version: 6.4.0 2018-09-05T14:15:18.327+0530 INFO pipeline/module.go:98 Beat name: Earth 2018-09-05T14:15:18.327+0530 INFO instance/beat.go:367 metricbeat start running. 2018-09-05T14:15:18.327+0530 INFO [monitoring] log/log.go:114 Starting metrics logging every 30s 2018-09-05T14:15:18.327+0530 INFO cfgfile/reload.go:140 Config reloader started 2018-09-05T14:15:48.329+0530 INFO [monitoring] log/log.go:141 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":10,"time":{"ms":19}},"total":{"ticks":30,"time":{"ms":48},"value":30},"user":{"ticks":20,"time":{"ms":29}}},"info":{"ephemeral\_id":"d5de602f-f24c-4069-837d-f04b7659f330","uptime":{"ms":30027}},"memstats":{"gc\_next":4194304,"memory\_alloc":2821696,"memory\_total":6956464,"rss":19427328}},"libbeat":{"config":{"module":{"running":0},"reloads":2},"output":{"type":"logstash"},"pipeline":{"clients":0,"events":{"active":0}}},"system":{"cpu":{"cores":4},"load":{"1":0,"15":0,"5":0.01,"norm":{"1":0,"15":0,"5":0.0025}}}}}} ![Screenshot%20from%202018-09-05%2014-29-34](https://us1.discourse-cdn.com/elastic/original/3X/5/9/5931d67485ce7028b268eea8b1b8f862418aa80f.png) ![Screenshot%20from%202018-09-05%2014-52-06](https://us1.discourse-cdn.com/elastic/original/3X/1/7/17ccc4fe69e6d7e60a91cbdaf4ad86780a1d32c8.png) Please resolve this ---
**Author:** ![kranthi\_851](https://avatars.discourse-cdn.com/v4/letter/k/67e7ee/32.png) [@kranthi\_851](https://discuss.elastic.co/u/kranthi_851)\ **Post date:** [September 5, 2018, 9:03am UTC](https://discuss.elastic.co/t/unable-to-execute-metric-beat-command-unable-to-view-on-kibana/147349/2 "2018-09-05T09:03:13Z")
###################### Metricbeat Configuration Example ####################### # This file is an example configuration file highlighting only the most common # options. The metricbeat.reference.yml file from the same directory contains all the # supported options with more comments. You can use it as a reference. # # You can find the full configuration reference here: # [https://www.elastic.co/guide/en/beats/metricbeat/index.html](https://www.elastic.co/guide/en/beats/metricbeat/index.html) #========================== Modules configuration ============================ metricbeat.config.modules: # Glob pattern for configuration loading path: ${path.config}/modules.d/\*.yml # Set to true to enable config reloading reload.enabled: true # Period on which files under path should be checked for changes #reload.period: 10s #==================== Elasticsearch template setting ========================== setup.template.settings: index.number\_of\_shards: 1 index.codec: best\_compression #\_source.enabled: false #================================ General ===================================== # The name of the shipper that publishes the network data. It can be used to group # all the transactions sent by a single shipper in the web interface. #name: # The tags of the shipper are included in their own field with each # transaction published. #tags: ["service-X", "web-tier"] # Optional fields that you can specify to add additional information to the # output. #fields: # env: staging By the way Output I has enabled as Logstash ---
**Author:** ![kranthi\_851](https://avatars.discourse-cdn.com/v4/letter/k/67e7ee/32.png) [@kranthi\_851](https://discuss.elastic.co/u/kranthi_851)\ **Post date:** [September 5, 2018, 10:01am UTC](https://discuss.elastic.co/t/unable-to-execute-metric-beat-command-unable-to-view-on-kibana/147349/3 "2018-09-05T10:01:05Z")
Now on kibana its showing like this: ![Screenshot%20from%202018-09-05%2015-29-21](https://us1.discourse-cdn.com/elastic/original/3X/2/e/2e3c7593fc4309798833971c4f64dcf6ca316785.png) As of now I have enabled the output as Elasticsearch. Please help me to sort it out this issue. ---
**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\ **Post date:** [September 5, 2018, 4:44pm UTC](https://discuss.elastic.co/t/unable-to-execute-metric-beat-command-unable-to-view-on-kibana/147349/4 "2018-09-05T16:44:30Z")
Hi, 6.4 has a known bug with modules directory, more details can be found here: [https://github.com/elastic/beats/issues/8104](https://github.com/elastic/beats/issues/8104) 6.4.1 will fix the issue and modules will be back on it's folder Br ---
**Author:** ![kranthi\_851](https://avatars.discourse-cdn.com/v4/letter/k/67e7ee/32.png) [@kranthi\_851](https://discuss.elastic.co/u/kranthi_851)\ **Post date:** [September 7, 2018, 9:46am UTC](https://discuss.elastic.co/t/unable-to-execute-metric-beat-command-unable-to-view-on-kibana/147349/5 "2018-09-07T09:46:01Z")
Error creating runner from config: 1 error: 1 error: metricset 'http/status' is not registered, metricset not found Now I am getting this error,could you please resolve this ? I am unable to get this issue. What are the metricset need to enable for http, I have alreay go through the metricset modules page but i didn't get what to write in the http.yml!! ---
**Author:** ![kranthi\_851](https://avatars.discourse-cdn.com/v4/letter/k/67e7ee/32.png) [@kranthi\_851](https://discuss.elastic.co/u/kranthi_851)\ **Post date:** [September 11, 2018, 5:02am UTC](https://discuss.elastic.co/t/unable-to-execute-metric-beat-command-unable-to-view-on-kibana/147349/6 "2018-09-11T05:02:35Z")
Is anybody there to resolve this issue! ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [September 11, 2018, 2:05pm UTC](https://discuss.elastic.co/t/unable-to-execute-metric-beat-command-unable-to-view-on-kibana/147349/7 "2018-09-11T14:05:35Z")
> [@kranthi\_851](#): > > What are the metricset need to enable for http, I have alreay go through the metricset modules page but i didn't get what to write in the http.yml!! What module are you trying to enable? The `http` module does not contain a `status` metricset. It has a `json` and `server` metricset as described [here](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-module-http.html). Heartbeat has a [http monitor](https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-heartbeat-options.html#monitor-http-check) that can check the server status. Perhaps that's what you want? ---
**Author:** ![kranthi\_851](https://avatars.discourse-cdn.com/v4/letter/k/67e7ee/32.png) [@kranthi\_851](https://discuss.elastic.co/u/kranthi_851)\ **Post date:** [September 12, 2018, 7:47am UTC](https://discuss.elastic.co/t/unable-to-execute-metric-beat-command-unable-to-view-on-kibana/147349/8 "2018-09-12T07:47:55Z")
Thanks for the reply, Yes I am expecting the sever status it working fine. Now like I need to monitor http like APM services do is there any alternatives for that one! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 10, 2018, 9:48am UTC](https://discuss.elastic.co/t/unable-to-execute-metric-beat-command-unable-to-view-on-kibana/147349/9 "2018-10-10T09:48:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.