Open Distro for Elasticsearch has Rollup implemented. But this is missing on the AWS Elasticsearch service. I do really need this feature. Is there anyway to implement this feature or does anybody have any solution which they are currently doing in this area?
Rollups were released in version 1.12.0 of OpenDistro which includes version 7.10.0 of Elasticsearch OSS
Related
Any best way to create a kibana automated snapshot to GCP storage as I am using an older version of Kibana 7.7.1, Also I do not have any automated backup currently.
Kibana has Snapshot lifecycle management(SLM) that helps you do this. You have to run the Kibana with basic license
Here is a tutorial, you could also directly use the SLM API to create and automate this process along with Index-lifecycle management.
I am trying to enable search with Elasticsearch enabled for my self-hosted Gitlab instance.
My question is this:
I have an Elasticsearch instance that is external to my Gitlab instance i.e. my Gitlab instance is hosted on one server and my Elasticsearch instance is hosted on another server.
Am I able to use the external Elasticsearch instance to provide the Elasticsearch functionality that Gitlab requires in order to enable Advanced Search functionality?
Thanks,
Sean
As long as you have network connectivity between your gitlab instance and your Elasticsearch instance, you can use the Elasticsearch functionality.
Elasticsearch provides all the features and API in form of REST request and designed for distributed systems where several component of an application are hosted separately.
Note: you can just use the curl command curl :9200 from your gitlab instance to see if you have network connectivity and if not, using security setting you can enable them , like in AWS ports settings can be changed using the security group.
Note: GitLab 15.0 (May 2022) offers new options.
Advanced Search is compatible with Elasticsearch 8
Elasticsearch 8 is the current version of Elasticsearch by Elastic. Previously, you could not use Elasticsearch 8 for Advanced Search. You had to use older versions instead. Starting in 15.0, you can use Elasticsearch 8 for Advanced Search.
If you use Elasticsearch 7.x, you must upgrade to GitLab 15.0 before upgrading to Elasticsearch 8.
If you use Elasticsearch 6.8, upgrade to any Elasticsearch 7.x version before upgrading to GitLab 15.0.
See Documentation and Epic.
And even, still with GitLab 15.0 (May 2022)
Advanced Search is compatible with OpenSearch
OpenSearch is an open source Elasticsearch fork. Prior to GitLab 15.0, Advanced Search was not compatible with OpenSearch. If you used AWS-managed services, you had to use older versions of Elasticsearch.
You can now take full advantage of OpenSearch for Advanced Search.
See Documentation and Epic.
I am usig elasticsearch 5.6 version.
Is there a way to add password to elassticsearch without an x-pack plugin and gold license?
I saw that x-pack supports security with basic license, but only from 6.8 version.
Currently, I can't upgrade elasticsearch and look for another way to add authentication (RBAC) to elasticsearch 5.6.
AFAIK Unfortunately, before 6.8 as you already mentioned basic X-pack security is not available and if you need RBAC at field and document level then it's not even available in Gold license and for that, you need to buy platinum or enterprise license.
I would suggest you go through the Elastic stack security section under Elastic subscription to see what is included and what is not included.
Apart from the other answer, you can look at [this shield] (https://www.elastic.co/guide/en/shield/current/index.html)
You can refer this post
This is the way with 5.6 ES and kibana.
I am confused in choosing the right version of Kibana with Elastic Search 5.1.
Is it necessary to use Kibana 5.1 with Elastic Search 5.1 or can I use any version? Please suggest.
Thanks
As mentioned in the official Kibana documentation:
Kibana should be configured to run against an Elasticsearch node of the same version. This is the officially supported configuration.
Running different major version releases of Kibana and Elasticsearch (e.g. Kibana 5.x and Elasticsearch 2.x) is not supported, nor is running a minor version of Kibana that is newer than the version of Elasticsearch (e.g. Kibana 5.1 and Elasticsearch 5.0).
However, in order to facilitate an upgrade process where Elasticsearch is upgraded first, you can run a minor version of Elasticsearch that is higher than Kibana (e.g. Kibana 5.0 and Elasticsearch 5.1). But this should only be temporary
I'm running an ELK stack and would like a strategy for automatically retiring logs older than a certain age... I have tried using elasticsearch-curator but it requires python 2.7 and I have python 2.6.6, and am anxious to upgrade python in case I break other packages.
Is there a similar product or does the elasticsearch api cater for such a requirement?
The older versions of curator will work with older versions of ElasticSearch ( I'm using curator version 3.1.0 with a 1.7.1 ES cluster.)
We started out using the Elasticsearch S3 archiving plugin but soon discovered certain limitations when wanting to restore data. We also experienced performance issues with the plugin, which tended to slow down the entire cluster. Since then, we have migrated to a new system in which we archive the data for us and our customers using our own code before indexing the data to Elasticsearch in a clear text format. This gives us all the flexibility we and our customers require.
You may be mistaking the dependency on a given version of the elasticsearch-py module for a version of Elasticsearch. Curator version 3.5.1 requires es-py 2.3, but works with any version of elasticsearch greater than 1.0.