New Relic Monitoring for Your Application inside the PaaS
This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.
Click or tap a screenshot to view it at its original size.
Objective
This guide explains how to use New Relic Monitoring for Your Application inside the PaaS on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.
Before you begin
- Sign in with an account permitted to manage the relevant environment.
- Confirm the target environment, region and resources before saving changes.
- Create a backup or rollback plan before changing a production system.
New RelicIt is an application performance monitoring (APM) tool for Developers and Ops, focused on providing real-time insights into project performance and reliability. It is designed to identify and root problems that can track the throughput of web transactions. Analyze application exceptions Finds slowness in web browsing or requests and generally provides a lot of useful information for quick and convenient troubleshooting.

Since New Relic is one of the most frequently used and very popular solutions for application administration, we provide a special add-on that makes delivering it even easier. Usage based onJPS(Jelastic Packaging Standard) makes it possible to install this software with a single mouse click. And start tracking the most important server application data in minutes. Plus, you can stay up to date with the embedded option for automatically installing ready-to-use New Relic.
So let's see how to reveal the hidden performance of your application with the help of New Relic - to proceed with the installation of this add-on you will need:
- A registered New Relic account with your unique user identifier (e.g. license key).
- At least 1 environment created on our platform with deploy the app you want to monitor.
Once these conditions are met you can integrate the New Relic agent into your cloud environment - just follow the steps below.
Note:New Relic monitoring software installations can be seamlessly updated to the latest version with the relevant add-on options.
Installing the New Relic add-on
You can install the New Relic add-on on Java (managed as Java agent) or PHP environment.
However, the installation process is similar - for example we use the Java environment with the Tomcat application server.
Note:Currently supported Java application servers are:Tomcat, TomEEandJettyof all versions The ability to use New Relic checksums with other servers is planned to be further added.
1. The first step is to click the Marketplace button at the top of your dashboard.

2. Click on the sectionAdd-onsSelectNew Relic APMthat appears in the list (You can search in the Search box above) and click.Install

Tips:New Relic APM agent is also available atJelastic JPS CollectionAlong with the JPS solution, you canimportand integrate them into any manifest using the link to the manifest.jps file within the appropriate repository.
3. You will see an installation frame appear:

On this page you should specify the following information:
- Application name- Enter a domain name for this app to display at your New Relic dashboard, e.g. my-project (environment domain is replaced by default here if switching between multiple domains)
- License key- Your unique identifier that is tied to each New Relic user and can be found in your Account Settings section.admin panel(To ensure that the information collected is reported to your account)


Note:channelLicense keyThe add-on installation frame contains a key mask by default. You can complete the installation without any changes. But you won't be able to explore the collected statistics. (Because there is no New Relic account tied to it)
However, you can specify this parameter later in the New Relic add-on settings usingConfiguration ManagerThe paths for the required files are:
forJavaapp servers:
-TomEE,Tomcat- /opt/tomcat/lib/newrelic/newrelic.yml
-Jetty- /opt/jetty/lib/newrelic/newrelic.yml
forPHPapp servers: The appropriate parameters can be found at the end of the etc/php.ini file (within the app servers section).[newrelic])
Additionally, the remaining add-on parameters can be edited within these files.
- Environment name- Select the name of the environment in which New Relic should be installed (the appropriate name will be highlighted in the drop-down list).
- Nodes- Select the instance for functional verification (currently only the application server can be selected).
Click the buttonInstallto confirm your entry and begin the deploy process.
4. Wait just a few minutes and the add-on will be added to your application.

5. According to the pop-up shown above. You'll need to restart your node to make your app more efficient. Click the button.Restart node(s)next to your server application.

Note that if your project is running on a single app server node, restarting it will cause your application to pause.
However, in case your server app isResize horizontallyDowntime is reduced because all server instances are restarted sequentially. You can fix this inconvenience by setting a delay for this operation on each subsequent node within the layer. While one node is undergoing maintenance, the remaining nodes will remain operational.
6. You can now log into your New Relic account and view within the collected data about your application's performance indicators. You can view the most important parameters in real time through custom dashboard reports and receive automatic alerts on important issues as they occur and more - see the list.monitoring featuresAll available

You will see that installing the New Relic add-on is very easy and doesn't take much time. At the same time, it is powerful enough to help deal with emerging problems and inefficiency problems.