-
Notifications
You must be signed in to change notification settings - Fork 28
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
Newrelic Infrastructure #18
Comments
hi, haven't looked into that. Do you have a link? |
thx, will take a look at this |
@Evanlec Hi, any link to the source of this information? Just curious? Thanks |
Accounts created after Nov 2016 will not have access to the "Servers" module. Only Infrastructure. Which tells me they're phasing out Servers in favor of Infra. |
Thank you.
Looks like they are killing free server monitoring completely?
Infrastructure doesn't seem to be free, or am i missing something?
On Thu, Jan 26, 2017 at 11:46 AM Evan LeCompte <[email protected]> wrote:
https://docs.newrelic.com/docs/servers/servers-pages/servers-ui/new-relic-servers-new-relic-infrastructure
Accounts created after Nov 2016 will not have access to the "Servers"
module. Only Infrastructure. Which tells me they're phasing out Servers in
favor of Infra
…--
Sincerely,
Dmitry Kireev
Cell: +1 (818) 850-55-77
Skype: kireev.co
|
Yeah it's discouraging. We had Servers first, tried Infrastructure, went back to Servers. Infrastructure was at best alpha software. But they are pushing it hard. Not sure what happened to the idea that server coverage was a freebie to get you to buy their APM. By the way you can install Infrastructure across your estate with a one line ansible ad-hoc command. :-) |
We are probably just going to use TICK stack, works well so far.
…On Mon, Feb 20, 2017 at 4:00 PM, spikerobinson ***@***.***> wrote:
hard
--
Sincerely,
Dmitry Kireev
Cell: +1 (818) 850-55-77
Skype: kireev.co
|
Apparently Newrelic is dropping support for the nrsysmon in favor of the new "Infrastructure" platform.
Any chance we could get a ansible role for this?
The text was updated successfully, but these errors were encountered: