Skip to content
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

Open
mlandauer opened this issue Apr 19, 2018 · 5 comments
Open

New Relic: Migrate from "server" to "infrastructure" #90

mlandauer opened this issue Apr 19, 2018 · 5 comments
Assignees

Comments

@mlandauer
Copy link
Member

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.

@kat
Copy link

kat commented Apr 20, 2018 via email

@mlandauer mlandauer self-assigned this Apr 20, 2018
@mlandauer
Copy link
Member Author

First step: get new agent installed on all server. With 377a98d that's done with the exception of morph and cuttlefish

@mlandauer
Copy link
Member Author

morph installed with openaustralia/morph@25d4d1d

@mlandauer
Copy link
Member Author

cuttlefish installed with openaustralia/cuttlefish@4ec5e9b and openaustralia/cuttlefish@a38a030

@mlandauer
Copy link
Member Author

Still to do:

  • set up alerts
  • give sensible names to the servers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants