homer7-docker
homer7-docker copied to clipboard
sipcapture
hom7-prom-all. no sip and qos data in grafana
Hello,
just run hom7-prom-all 7.7 branch in docker-compose and faced a problem - there are no data in grafana sip and qos graphics. It it a bug or did I something wrong?
@akam-it it all depends on the data you're sending. Can you find any sessions in the Homer UI to begin with? No sessions = no statistics
sure, there are many data about calls in homer ui. but no data in grafana (except Host Overview dashboard)
No reason it shouldn't work then - explore the queries for those widgets and let us know what they are actually returning, or play with the data ranges and we'll try figure it out as we go.
after docker-compose is up, created database folder is avahi(70), not my user is it ok?
Hello, it seems I have the same problem. From what I can see, prometheus doesn't have heplify_method_response records :
Everything else seems fine. Calls can be seen in Homer or Loki. heplify_packets_total seems fine too.
To reproduce the problem I remove all container / volumes and redo a docker-compose up in hom7-prom-all.
Let me know if you need more information.
Hi
+1 for the above post. I have done a fresh install today of hom7-prom-all and have the same symptoms.
I have faced the same issue, but it seems resolved when i have removed the IP (127.0.0.1)& name(local) from PromtargetIp & Promtagetname on the Docker-compose file.
Its because you need to specify all targets being scraped:
https://github.com/sipcapture/heplify-server/issues/267#issuecomment-531721523
Heplify will only expose metrics that are configured in HEPLIFYSERVER_PROMTARGETIP and HEPLIFYSERVER_PROMTARGETNAME
@karstenjakobsen I am trying to get into the Docker container for Heplify-server to make the changes you suggested above (I am having the same issue everyone else is) but cannot figure out how to get into the container to edit heplify's conf file. Any tips to get into the Docker container? The typical docker exec bash etc. does not function.
Ah, a simple reconfiguring of the docker-compose file was necessary - Missed that comment above. I apologize for overlooking it!
Thanks for all the reports fellas! I commented out the offending examples from the prometheus compose, could you guys confirm this satisfies the desired defaults?