Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hom7-prom-all. no sip and qos data in grafana #50

Open
akam-it opened this issue Nov 29, 2019 · 12 comments
Open

hom7-prom-all. no sip and qos data in grafana #50

akam-it opened this issue Nov 29, 2019 · 12 comments
Assignees

Comments

@akam-it
Copy link

akam-it commented Nov 29, 2019

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?

Screenshot from 2019-11-29 13-22-10

@lmangani
Copy link
Member

@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

@akam-it
Copy link
Author

akam-it commented Nov 29, 2019

sure, there are many data about calls in homer ui. but no data in grafana (except Host Overview dashboard)
Screenshot from 2019-11-29 13-31-03
Screenshot from 2019-11-29 13-33-02

@lmangani
Copy link
Member

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.

@akam-it
Copy link
Author

akam-it commented Nov 29, 2019

after docker-compose is up, created database folder is avahi(70), not my user is it ok?
Screenshot from 2019-11-29 15-18-57

@Karnus
Copy link

Karnus commented Jan 3, 2020

Hello, it seems I have the same problem. From what I can see, prometheus doesn't have heplify_method_response records :

image

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.

@farmorg
Copy link

farmorg commented Jan 8, 2020

Hi

+1 for the above post. I have done a fresh install today of hom7-prom-all and have the same symptoms.

@benhamoua
Copy link

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.

@farmorg
Copy link

farmorg commented Jan 14, 2020

Same here:

  • "HEPLIFYSERVER_PROMTARGETIP="
  • "HEPLIFYSERVER_PROMTARGETNAME="

Screenshot 2020-01-14 at 10 40 49

@karstenjakobsen
Copy link

Its because you need to specify all targets being scraped:

sipcapture/heplify-server#267 (comment)

Heplify will only expose metrics that are configured in HEPLIFYSERVER_PROMTARGETIP and HEPLIFYSERVER_PROMTARGETNAME

@lukeescude
Copy link

@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.

@lukeescude
Copy link

Ah, a simple reconfiguring of the docker-compose file was necessary - Missed that comment above. I apologize for overlooking it!

@lmangani
Copy link
Member

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants