search

Meteor-Community-Packages / organization

Discussions on organization of the organization 🎩
https://meteorjs.community/
41 stars 1 forks source link

New package for inclusion - (monitoring) meteor-apm-server #37

Closed afrokick closed 4 years ago

afrokick commented 5 years ago

meteor-apm-server

This project reduces the original Kadira APM to a single Meteor project and includes template MUP configuration to let you deploy to any remote server.

We use it in production last year, very stable.

Links

Current status of the project

I have a fork with some improvements, but i'd like to merge it into @Imachens repo.

Progress

vparpoil commented 5 years ago

We have been using it as well. I think we should also migrate the client repo : https://github.com/lmachens/kadira

afrokick commented 5 years ago

Yes, i created a separate issue for that https://github.com/Meteor-Community-Packages/organization/issues/38 for my fork of lmachens:kadira. But i can merge my fix into it if it more preferable.

afrokick commented 5 years ago

@lmachens what do you think?

lmachens commented 5 years ago

I found some maintainers for the project, so it is not abandoned. Anyway, how can I help?

SimonSimCity commented 5 years ago

I think it's worth mentioning as a note aside that there's also a good alternative to Kadira: the ELK stack. You might want to use it anyways if you're managing the infrastructure yourself - but it can be used equally easy for a hosted meteor installation: https://github.com/kschingiz/meteor-elastic-apm

evolross commented 5 years ago

Could one run Meteor APM and Elastic APM at the same time?

afrokick commented 5 years ago

I use Elastic only for logs. But don't like it. It consumes a huge amount of RAM.

evolross commented 5 years ago

When you say it consumers a lot of RAM - like just having the connection to Elastic (running on another machine) uses a lot of RAM? Or are you running Elastic on the same machine as your app and thus is uses a lot of RAM?

Could you explain more about your configuration. As I've been increasingly unsatisfied by Galaxy's logging and was going to set up the Elastic integration.

SimonSimCity commented 5 years ago

@evolross I haven't tried running them side-by-side. I was using a self-hosted version of Kadira (don't recall how we did it - I just now found tons of tutorials online which you can try out) which at some point in time got really slow - could well be that it would've been OK again with 5min of work - but we also wanted more NodeJS internal and also infrastructural metrics of our systems, so we did a hard cut. One metric we desperately were missing is the event-loop-delay.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.