Thank you Daniel, I will take a look into that!

2013/7/13 Daniel Rinehart <[email protected]>

> If you are okay with setting up and running your own servers on EC2, I'd
> look into setting up a server with statsd and graphite. Then with a
> little hacking you can use the metrics collection infrastructure of
> nodetime but define a custom data sender that reports the data to your
> server instead. I used a similar approach and it worked wonderfully.
>
>
>
> -- Daniel R. <[email protected]> [http://danielr.neophi.com/]
>
>
> On Thu, Jul 11, 2013 at 5:00 PM, Guilherme Pim <[email protected]>wrote:
>
>> Hi guys!
>>
>> I have just launched a service and don't yet know well how to monitor it
>> and get a hang of what's going on. The service is comprised of a Node
>> server in Heroku, a MongoDB server in Amazon (medium), and a Redis server
>> in Amazon (micro).
>>
>>
>> I would very much like to monitor what's going on with all my servers:
>>
>> Node: I have to monitor Socket.io response times, and would like to have
>> access to what data was sent (because I have devised a system where the
>> message name is the same for all requests);
>>
>> MongoDb: is it possible to know query details (times, arguments,
>> strategy) in a generic fashion, with a plugable solution? I have tried MMS
>> but couldn't collect any data, so I would also like to know if MMS is any
>> good before going any further.
>>
>> Redis: may I know any details that may help me identify bottlenecks and
>> hickups?
>>
>>
>> I've experimented with NodeTime but couldn't get much out of it without
>> paying, because I have set up a clustered server and it is marking me as
>> having too many agents for the free plan.
>>
>> Do you know some sort of killer monitoring solution I'd be able to use
>> and orcherstrate it all?
>>
>>
>> I understand these are a lot of questions, so thank you for your time and
>> effort!
>> Guilherme Pim
>>
>> --
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "nodejs" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to