Search results for elasticsearch

ansible-pcp-2.3.0-3.lbn36.noarch

A collection containing roles for Performance Co-Pilot (PCP) and related software such as Redis and Grafana. The collection is made up of several Ansible roles, including: performancecopilot.metrics.pcp A role for core PCP capabilities, configuring live performance analysis with a large base set of metrics from the kernel and system services, as well as data recording and rule inference. performancecopilot.metrics.redis A role for configuring a local Redis server, suitable for use with a Performance Co-Pilot archive repository (for single or many hosts) and fast, scalable querying of metrics. performancecopilot.metrics.grafana A role for configuring a local Grafana server, providing web frontend visuals for Performance Co-Pilot metrics, both live and historically. Data sources for Vector (live), Redis (historical) and interactive bpftrace (eBPF) scripts can be configured by this role. The PCP REST API service (from the core pcp role) should be configured in order to use this role. performancecopilot.metrics.bpftrace A role that extends the core PCP role, providing metrics from bpftrace scripts using Linux eBPF facilities. Configuring authentication of a local user capable of running bpftrace scripts via the PCP agent is a key task of this role. performancecopilot.metrics.elasticsearch A role that extends the core PCP role, providing metrics from a live ElasticSearch instance for PCP analysis or exporting of PCP metric values (and metadata) to ElasticSearch for the indexing and querying of performance data.

nodejs-elasticsearch-15.1.0-1.lbn25.noarch

The official low-level Elasticsearch client for Node.js and the browser.

nodejs-elasticsearch-browser-12.0.0-1.lbn25.noarch

The official low-level Elasticsearch client, for use in the browser.

python3-elasticsearch-dsl-7.0.0-1.lbn25.noarch

Elasticsearch DSL Elasticsearch DSL is a high-level library whose aim is to help with writing and running queries against Elasticsearch. It is built on top of the official low-level client (elasticsearch-py < provides a more convenient and idiomatic way to write and manipulate queries. It stays close to the Elasticsearch JSON DSL, mirroring its terminology and structure. It exposes the whole...

collective.elasticindex-1.2.5-1.lbn19.noarch

This extension index Plone content into ElasticSearch. This doesn’t replace the Plone catalog with ElasticSearch, nor interact with the Plone catalog at all, it merely index content inside ElasticSearch when it is modified or published. In addition to this, it provides a simple search page called search.html that queries ElasticSearch using Javascript (so Plone is not involved in searching) and propose the same features than the default Plone search page. A search portlet let you redirect people to this new search page as well. This extension have been built for Plone 4, but might work with Plone 3. Usage After adding this extension to your buildout (including the zcml), you can install the extension in Plone. A configuration screen is available inside site setup. It will let you configure the URLs of the ElasticSearch servers to use in order to index, and search. To proceed: Fill in the ElasticSearch settings, Click on Save, Click on Create Index in order to create the ElasticSearch index, Click on Import site content in order to index already existing content in ElasticSearch. You can use the same ElasticSearch server (and probably index) for multiple Plone sites, creating a federated search that way. Security disclaimer By default is no authentication or access validation while searching or indexing content. The original purpose of this search is to be public. If you have private content that you don’t want to be searchable or viewable by unauthorized people, please be sure to check the checkbox index only published content in the configuration screen. In addition to this ElasticSearch is not secured by default, meaning there is no authentication to provide in order to index or look-up content. Be sure to hide it behind a firewall and use a proxy or Apache in order to restrict the requests made to it: you only need to allow access via POST to the sub-URL _search after the index name configured in the configuration screen. For instance, if the index name is plone, you shall allow only requests to http://your-public-es-url/plone/_search. After you configured your proxy, be sure to configure its public URL, like http://your-public-es-url in the configuration screen so the search page knows how to contact it. However if you want to allow users to search though restricted and not yet published content, you can check index security and uncheck index only published content in the configuration screen. After reindexing your content, if you check proxy search requests though Plone and apply security filter, search will work on restricted and not yet published content, but will be slower as the queries will be proxied though Plone.

dockbeat-1.0.0-1.final.lbn19.x86_64

Dockbeat is the new Dockerbeat name. We had to rename the project due to the Docker trademarking policy. Dockbeat is a Beat used for docker daemon monitoring. It is a lightweight agent that installed on your servers, reads periodically docker container statistics and indexes them in Elasticsearch. Exported document types There are five types of documents exported: type: container: container attributes type: cpu: container CPU usage statistics. One document per container is generated. type: net: container network statistics. One document per network container is generated. type: memory: container memory statistics. One document per container is generated. type: blkio: container io access statistics. One document per container is generated. type: log: dockbeat status information. One document per tick is generated if an error occurred.

elasticsearch-5.0.0-5.rc1.lbn19.noarch

Elasticsearch is a search server based on Lucene. It provides a distributed, multitenant-capable full-text search engine with a RESTful web interface and schema-free JSON documents. Elasticsearch is developed in Java and is released as open source under the terms of the Apache License. It is a flexible and powerful open source, distributed, real-time search and analytics engine. Architected from the ground up for use in distributed environments where reliability and scalability are must haves, Elasticsearch gives you the ability to move easily beyond simple full-text search. Through its robust set of APIs and query DSLs, plus clients for the most popular programming languages, Elasticsearch delivers on the near limitless promises of search technology.

elasticsearch-lang-python-2.4.1-1.lbn19.noarch

The Python (jython) language plugin allows to have python as the language of scripts to execute.

elasticsearch-plugin-analysis-icu-5.0.0-5.rc1.lbn19.noarch

The Store SMB plugin adds support for SMB stores.

elasticsearch-plugin-analysis-kuromoji-5.0.0-5.rc1.lbn19.noarch

The Store SMB plugin adds support for SMB stores.