<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Elasticsearch on Samarthya</title><link>https://samarthya.me/tags/elasticsearch/</link><description>Recent content in Elasticsearch on Samarthya</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© Samarthya 2018-2026. All rights reserved.</copyright><lastBuildDate>Sat, 01 Aug 2020 08:25:16 +0000</lastBuildDate><atom:link href="https://samarthya.me/tags/elasticsearch/index.xml" rel="self" type="application/rss+xml"/><item><title>Timeseries &amp; Index Management (ILM)</title><link>https://samarthya.me/posts/timeseries-index-management-ilm/</link><pubDate>Sat, 01 Aug 2020 08:25:16 +0000</pubDate><guid>https://samarthya.me/posts/timeseries-index-management-ilm/</guid><description>&lt;p&gt;Timeseries is a data stream that is defined for a set of fields over a time period. Some examples may include, daily attendance register for an organization, wherein people punching in every-morning will be different, missing mostly for weekends or on planned and unplanned leaves.&lt;/p&gt;</description></item><item><title>Elastic Alerting</title><link>https://samarthya.me/posts/elastic-alerting/</link><pubDate>Sun, 05 Jul 2020 00:00:00 +0000</pubDate><guid>https://samarthya.me/posts/elastic-alerting/</guid><description>&lt;h2 class="relative group"&gt;Watcher&#10; &lt;div id="watcher" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#watcher" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;Watcher is an Elasticsearch feature that facilitates alerting and can be used to create actions based on conditions, which are periodically evaluated using queries on your data. There are two ways of creating a watcher&lt;/p&gt;</description></item><item><title>Aggregations: Elastic</title><link>https://samarthya.me/posts/aggregations-elastic/</link><pubDate>Tue, 09 Jun 2020 00:00:00 +0000</pubDate><guid>https://samarthya.me/posts/aggregations-elastic/</guid><description>&lt;p&gt;Aggregation works on a group of documents and can be categorized&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Metric&lt;/li&gt;&#10;&lt;li&gt;Pipeline&lt;/li&gt;&#10;&lt;li&gt;Bucket&lt;/li&gt;&#10;&lt;li&gt;Matrix&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&#10;&lt;h2 class="relative group"&gt;Metric Aggregation&#10; &lt;div id="metric-aggregation" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#metric-aggregation" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;Computes a single or multiple values&lt;/p&gt;</description></item><item><title>LDAP Realm in Elasticsearch</title><link>https://samarthya.me/posts/ldap-realm-in-elasticsearch/</link><pubDate>Fri, 05 Jun 2020 04:18:06 +0000</pubDate><guid>https://samarthya.me/posts/ldap-realm-in-elasticsearch/</guid><description>&lt;p&gt;It is a short &lt;strong&gt;howto&lt;/strong&gt; guide which shall talk about adding a LDAP realm to an Elasticsearch 7.6.2 cluster.&lt;/p&gt;&#10;&#10;&lt;h2 class="relative group"&gt;Realms&#10; &lt;div id="realms" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#realms" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;It is a concept not alien to IDAM professionals. In simple words it is a system that allows you to authenticate and authorize an incoming request. It will define the entity USER, that may include at a bare minimum (not limited to)&lt;/p&gt;</description></item><item><title>Analyze: _analyze api</title><link>https://samarthya.me/posts/analyze-_analyze-api/</link><pubDate>Sat, 02 May 2020 10:21:09 +0000</pubDate><guid>https://samarthya.me/posts/analyze-_analyze-api/</guid><description>&lt;p&gt;Text is a key data in most of the information that is ingested in the &lt;strong&gt;elasticsearch&lt;/strong&gt;, and whether it is type &lt;code&gt;text&lt;/code&gt; or &lt;code&gt;keyword&lt;/code&gt; it requires careful consideration to choose which analyzer to use.&lt;/p&gt;</description></item><item><title>Pipeline: _ingest API</title><link>https://samarthya.me/posts/pipeline-_ingest-api/</link><pubDate>Thu, 23 Apr 2020 11:08:40 +0000</pubDate><guid>https://samarthya.me/posts/pipeline-_ingest-api/</guid><description>&lt;p&gt;Pipelines is a smooth way of processing some incoming data. In this blog, I will walk through some of the items I have tried my hands on.&lt;/p&gt;&#10;&#10;&lt;h2 class="relative group"&gt;Pipeline&#10; &lt;div id="pipeline" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#pipeline" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;A pipeline is a definition of a series of processors that are to be executed in the same order as they are declared.&lt;/p&gt;</description></item><item><title>API _reindex</title><link>https://samarthya.me/posts/api-_reindex/</link><pubDate>Mon, 06 Apr 2020 00:00:00 +0000</pubDate><guid>https://samarthya.me/posts/api-_reindex/</guid><description>&lt;p&gt;I will extrapolating based on the original documentation available &lt;a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html" target="_blank" rel="noreferrer"&gt;here&lt;/a&gt; and based on some of my experience using this API.&lt;/p&gt;&#10;&lt;blockquote&gt;&lt;p&gt;It copies documents from one index to another.&lt;/p&gt;&#10;&lt;/blockquote&gt;&lt;p&gt;Extracts the document source from the source index and indexes the documents into the destination index. You can copy all documents to the destination index, or reindex a subset of the documents.&lt;/p&gt;</description></item><item><title>ECS: Elastic common schema</title><link>https://samarthya.me/posts/ecs-elastic-common-schema/</link><pubDate>Thu, 02 Apr 2020 00:00:00 +0000</pubDate><guid>https://samarthya.me/posts/ecs-elastic-common-schema/</guid><description>&lt;p&gt;Open specification for document fields for data ingested in Elasticsearch. It brings uniformity to certain common fields that are used across data sources.&lt;/p&gt;&#10;&lt;p&gt;ECS defines two field levels&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Core fields: Represent the fields that are most common across all use cases.&lt;/li&gt;&#10;&lt;li&gt;Extended fields: That are not part of the core and specific to cases.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&#10;&lt;h2 class="relative group"&gt;Field sets&#10; &lt;div id="field-sets" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#field-sets" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;Field sets are multiple groups of related fields defined by ECS. More information &lt;a href="https://www.elastic.co/guide/en/ecs/current/ecs-field-reference.html" target="_blank" rel="noreferrer"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Text - Elastic</title><link>https://samarthya.me/posts/text-elastic/</link><pubDate>Sun, 29 Mar 2020 17:37:33 +0000</pubDate><guid>https://samarthya.me/posts/text-elastic/</guid><description>&lt;p&gt;If you are not aware of mapping, it might be a little confusing but I would try my best.&lt;/p&gt;&#10;&lt;p&gt;Every document that gets indexed in elastic has fields, every field that is accessible has an associated type with it (Inverted Index) which helps elastic organize data for quick retrieval.&lt;/p&gt;</description></item><item><title>Securing Elasticsearch</title><link>https://samarthya.me/posts/securing-elasticsearch/</link><pubDate>Wed, 25 Mar 2020 12:00:00 +0000</pubDate><guid>https://samarthya.me/posts/securing-elasticsearch/</guid><description>&lt;p&gt;In this post I will try to enable security for the elasticsearch cluster. It would be simply penned as a sequence of steps you need to follow to enable security as part of the cluster.&lt;/p&gt;</description></item><item><title>Elasticsearch v7.6</title><link>https://samarthya.me/posts/elasticsearch-v7-6-2/</link><pubDate>Mon, 24 Feb 2020 12:00:00 +0000</pubDate><guid>https://samarthya.me/posts/elasticsearch-v7-6-2/</guid><description>&lt;p&gt;In the previous blog we searched for a match_all, and sorted it by age. In this we will improve upon the query we are writing and look for other options.&lt;/p&gt;</description></item><item><title>Elasticsearch v7.6</title><link>https://samarthya.me/posts/elasticsearch-v7-6/</link><pubDate>Fri, 21 Feb 2020 11:24:29 +0000</pubDate><guid>https://samarthya.me/posts/elasticsearch-v7-6/</guid><description>&lt;p&gt;What I have been doing is evaluating Elasticsearch. The indexing, searching (Phrase, Similarity, Structured, Full Text, Complex), clustering etc. In this blog I will just try and simplify the learning curve.&lt;/p&gt;</description></item></channel></rss>