-
Notifications
You must be signed in to change notification settings - Fork 2
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
New Relic: Migrate from "server" to "infrastructure" #90
Comments
ok thanks for the heads up. With one thing and another, looks like we have a bunch of increasing monthly running costs this quarter.
—
Kat Szuminska
…--- original message ---
On Fri, Apr 20, 2018 at 02:24 am, <[email protected]> Matthew Landauer wrote:
With breathtakingly little notice (less than a month), New Relic is shutting down server monitoring and forcing users to their "Infrastructure" tool. Not Happy.
Infrastructure costs money. We're already on a Pro account. Let's move and see how much it comes to. I don't think we can afford to not have server monitoring in place for any time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
--- end of original message ---
|
First step: get new agent installed on all server. With 377a98d that's done with the exception of morph and cuttlefish |
morph installed with openaustralia/morph@25d4d1d |
cuttlefish installed with openaustralia/cuttlefish@4ec5e9b and openaustralia/cuttlefish@a38a030 |
Still to do:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With breathtakingly little notice (less than a month), New Relic is shutting down server monitoring and forcing users to their "Infrastructure" tool. Not Happy.
Infrastructure costs money. We're already on a Pro account. Let's move and see how much it comes to. I don't think we can afford to not have server monitoring in place for any time.
The text was updated successfully, but these errors were encountered: