New Relic is a performance monitoring tool.
In order to share links you need to both be logged in as the same user.
New Relic Slack Alerts¶
You can set up New Relic to send out alerts to a slack channel. There are 2 main steps to follow.
Setting up Slack to speak to New Relic¶
- While on the New Relic homepage, click on "Alerts new" on the top right.
- On the middle of this page at the top, select "Notification Channels"
- Click on "New notification Channel" and change the channel type to "Slack"
- We now need a webhook link from slack. Go to the apps and intergrations page on slack.
- Click Manage on the top right
- In here you should already see New Relic click on it. If for some reason this is not the case, you will have to add New Relic to slack.
- You should now see a list of configurations. This is where we will find the one we are about to make in future. Click on "Add Configuration".
- Choose the slack channel that alerts and updates will be posted to. The channel is usually related to the client.
- You will now see various expandable menus and also the intergrations settings. Scroll down to "Webhook URL" and copy the URL that is there.
- You now need to go back to into New Relic where we left off and paste in the URL we copied into "URL".
- Give it a name under "channel name" You shouldn't have to type out the channel where it says "Team Channel" as we already did this in Slack. But if for some reason you are not getting slack updates, it may be worth a try. Now select Create Channel
- You should now see your new channel in a list.
Setting the Alert policy in New Relic¶
- In the tabs under the New Relic logo, you should see "Alert policies". Click onto it
- Click onto "New alert policy" on the top right
- You will now have made a new policy. You can change the name of it by hovering over the name on the top left.
- Now we need to create a condition so click on "Add a condition".
- You will now see a few menus. You need to change these settings so that they make sense with the site. If you are part of the admin team, it is best to ask the dev who is assigned to the site.
- Before you hit "Save condition", you need to switch to the "notification channel" tab at the top.
- Click on "Add notification channels". A popup will appear which will show some folders.
- Open up the slack folder. Tick the slack channel intergration that was made earlier.
- Update the policy, switch the table to "Alert conditions" and hit "save condition"
That should be it. You're all set.
This is one of the main headings on the left. This covers all the data collected from the server. Under this you'll find the following items.
This gives you a quick overview of the health of the site.
You can control the time period in which you wish to review the data by selecting the 'Web transaction time' dropdown above the main graph or selecting (highlighting) a time period on the main graph. Once you've done this all the other monitoring data you'll view will adhere to this time period.
On the main graph you can see the total response time for each transaction. This is broken down into the different actors involved in the request e.g. PHP, MySQL etc.
This gives you a list of the worst performing transactions for the current time period. You can click on these to get more info.
The error rate over time.
This is a metric designed to give you an idea of how well the site is performing. On this screen you can see the score over time.
This gives you the number of requests per minute (rpm) over time.
This page provides a breakdown of transactions.
You can sort the transactions by:
- Most time consuming
- Slowest average response time
- Apdex most dissatisfying
- Highest throughput
On the left you'll see a list of transactions. You can click on these to get more details.
After clicking on a transaction you'll see a breakdown of the transaction and where the most time was spent.
If a transaction has taken longer than 4 * the apdex time then a transaction trace is stored by New Relic. This gives you a detailed trace of the transaction and how much time was spent at each step (see Trace details and Database queries tabs).
This section is much the same as transactions but focuses solely on database queries. The same as before you can sort the queries, click on them for details and view query traces for queries that take a long time to run.
Database Query Trace¶
This includes the query, optimisation options and the stack trace for the code that ran the query.
This lists all the external services used by the site and how much time they consume. Again this can be sorted and clicked on for more details.
The Errors section has been retired
This page displays all the errors that New Relic is aware of and how many times they've occurred withing your selected time frame.
New Relic seems to miss some errors so don't 100% rely on this.
You can click on the error to get more info including a stack trace.
Installing and Upgrading using the .rpm's¶
In order to upgrade New Relic you'll need to grab the latest
.rpm files from:
- 32 bit - https://download.newrelic.com/pub/newrelic/el5/i386/
- 64 bit - https://download.newrelic.com/pub/newrelic/el5/x86_64/
Then SCP these up to the server and upgrade using:
rpm -Uhv newrelic-php5-common-<version>.noarch.rpm newrelic-daemon-<version>.x86_64.rpm newrelic-php5-<version>.x86_64.rpm
You can find usage data at
Account (top right corner) > Account Settings > ACCOUNT > Usage.
Instance Size = Number of CPU Cores + Total GB of RAM
The instance size is capped at 16 per instance (server). This means that any resources over 16 aren't charged for.
CUs = Instance Size x Number of Hours Used
This means that for each hour in which you send at least one request to New Relic your CUs will increase by the instance size.
This is a flat charge per server being monitored. This charge is agreed with New Relic.