hi, Roberto:
thanks for your suggestion, I found the reason in the below code
// do not waste time if no --rrdtool option is defined
if (!u_rrd.directory) return;
with no rrdtool option, uwsgi will not create rrd file so rrd_update faile.
so if I add rrdtool option to specify rrd file dir, everything is ok
but in the doc, https://uwsgi-docs.readthedocs.org/en/latest/Metrics.html,
uwsgi --rrdtool my_rrds ...
# or
uwsgi --stats-push rrdtool:my_rrds ...
It seems that stats-push can instead of rrdtool option ?
At 2016-01-12 17:43:35, "Roberto De Ioris" <[email protected]> wrote:
>
>> hello:
>>
>>
>> when I config uwsgi like below:
>>
>>
>> enable-metrics = true
>> stats-push = rrdtool:/home/project/project/data/rrd
>> rrdtool-freq = 30
>> rrdtool-lib = librrd.so
>>
>> uwsgi report all metric like this : ERROR:
>> rrd_update("/home/project/user/data/rrd/core.avg_response_time.rrd",
>> "N:2270")
>>
>>
>> I use apt-get intall librrd-dev for the librrd.so
>>
>>
>> I think I had made some mistakes, and how to deal with the problem ?
>>
>
>
>hi, can you check the rrd files have been created and initialized ?
>
>
>--
>Roberto De Ioris
>http://unbit.com
>_______________________________________________
>uWSGI mailing list
>[email protected]
>http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
