[ZBXNEXT-4968] Allow to customize indices/index names for Elasticsearch Created: 2019 Jan 18  Updated: 2020 Mar 17

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F), Server (S)
Affects Version/s: 4.0.3, 4.2.0alpha2
Fix Version/s: None

Type: Change Request Priority: Minor
Reporter: jchegedus Assignee: Valdis Murzins
Resolution: Unresolved Votes: 3
Labels: Elasticsearch, database, patch, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File elastic_feature_cfg.txt     File elastic_feature_zabbix_4.0.3.patch    
Issue Links:
Duplicate

 Description   

Problem
I got a project that will require to run two zabbix servers at once, looking into different hosts and objects. Well, I can simply say on the configuration to use different database names on the MySQL, although, wanting to use Elasticsearch as a history storage, it will not allow me to do the same. I cannot give custom names to the indices that zabbix will use. Installing two elasticsearch clusters is not an option as the one cluster is licensed.

Solution
As I need to go forward with the project, I have wrote a patch for Zabbix which allow me to work with prefixes to indices, allowing me to add a 5 character word in front of the index name..., but obviously, the best would be to have that implemented in Zabbix itself, so I don't have to patch my source in coming versions.

I see other similar requests but, I could not find one specifically to add this feature.

Attached you will find a patch that fix the problem on the server binary and the PHP interface and I have successfully deployed a server using such feature.

For the configuration file part, I just need to add this:

HistoryIndicePrefix=prefix

With this, it will allow me to run as many servers I want against the same elasticsearch cluster.



 Comments   
Comment by jchegedus [ 2019 Jan 18 ]

Just found this one now: https://support.zabbix.com/browse/ZBXNEXT-4513 – anyway, here there is a solution provided

Generated at Thu Apr 25 18:24:12 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.