# Logstash-input-http\_poller install **URL:** \ **Category:** Logstash\ **Created:** [July 24, 2018, 6:53pm UTC](https://discuss.elastic.co/t/logstash-input-http-poller-install/141434 "2018-07-24T18:53:11Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![m.sereda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m.sereda/32/48232_2.png) [@m.sereda](https://discuss.elastic.co/u/m.sereda)\ **Post date:** [July 24, 2018, 6:53pm UTC](https://discuss.elastic.co/t/logstash-input-http-poller-install/141434/1 "2018-07-24T18:53:12Z")
Could you please explain me how to install `logstash-input-http_poller` on a last ELK stack? As I read I should to go to `cd /usr/share/elasticsearch` and after that use command `bin/elasticsearch-plugin install logstash-input-http_poller`. But I have a such output, how to install? ``` [root@localhost elasticsearch]# bin/elasticsearch-plugin install logstash-input-http_poller A tool for managing installed elasticsearch plugins Commands -------- list - Lists installed elasticsearch plugins install - Install a plugin remove - removes a plugin from Elasticsearch Non-option arguments: command Option Description ------ ----------- -h, --help show help -s, --silent show minimal output -v, --verbose show verbose output ERROR: Unknown plugin logstash-input-http_poller ``` ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 24, 2018, 9:44pm UTC](https://discuss.elastic.co/t/logstash-input-http-poller-install/141434/2 "2018-07-24T21:44:45Z")
Unless you are running a super old version of Logstash you shouldn't need to install it. Also; > [@m.sereda](#): > > [root@localhost elasticsearch]# bin/elasticsearch-plugin install logstash-input-http\_poller This is a Logstash plugin, not an Elasticsearch one, so the command you are running is not valid. ---
**Author:** ![m.sereda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m.sereda/32/48232_2.png) [@m.sereda](https://discuss.elastic.co/u/m.sereda)\ **Post date:** [July 25, 2018, 6:22am UTC](https://discuss.elastic.co/t/logstash-input-http-poller-install/141434/3 "2018-07-25T06:22:07Z")
OK, I see. Could you please help me to do the following: "collecting data periodically from multiple HTTP endpoints, and indexing the result in Elasticsearch" ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 25, 2018, 7:07am UTC](https://discuss.elastic.co/t/logstash-input-http-poller-install/141434/4 "2018-07-25T07:07:35Z")
Elasticsearch cannot connect to an endpoint like that, you need to use Logstash. ---
**Author:** ![m.sereda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m.sereda/32/48232_2.png) [@m.sereda](https://discuss.elastic.co/u/m.sereda)\ **Post date:** [July 25, 2018, 7:08am UTC](https://discuss.elastic.co/t/logstash-input-http-poller-install/141434/5 "2018-07-25T07:08:29Z")
ok, could you help me to do that in logstash? ---
**Author:** ![m.sereda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m.sereda/32/48232_2.png) [@m.sereda](https://discuss.elastic.co/u/m.sereda)\ **Post date:** [July 25, 2018, 7:13am UTC](https://discuss.elastic.co/t/logstash-input-http-poller-install/141434/6 "2018-07-25T07:13:52Z")
Maybe with help of metricbeat? ``` ###################### Metricbeat Configuration Example ####################### #========================== Modules configuration ============================ metricbeat.modules: - module: http metricsets: ["json"] period: 10s hosts: ["localhost:8080"] namespace: "json_namespace" path: "/api/session/login" # body: "" method: "POST" username: "admin" password: "mypass" request.enabled: true response.enabled: true #json.is_array: false #dedot.enabled: false # Set to true to enable config reloading #reload.enabled: false # 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 #============================== Dashboards ===================================== # These settings control loading the sample dashboards to the Kibana index. Loading # the dashboards is disabled by default and can be enabled either by setting the # options here, or by using the `-setup` CLI flag or the `setup` command. #setup.dashboards.enabled: false # The URL from where to download the dashboards archive. By default this URL # has a value which is computed based on the Beat name and version. For released # versions, this URL points to the dashboard archive on the artifacts.elastic.co # website. #setup.dashboards.url: #============================== Kibana ===================================== # Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API. # This requires a Kibana endpoint configuration. setup.kibana: # Kibana Host # Scheme and port can be left out and will be set to the default (http and 5601) # In case you specify and additional path, the scheme is required: http://localhost:5601/path # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601 host: "localhost:5601" #================================ Outputs ===================================== # Configure what output to use when sending the data collected by the beat. #-------------------------- Elasticsearch output ------------------------------ #output.elasticsearch: # Array of hosts to connect to. # hosts: ["localhost:9200"] # Optional protocol and basic auth credentials. #protocol: "https" # username: "elastic" # password: "root" #----------------------------- Logstash output -------------------------------- output.logstash: # The Logstash hosts hosts: ["localhost:5044"] # Optional SSL. By default is off. # List of root certificates for HTTPS server verifications #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"] # Certificate for SSL client authentication #ssl.certificate: "/etc/pki/client/cert.pem" # Client Certificate Key #ssl.key: "/etc/pki/client/cert.key" #================================ Logging ===================================== # Sets log level. The default log level is info. # Available log levels are: error, warning, info, debug #logging.level: debug # At debug level, you can selectively enable logging only for some components. # To enable all selectors use ["*"]. Examples of other selectors are "beat", # "publish", "service". #logging.selectors: ["*"] #============================== Xpack Monitoring =============================== # metricbeat can export internal metrics to a central Elasticsearch monitoring # cluster. This requires xpack monitoring to be enabled in Elasticsearch. The # reporting is disabled by default. # Set to true to enable the monitoring reporter. #xpack.monitoring.enabled: false # Uncomment to send the metrics to Elasticsearch. Most settings from the # Elasticsearch output are accepted here as well. Any setting that is not set is # automatically inherited from the Elasticsearch output configuration, so if you # have the Elasticsearch output configured, you can simply uncomment the # following line. #xpack.monitoring.elasticsearch: ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 22, 2018, 7:14am UTC](https://discuss.elastic.co/t/logstash-input-http-poller-install/141434/7 "2018-08-22T07:14:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.