Continuous observation and recording of systems and processes to ensure performance and reliability is called Monitoring. Learn about the relevance of monitoring with distributed architecture and microservices architecture models.

Learn about the different approaches and techniques that software development teams use to monitor their complex and ever-growing systems.

Learn how Observability differs from Monitoring and when and why you need to invest in building an observability platform for your systems.

Metrics alone are insufficient for providing a clear picture of your software echo system and cannot help you diagnose the root cause of problems alone. Learn about the various types of telemetry data that is collected and analysed by New Relic One.

There are several methods for transferring the telemetry data from your infrastructure and applications to the observability platform. New Relic One supports more than one method. However, it prefers the collection and sharing of metrics using agents. In this lecture you will learn that how agents work and what types of agents are used in New Relic One.

The New Relic Observability Platform is a cloud-based platform that provides a unified view of your entire software stack, from infrastructure to applications to end-user experience. It collects and analyzes telemetry data from various sources, including metrics, logs, and traces, to give you a real-time view of how your systems are performing.

New Relic helps you to:

• Monitor your systems for performance and reliability: Identify and troubleshoot problems quickly and easily.

• Optimize your systems for efficiency and cost: Understand how your systems use resources and identify opportunities to improve performance.

• Improve the end-user experience: Get insights into how users interact with your systems and identify areas where you can improve the experience.

Putting all our learnings into one diagram will give you a clear picture as to how New Relic One works as an observability platform.

New Relic University has provided us with free access to training accounts New Relic One. Learn about this learning environment and how you can access them.

The New Relic Command Line Interface (CLI) is a tool that allows you to manage your New Relic account and resources from the command line. It provides a variety of commands for tasks such as:

• Installing and configuring the New Relic infrastructure agent

• Managing entity tags and workloads

• Recording deployment markers

• Generating Nerdpack and Nerdlet templates

• Publishing and deploying Nerdpacks

• Subscribing to Nerdpacks

• Adding screenshots and metadata to the catalogue

The New Relic CLI is a powerful tool that can help you automate everyday tasks in your DevOps workflow. It is also a valuable tool for troubleshooting and debugging issues.

Learn how you can install  NewRelic Command Line Interface on Linux systems such as Amazon Linux. The CLI will enable you to automate a variety of aspects of New Relic, such as crating tags, which are helpful when you deploy a new release of an application or microservice to the production environment.

Learn how you can install  NewRelic Command Line Interface on Windows servers. The CLI will enable you to automate various aspects of New Relic, such as creating tags, which are helpful when you deploy a new release of an application or microservice to the production environment. You can use New Relic CLI to install some of the New Relic Agents such as New Relic Agent for Dot Net too.

If you are a DevOps engineer, you will likely use a Mac computer. In this lecture I will explain in details that how you can setup the New Relic CLI on your Apple Mac computer.

You can install New Relic CLI on a computer and automate and manage several different New Relic One accounts. The authentication details of each New Relic One account is stored in a Profile. In this lecture you will learn that how you can create profiles and activate them as you need them,

If your website or microservice is written in Microsoft .NET Framework, .NET Core or.NET 6 and above you can follow this lecture and install the New Relic One Agent For Dotnet and instrument your web application or microservice seamlessly.

With he advent of .NET Core, dotnet applications can be deployed to and hosted on the Linux operating system.  In this lecture, you will learn how you can instrument your .NET Core (and .NET 6+) applications on Linux using New Relic One Agent for Dotnet .

Java is the most common framework used to develop enterprise-grade applications. In this lecture, you will learn how you can install the New Relic Agent for Java and instrument a java application whether it is based on Springboot or Tomcat.

Python is the fastest-growing programming language, and it has increasingly been adopted for developing serverless and containerised microservices.

New Relic One has introduced the concept of Entities. It is important to know what Entities are and what they look like because in the future lectures when we learn about querying the data in New Relic you will use properties of Entitites to find the data that you want.

In a distributed or microservices-based architecture, several systems collaborate to fulfill a request. It is hard to understand how microservices interact in a vast software ecosystem. New Relic One makes this issue easy by keeping track of metrics that come from different sources and maintain their relationship.

Learn how to navigate around the New Relic One's user interface and find the information that help you monitor your systems.

Web and Browser applications run in the users' browser. They must be monitored differently because not only does their backend and client-side code affect the application's performance, but also the quality of its HTML and CSS may impact the user's experience. A poor user experience will also negatively impact the SEO ranking of public websites. In this lecture we will learn about Google's metrics for monitoring browser-based applications using New Relic One.

