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

Meetme Plugin Error - No metrics to send to NewRelic this interval #553

Open
JustGithub1 opened this issue May 23, 2018 · 2 comments
Open

Comments

@JustGithub1
Copy link

We have installed the Meetme plugin and it is not started. Received error below. Appreciate any suggestion to resolve the issue.

Thank you,
JP

INFO 2018-05-23 13:44:13,255 33 MainProcess MainThread newrelic_plugin_agent.agent init L55 : Agent v1.3.0 initialized, Linux-4.4.0-43-Microsoft-x86_64-with-glibc2.7 (Ubuntu 16.04 xenial) CPython v2.7.12
INFO 2018-05-23 13:44:13,256 33 MainProcess MainThread helper.controller run L251 : newrelic-plugin-agent v2.4.2 started
WARNING 2018-05-23 13:44:13,256 33 MainProcess MainThread newrelic_plugin_agent.agent send_components L217 : No metrics to send to NewRelic this interval
INFO 2018-05-23 13:44:13,256 33 MainProcess MainThread newrelic_plugin_agent.agent process L133 : Stats processed in 0.00 seconds, next wake in 59 seconds
WARNING 2018-05-23 13:45:13,257 33 MainProcess MainThread newrelic_plugin_agent.agent send_components L217 : No metrics to send to NewRelic this interval
INFO 2018-05-23 13:45:13,260 33 MainProcess MainThread newrelic_plugin_agent.agent process L133 : Stats processed in 0.00 seconds, next wake in 59 seconds

@doreplado
Copy link

@Jackpham6407 try setting the cfg log-level to DEBUG for requests and the agent. I had a similar issue where my license key had a typo and I didn't know until I turned on debug.

@hansgv
Copy link

hansgv commented Sep 10, 2018

I have a similar issue (running Ubuntu 18.04). Rising the log levels to debug doesn't provide any additional information. My conf is pretty simple. The conf URLs (http:/127.0.0.1:80/nginx_status , http:/127.0.0.1:80/status-php56 and http:/127.0.0.1:80/status-php72 all respond)

nginx:
    name: my.hostname.here
    scheme: http
    host: 127.0.0.1
    port: 80
    path: /nginx_status

php_fpm:
  - name: fpm56-pool
    scheme: http
    host: 127.0.0.1
    port: 80
    path: /status-php56
    query: json
  - name: fpm72-pool
    scheme: http
    host: 127.0.0.1
    port: 80
    path: /status-php72
    query: json

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

3 participants