HASTIC_IN_MEMORY_PERSISTANCE: false
HASTIC_DB_CONNECTION_TYPE: nedb
HASTIC_DB_CONNECTION_STRING: hastic:password@mongodb:27017/hastic
HASTIC_PORT: 8000
HASTIC_API_KEY: eyJrIjoiTlVvbnR5T0hHenpXZDNSQjAxWDE2a3V0RGlvRGc1ZDgiLCJuIjoiaGFzdGljX3NlcnZlcl91c2VyIiwiaWQiOjF9
GRAFANA_URL: http://infra-grafana
Removing the slash at the end of GRAFANA_URL
ORG_ID: 1
HASTIC_ALERT_TYPE: webhook
HASTIC_ALERT_IMAGE: false
HASTIC_WEBHOOK_URL: null
HASTIC_TIMEZONE_OFFSET: null
HASTIC_ALERTMANAGER_URL: null
HASTIC_SERVER_URL: http://hastic:8000
HASTIC_INSTANCE_NAME: infra-hastic-75897cd69d-skqf4
NeDB is used as the storage
Creating websocket server ... ws://localhost:8002# this worries me as it should be localhost:8000 (?) but I have not found any way that can be changed
Server is running on :8000
starting data puller with [] analytic units
data puller started
Got new analytic connection
Start analytics pinger...
Analytics pinger started
Analytics is up
HASTIC_WEBHOOK_URL is not set, skip sending notification: Analytics is up
Now in the grafana hastic app I see this:
So, connection to server succeeds, analytics is up and running as i can see in the logs. For some reason the zmqConectionString is not populated in Grafana app even though in the server logs i can see that it starts data puller with [] analytics units. Why is there an empty list on analytics units? I had the impression I would get at least one. I've been going through this guide here: https://github.com/hastic/hastic-grafana-app/wiki/Getting-started
Hi guys, I'm struggling for a few days to set it up and get it working, but no luck. My setup on kubernetes is as follows
apiVersion: apps/v1 kind: Deployment metadata: name: "{{ .Release.Name }}-hastic" labels: appName: "hastic" version: "0.3.9" annotations: kubernetes.io/change-cause: "deployed app version {{ .Values.hastic.version }}" spec: replicas: 1 selector: matchLabels: appName: "hastic" template: metadata: labels: appName: "hastic" version: "0.3.9" spec: restartPolicy: Always containers:
apiVersion: v1 kind: Service metadata: labels: appName: "hastic" name: "hastic" spec: type: NodePort ports:
The logs say: $ kctl logs -f infra-hastic-75897cd69d-skqf4 hastics
HASTIC_IN_MEMORY_PERSISTANCE: false HASTIC_DB_CONNECTION_TYPE: nedb HASTIC_DB_CONNECTION_STRING: hastic:password@mongodb:27017/hastic HASTIC_PORT: 8000 HASTIC_API_KEY: eyJrIjoiTlVvbnR5T0hHenpXZDNSQjAxWDE2a3V0RGlvRGc1ZDgiLCJuIjoiaGFzdGljX3NlcnZlcl91c2VyIiwiaWQiOjF9 GRAFANA_URL: http://infra-grafana Removing the slash at the end of GRAFANA_URL ORG_ID: 1 HASTIC_ALERT_TYPE: webhook HASTIC_ALERT_IMAGE: false HASTIC_WEBHOOK_URL: null HASTIC_TIMEZONE_OFFSET: null HASTIC_ALERTMANAGER_URL: null HASTIC_SERVER_URL: http://hastic:8000 HASTIC_INSTANCE_NAME: infra-hastic-75897cd69d-skqf4 NeDB is used as the storage Creating websocket server ... ws://localhost:8002 # this worries me as it should be localhost:8000 (?) but I have not found any way that can be changed Server is running on :8000 starting data puller with [] analytic units data puller started Got new analytic connection Start analytics pinger... Analytics pinger started Analytics is up HASTIC_WEBHOOK_URL is not set, skip sending notification: Analytics is up
Now in the grafana hastic app I see this:
So, connection to server succeeds, analytics is up and running as i can see in the logs. For some reason the zmqConectionString is not populated in Grafana app even though in the server logs i can see that it starts data puller with [] analytics units. Why is there an empty list on analytics units? I had the impression I would get at least one. I've been going through this guide here: https://github.com/hastic/hastic-grafana-app/wiki/Getting-started