Elasticsearch

Enterprise search with Elasticsearch The reliable search solution for demanding projects

Elasticsearch is an open source search engine based on the Java library Apache Lucene. The program searches and indexes documents of different formats, stores the search results in a NoSQL format and outputs them in JSON format via a RESTful web interface.

The perfect tools for large datasets
The Elastic Stack (ELK) is a collection of open source software for searching large databases and analyzing logs. This includes the search engine ElasticSearch, Beats to collect metrics from different sources, Logstash to preprocess the data and Kibana for easy and comfortable data visualization.

What is Elasticsearch?

Elasticsearch is a search engine based on Lucene. The program, written in Java, stores all kinds of documents in a NoSQL format and returns them to the application via a RESTful API in JSON format.

Elasticsearch is not only a first-class tool for the page-wide search function, with the Elastic-Stack, logs and particularly large data stocks can also be conveniently analysed and visually prepared.

With Elastic, decisions can be made with the help of data. Next to Apache Solr, Elasticsearch is the most widespread search server in the enterprise environment.

Ingredient	Bakingtime	Bakery	Baking instructions
Cookie secret ingredient	1 year	TYPONiels HTML	Saves your consent to using cookies.
TYPO3 Users (Login)	session	TYPONiels HTTP	Assigns your browser to a session on the server.

Delicious toppings 🍯 from the Marketing Manufacture

With the help of these cookies we are trying to make our offer even more attractive for you. By means of pseudonymized data of website users the user flow can be analyzed and evaluated. This gives us the opportunity to optimize advertising and website content.

Ingredient	Bakingtime	Bakery	Baking instructions
User ID	13 months	Matomo HTML	Used to store a few details about the user such as the unique visitor ID.
Referrer	6 months	Matomo HTML	Used to store the attribution information, the referrer initially used to visit the website.
Session of the user	30 minutes	Matomo HTML	Short lived cookie used to temporarily store data for the visit.
Data of the session	30 minutes	Matomo HTML	Short lived cookie used to temporarily store data for the visit.
Temporary Data Object	30 minutes	Matomo HTML	Short lived cookie used to temporarily store data for the visit.
AdSense Audit	3 months	Google HTML	Used by Google AdSense to experiment with advertisement efficiency.
AMP Token	1 year	Google HTML	Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, request in progress or an error retrieving a Client ID from AMP Client ID service.
DoubleClick identifier	2 years	Google HTML	Used by DoubleClick (Google Tag Manager) to help identify the visitors by either age, gender or interests.
Survey Invitation	365 days	Hotjar HTML	Hotjar cookie that is set once a visitor interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.
Survey completed	365 days	Hotjar HTML	Hotjar cookie that is set once a visitor completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.
Survey (FeedbackMessage)	365 days	Hotjar HTML	Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.
Feedback form minimized	365 days	Hotjar HTML	Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show.
User identifier	365 days	Hotjar HTML	Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Letzte Aktivität	session	Hotjar HTML	This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).
TLD test	session	Hotjar HTML	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
Feedback User Attributes	session	Hotjar HTML	User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
User attributes (Cached)	session	Hotjar HTML	This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.
LocalStorage test	365 days	Hotjar HTML	This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
Page limit	30 minutes	Hotjar HTML	This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.
Session limit	30 minutes	Hotjar HTML	This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit.
Session Process Flag	30 minutes	Hotjar HTML	This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.

Do you need support for your next web project?