I recall reading in some places it was broken by the business model change. Just wanted to get the most up to date information before I dive in head first.
I recall reading in some places it was broken by the business model change. Just wanted to get the most up to date information before I dive in head first.
Correct - when NewRelic removed their free tier, they disabled the endpoints used by our integration. We looked into updating for their changes, but the feedback we got from the developers who'd been using NewRelic up to that point was that their new pricing model wasn't acceptable, but there wasn't a good reason to invest the time in the update. If we get enough feedback from folks who are interested in paying NewRelic's current rates, we'll look into this again.
Thanks for the context. Do you have any recommendations for alternatives?
Even if it's a much simpler alternative, just having some basic performance insights might be helpful.
If not, np!
Your best bet for now is detailed logging, so that you can review performance along with info on the specifics of what the server is actually doing. Technically, the 9xxx port range is available, so you could conceivably use something like 99xx (depending on how many instances your configuration is set to run on a server), so you could use those ports (along with a key exchange, for security) to provide a way to connect to query the server for info directly. Granted, that would be querying each instance separately, but it would still serve to get you overall performance info.
We do plan to add in another server monitoring option later on, but I don't have a date I can share for that just yet.
2 People are following this question.