When users interact with websites, web applications and mobile applications, they send requests to the backend systems and receive responses from them. These requests and responses are called transactions. A transaction may traverse through several microservices to fulfil a request. In this lecture we will see that how we can view the path a request has traveled through.

APDEX is a concept that is widely used in New Relic One. In this lecture you will learn that what APDEX is, how it is calculated and how it is used.

Application Performance Monitoring or APM in New Relic One refers to monitoring the back-end microservices and server-side applications. In this lecture you will learn that how you find the information regarding a back-end application in New Relic Explorer.

In a real-world application, when the user interacts with a customer-facing application, they generate transactions that use databases to store and retrieve information. One transaction may use multiple databases for storing data, fast search and distributed caching. In this lecture we will see that how database interactions can be seen in New Relic One. We also learn about errors that are captured and need attention, and how you will manage them.

Metrics that Agents collect cannot show you where your code is not optimised, potential memory leaks and threading issues. You can find such issues with profiling your application in production environments using New Relic One's profiling capability.

In this lecture you will learn that how you can monitor the hardware and servers such as disks, memory and CPU.

An essential part of monitoring the infrastructure is monitoring databases, operating systems, message brokers and event streaming platforms. In this lecture, we will see how to set up the relevant agent for a hosted service, i.e., SQL Server and see its internal metrics in New Relic One.

So many systems are not hosted on-premises anymore; rather they are hosted on Amazon Web Services. Some companies use a hybrid model where part of their ecosystem is hosted on-prem and the rest on the cloud. It is necessary to bring the metrics of both environments to New Relic One to get a clear picture of the entire software ecosystem.

On top of the metrics that we collect from our applications and microservices, we also want to know if our websites are up, if our APIs are responding and if users can adequately interact with our websites. Synthetic monitoring in New Relic enables us to do so, and in this lecture we will learn about it.

DevOps engineers and developers cannot constantly look at dashboards and try to figure out if there is a problem. Alerts are a technical solution for this problem. By defining alerts New Relic One will tell us if something is out of ordinary. In this lecture we will learn about concepts such as alerts, issues, and incidents.

In this lecture you will learn that how you can set thresholds for alerts and how you can group the alerting conditions together.

In this topic you will learn that how you can handle incidents and issues that are raised by New Relic.

Once issues are raised, and incidents are created, they will only be visible in New Relic. We want out developers and support engineers to be notified quickly so they can take action and fix the problems. Therefore we will create workflows in New Relic One and define that what has to be done when an incident is created, and how our engineers are notified.

When we deploy a new version of the application to the Production environment, often websites and databases become inaccessible for a short period. Because they will not send any metrics to New Relic during that time, New Relic will raise alerts. But these alerts are false alarms and we must be able to mute them. In the lesson you will learn that how you can mute the alerting rules in New Relic.

NRQL or New Relic Query Language is a powerful querying language in New Relic One that enables us retrieve data that is not readily available in the New Relic Explorer (UI). In this topic you will learn the basics of NRQL.

In this lecture you will see that how you can filter out unwanted data using NRQL

Grouping results based on a given field or key is essential in any querying language. In NRQL you can group the query results based on fields such as host, application, dates and so forth. In this lecture you will learn how grouping is done in New Relic Querying Language or NRQL.

In New Relic Query Language (NRQL), limiting the results to a desired time window is very easy and intuitive. This topic shows that how a time windows is applied in NRQL.

Graphical representation of data is better understood by humans. New Relic One can easily draw diagrams and charts for us directly from NRQL so that we will not need another tool for drawing charts.

New Relic creates metrics in the background, and we can use them in our dashboards and graphs. Using NRQL you can obtain data that from Metrics and enrich your graphs and alerts.

The Common Vulnerabilities and Exposures (CVE) system provides a reference method for publicly known information security vulnerabilities and exposures. New Relic One can scan third-party libraries and, if enabled, the running code to find potentially exploitable vulnerabilities (EV).

Whilst the Vulnerability Management feature of New Relic looks for Common Vulnerabilities and Exposures (CVE) predominantly in third-party libraries, the new IAST capability in New Relic can perform a more aggressive vulnerability scanning for the running applications to find the exploitable vulnerabilities (CEV - Not to be confused with CVE) and reports them.

Once an exploitable vulnerability is discovered, New Relic can send notifications to Slack via a direct connection, or to other communication tools i.e., Microsoft Team via an incoming Webhook.