Connect zamamd to grafana

[juliels]

Infos:

• Used Zammad version: V4.0
• Used Zammad installation type: (source, package, docker-compose, …): package
• Operating system: centos7
• Browser + version: chrome/firfox

Expected behavior:

• I want to connect my zammad instance to grafana

Actual behavior:

• I dont know how to configure grafana with the right parameters
  ->zammad and grafana are installed on different VM on the same private network

on zammad VM :

# curl http://localhost:9200
{
  "name" : "helpdesk.xxx.xx",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "yyyyyyyyyyyyyyyy",
  "version" : {
    "number" : "7.6.2",
    "build_flavor" : "default",
    "build_type" : "rpm",
    "build_hash" : "dfg8eb548236666466ggddtaabd087olhtngf",
    "build_date" : "2020-01-26T06:34:37.853214A",
    "build_snapshot" : false,
    "lucene_version" : "8.4.0",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}

How to configure grafana datasource? I couldnt found clear documentation with steps , just this ticket helped me Grafana dashboards - #2 by MrGeneration

->I can’t put http://localhost:9200 because its on another server
→ I have tried http://helpdesk.xxx.xx:9200

[olafbuitelaar]

Are you sure you can reach http://helpdesk.xxx.xx:9200 from your grafana machine? e.g. if you try the curl command instead with localhost, with your actual address.

[juliels]

I have solved the issue by adding in my file elasticsearch.yml

network.host: 0.0.0.0
discovery.seed_hosts: ["@grapfanaserver"]

and it worked fine, I hope this answer will helps.

[juliels]

I couldnt reach http://helpdesk.xxx.xx:9200 from my grafana server , I have posted the solution.
thank you for your answer it helped me

[MrGeneration]

@juliels

I have solved the issue by adding in my file elasticsearch.yml

network.host: 0.0.0.0
discovery.seed_hosts: [“@grapfanaserver”]

and it worked fine, I hope this answer will helps.

Warning

Please note that Elasticsearch contains very sensitive user information and does not require authentication by default. Above mentioned solution can work but should be considered highly insecure without further measurements in order to ensure only authenticated users or host can access the ES.

That’s out of our scope, please consult the Elasticsearch documentation for further hints on that topic.

[juliels]

Thank you for your remarks, I will look into it