June 2023 Summaries

As we reflect on our Pride Month celebrations, we stand proud and reaffirm our commitment to fostering a diverse, inclusive, and supportive environment for all employees, welcoming their sexual orientation, gender identity, and gender expression. We recognize that embracing diversity and its intersections is not just a moral imperative, but also a vital driver of innovation, creativity, and success. This year's celebration, "Strong. Proud. Thriving.", highlighted our commitment to strengthening diversity, equity, and inclusion efforts, with weekly allyship actions for Relics worldwide. The company encourages all employees to show up authentically every day, and the Rainbow Relics employee resource group partnered with OutFront Minnesota to educate Relics on advocacy basics. We also encourage supporting LGBTQIA+ businesses in communities and engaging in volunteerism, such as our event with Queer Lifespace where we volunteered by writing letters to support their development and fundraising initiatives. By fostering an inclusive culture, we continue to make a positive impact on the lives of Relics and the communities they live in around the world.

New Relic reflects on its Pride Month celebrations, emphasizing its commitment to fostering a diverse, inclusive, and supportive environment for all employees, particularly those within the LGBTQIA+ community. The company celebrated under the theme "Strong. Proud. Thriving," highlighting the importance of diversity, equity, and inclusion (DE&I) as drivers of innovation and success. New Relic's initiatives include sharing weekly allyship actions to promote day-to-day allyship, supporting LGBTQIA+ businesses, and engaging in volunteerism and advocacy training through partnerships like the one with OutFront Minnesota. The Rainbow Relics employee resource group and events with organizations like Queer Lifespace exemplify their efforts to empower LGBTQIA+ individuals and create spaces where everyone can be their authentic selves, ensuring that diversity thrives within the company and their communities.

New Relic has released three powerful query capabilities: subquery JOINs, lookups, and GeoIP. These enhancements allow users to resolve business-critical incidents with one query, understand how their technology stack impacts their business, and connect the dots between performance of applications and infrastructure, business operations, and customer experiences. Subquery JOINs enable combining data from different tables in the New Relic database, while lookups allow mapping alphanumeric strings to physical world or business data. GeoIP translates IP addresses into geographical data, enabling users to understand the origin of their traffic. These new query capabilities can be used to answer various questions and provide insights into system performance and business operations.

This powerful query capability allows you to resolve business-critical incidents with your data in one simple query, enabling effective analysis and enrichment across datasets by joining related datasets using subquery JOINs. Subqueries are limited but can be overcome by using subquery JOINs, which allow for analysis and enrichment across datasets, making it easier to combine application performance monitoring (APM) event data and metrics, logs and infrastructure, synthetics and NrAuditEvent, or custom events. By utilizing subquery JOINs, you can join two result tables together, determine correlations between data from different sources, and gain insights about the health and performance of your application that may not be obvious or easy to correlate. The syntax of a subquery JOIN requires three components: dataset 1, dataset 2, and a primary key that links the two datasets together, with specific rules governing the structure of the query, including the use of parentheses, ON clause, and limitations such as a maximum result limit of 5,000 rows.

Subquery JOINs are a powerful tool for resolving business-critical incidents by allowing the integration of related datasets to enhance data analysis and understanding. This blog post delves into the mechanics and benefits of subquery JOINs, demonstrating how they enable the joining of two result tables to facilitate comprehensive analysis and enrichment across different datasets. This process is crucial for analyzing telemetry data, where combining data from various sources can reveal correlations and trends that provide insights into the health and performance of applications and systems. The post explains the syntax and components required for executing subquery JOINs, such as dataset selection and linking primary keys, and emphasizes best practices like using `LIMIT MAX` to maximize results and `latest()` to maintain aggregated values. Examples illustrate how subquery JOINs can enrich datasets by integrating missing data, perform calculations across datasets, and parse log messages for data extraction. Despite some limitations, such as a 5,000 result cap and restrictions on high-cardinality relationships, subquery JOINs offer a versatile method for data enrichment and analysis, allowing teams to derive insights that might otherwise be difficult to uncover.

New Relic has announced the release of three new query capabilities—subquery JOINs, lookups, and GeoIP—that enhance the ability to resolve business-critical incidents by allowing faster and more comprehensive data analysis. These features enable users to correlate various datasets, such as application performance and infrastructure metrics, without needing additional tools. Subquery JOINs facilitate the combination of data from different tables, lookups allow mapping of alphanumeric IDs to understandable business data, and GeoIP translates IP addresses into geographical information, enriching data analysis. These capabilities are designed to improve understanding of how different components of a technology stack impact each other, thus unlocking new use cases like monitoring application response times, identifying unusual system behaviors, and tracing CDN traffic origins. The enhancements are available within the New Relic unified database, and users are encouraged to explore further through various resources and start using the new features, with the option of a free account offering limited access to data ingestion and user capabilities.

As head of platform engineering at IGS, the company's focus is on delivering business value via tooling, infrastructure, and end-to-end process without the day-to-day overhead of maintaining monitoring and fixing errors. Due to its product's nature, vertical growth requires high reliability, especially in handling larger volumes of data while keeping costs under control. The team initially used Application Insights but later switched to SaaS solutions like New Relic due to its Kubernetes-native approach, ease of consumption for end-to-end tracing, speedy instrumentation, and reduced cost and developer time. With New Relic's integration ecosystem, the company streamlined its production route, enabling faster feature deployment from code to customer availability. The platform also leverages logs in context, customizable alerts, Terraform automation, and a rich API, resulting in improved productivity and efficiency.

To integrate observability into your CI/CD pipelines and ensure confident deployment of applications, you can use New Relic change tracking with two different approaches: GraphQL and the New Relic CLI. Change tracking allows you to visualize deployments, validate changes, deliver them faster, and capture different events across your pipeline. With change tracking markers, you can record events, logs, anomalies, and incidents across deployed applications and services, and correlate errors, logs, and other metrics for valuable insights. The process of creating a user key, setting up environment variables, and integrating with CI/CD tools such as GitHub Actions, Ansible, and Jenkins is also explained in detail, making it easier to deploy markers and track changes in your pipeline.

Integrating observability into CI/CD pipelines is key for DevOps engineers, and New Relic's change tracking offers a way to visualize and validate deployments, enhancing the speed and accuracy of delivery. The blog post explores how to send change tracking events using either the New Relic CLI or the GraphQL API, with additional methods for implementing these markers through GitHub Actions, Jenkins, and Ansible. Change tracking provides insights into application changes and their impacts on related services, allowing for improved monitoring and troubleshooting. Prerequisites for deployment include a New Relic account and user key, with detailed steps provided for using both the New Relic CLI and GraphQL for creating deployment markers. The post also outlines integrating change tracking with popular CI/CD tools like GitHub Actions, Ansible, and Jenkins, emphasizing the importance of these markers in identifying and resolving deployment issues efficiently.

Intelligent Growth Solutions (IGS) has enhanced its platform engineering by adopting New Relic for monitoring and observability, allowing the company to manage their operations more effectively as they scale. The integration with Kubernetes and the adoption of open-source tools like OpenTelemetry and Prometheus have enabled IGS to streamline their processes, reduce costs by 58%, and decrease the mean time to recovery by 80%. New Relic's capabilities have facilitated a reduction in the time to move features from code to customer from 22 days to just 4 days by leveraging auto-instrumentation, real-time monitoring, and a ring-based deployment approach. This transition has allowed IGS to focus on delivering value to customers while maintaining high system reliability crucial for their vertical growth towers, which require consistent monitoring to prevent crop loss. Additionally, the new system has improved log management by providing contextual insights, thus simplifying the process of tracking and resolving issues across their distributed environments.

New Relic`, a leading Observability platform provider, has announced a restructuring plan aimed at simplifying the company's business and creating a singular focus on consumption. The plan will result in the departure of approximately 155 employees in the United States and up to 57 internationally, with a goal of reducing headcount by nearly every function, level, and region. The restructuring is part of New Relic's multi-year journey to transition its business into one that brings ubiquity to Observability while sustaining high growth rates and profitability. The company aims to accelerate its delivery of this promise through bold action, particularly in light of current economic uncertainty. Employees departing the company will receive severance pay, extended benefits coverage, mental health support, and career outplacement assistance.

New Relic's CEO, Bill Staples, announced a restructuring plan, affecting approximately 212 employees globally, as part of a strategic shift to enhance the company's focus on consumption-based business models. This decision follows a thorough review of roles and aims to align resources with New Relic's strategic priorities, which include exiting the subscription business within the next 4-6 quarters and continuing to grow its observability platform. Despite the layoffs, New Relic plans to maintain its headcount by hiring for essential roles and is committed to supporting departing employees with severance packages, extended benefits, and career assistance. As New Relic moves towards a more streamlined and profitable future amid economic uncertainties, it emphasizes maintaining high growth rates and optimizing resource allocation. The company remains dedicated to its core values and culture while navigating through these changes, and further details on the restructuring will be discussed in an upcoming company meeting.

The problem server administrators face is being able to tie disparate data from multiple sources together. One solution is to create a "swivel chair integration" with multiple dashboards on different screens, but this can be hard to compare and correlate data into meaningful insights. A better solution is to bring all data into one platform, such as New Relic, which can unify data and remove observability silos. This can be achieved by integrating open source server monitoring tools like Nagios, Zabbix, or Prometheus using alternate agents, APIs, or custom integrations. These tools can collect different types of data, some of which may not be available in every solution on the market, requiring multiple tools to be used together. By sending this data to New Relic, administrators can gain a unified view of their environment and make better decisions about their infrastructure.

Open-source server monitoring tools like Prometheus, Zabbix, and Nagios offer robust solutions for collecting and analyzing data, but they often result in fragmented data silos that complicate troubleshooting and data correlation. This blog explores how New Relic can unify disparate data sources, effectively acting as a data switchboard to address tool fragmentation and observability silos. By using alternative agents, APIs, or custom integrations, data from popular open-source tools can be seamlessly integrated into New Relic, enhancing data accessibility and analysis. Specific methods include using the New Relic agent with Nagios, the Zabbix API with New Relic Flex, and Prometheus as a data forwarder. These integrations provide a streamlined approach to consolidating server monitoring data, allowing for more comprehensive insights and improved decision-making without abandoning existing open-source infrastructures.

Open source software libraries are widely used in modern software development to accelerate development and reduce costs, but they also pose hidden security risks that can harm an organization's reputation and financial well-being. These risks include vulnerabilities in libraries, lack of control over open source code, complex dependency trees, outdated libraries, and the need for regular security audits, staying up-to-date with library versions, using reputable libraries, monitoring dependencies, and implementing code reviews to mitigate these risks. By understanding these risks and implementing effective strategies, developers can safeguard their software projects against potential vulnerabilities.

Open source software libraries are a crucial component of modern software development, often comprising 70-90% of an application, but they present hidden security risks that can threaten an organization's reputation and financial stability. These risks include vulnerabilities in library code, lack of control over open source code, complications from complex dependency trees, and the use of outdated libraries. Developers and security professionals need to understand these risks to proactively identify and address potential vulnerabilities, thereby improving software security. New Relic offers tools such as Security RX and APM agents to help detect and manage these risks by providing visibility into library vulnerabilities. To mitigate these risks, the article suggests conducting regular security audits, staying updated on library versions, selecting reputable libraries, monitoring dependencies, and implementing code reviews. These measures aim to safeguard software projects and ensure a more secure development environment.

The world wide web and Steve Jobs' introduction of the iPhone were two disruptive technologies that share a common trait with ChatGPT: limitless innovation fractals. These technologies have led to massive value creation opportunities, with trillions of dollars in shareholder value realized since their debut. The pace of innovation continues to increase, driven by innovation itself, creating a virtuous cycle of acceleration. Generative AI is another technology that promises to bring about a new wave of innovation and create new opportunities for businesses and consumers alike. It refers to artificial intelligence models that can generate new data based on existing patterns and has the potential to radically impact the observability industry in two fundamental ways: improving actionable insights delivery and shaping generative AI system capabilities. The observability industry is crucial for several reasons, including performance monitoring and optimization, issue detection and troubleshooting, enhanced robustness and reliability, compliance and governance, and quick response to changes. As generative AI continues to gain traction, the observability industry must be prepared to adapt and evolve to meet new challenges and opportunities. New Relic is already developing AI-specific observability solutions that can empower companies to build and maintain reliable AI systems. The transformative power of generative AI is undeniable, and its potential to reshape the observability industry is immense.

New Relic has been recognized as a Leader and Fast Mover in the 2023 AIOps Radar report by GigaOm, highlighting its advanced data collection, customizable dashboards, predictive capabilities, multi-cloud support, service level management, scalability, manageability & maintainability, and ease of use. This recognition follows New Relic's recent ranking as a Leader and Outperformer in the GigaOm Radar for Cloud Observability. The company is committed to innovation and delivering exceptional value to engineers, with its all-in-one observability platform providing a comprehensive solution for collecting, analyzing, and troubleshooting telemetry data. With its scalable data ingestion, commitment to open source, automated remediation, seamless API integration, and observability built directly into IDEs, New Relic aims to continue pushing the boundaries of observability innovation and setting new industry standards.

The company Koneksa adopted Kubernetes and Pixie to improve observability and instrumentation in their infrastructure, moving away from serverless solutions due to concerns over cost and overhead. They needed a tool that could handle spikes in data load, such as when all participants completed their study tasks at once. After exploring various open-source projects, they chose Pixie for its tracing capabilities and ability to provide pod-specific metrics without the need for sidecars. With Pixie integrated with New Relic, they gained detailed insights into their Kubernetes environment, including Linux Kernel data level, anomaly detection, and security scanning tools. They were able to optimize their Kubernetes rollout, develop custom alerts, and create a learning channel for their team to test different alerting strategies. The combination of logs, SLIs, and SLOs provided a full picture of their application performance, enabling them to identify and resolve issues before they reached production.

New Relic has been recognized as a leader and fast mover in GigaOm's 2023 AIOps Radar report, highlighting its strong position in the observability and AIOps space. The company's recent innovations, including the introduction of New Relic AI, a generative AI assistant, aim to democratize observability and enhance the operational efficiency of engineers by optimizing their workflows, reducing downtime, and improving customer experiences. New Relic's platform offers advanced data collection, customizable dashboards, predictive capabilities, and multi-cloud support, providing an integrated workflow across telemetry data. This approach seeks to eliminate integration challenges and inefficiencies associated with using multiple solutions, thereby maintaining a low total cost of ownership. The company continues to prioritize scalability, reliability, and open-source commitment, while forward-looking statements indicate a focus on further enhancing observability practices with new developments to come.

Koneksa's transition to Kubernetes and Pixie from a serverless architecture reflects a strategic shift to enhance observability and manageability of their infrastructure, crucial for handling the data-intensive demands of their clinical trial platform. Initially reliant on serverless solutions like AWS Fargate for scalability, Koneksa faced challenges with cost and integration overheads, prompting a return to self-managed nodes. This move allowed for improved host-level monitoring, essential for managing the burst-like data upload patterns of trial participants. By adopting Kubernetes and integrating open-source tools like Pixie, Koneksa enhanced their ability to monitor and troubleshoot applications in real-time, providing engineers with greater insights into performance metrics without the need for additional sidecars. This shift not only optimized their rollouts but also fostered innovation through detailed monitoring, empowering engineers to take ownership of their services and improve application performance monitoring (APM).

With .NET Core, you can build a wide variety of applications and services that work on any operating system. Monitoring your application's performance is crucial to understand its health and behavior, which helps identify and resolve issues quickly. New Relic quickstarts provide curated, opinionated monitoring for your entire technology stack in just a few minutes. The .NET Core quickstart helps you instrument and collect data from your .NET Core application, service, or infrastructure running on other technologies such as Windows, Linux, Azure, and AWS. Distributed software environments make tracking and troubleshooting issues complicated, but New Relic's all-in-one observability solution can help. By using the .NET Core quickstart, you'll get a pre-configured dashboard and alerts that detect changes in key performance metrics, such as CPU usage, total transactions, and slowest query time. The dashboard provides an overview of your application's performance, including charts for web transactions time, Apdex score, throughput, error rate, logs, transactions, and infrastructure. Alerts can help you stay on top of emergent issues in your application, and the quickstart guide includes steps to deploy the dashboard and alerts.

.NET Core allows developers to create versatile applications across various platforms, but monitoring performance is crucial to address speed and resource issues. New Relic offers a quickstart for .NET Core, which simplifies the setup of comprehensive monitoring through the installation of the New Relic .NET agent in environments like ASP.NET Core MVC applications running in Docker containers. It provides an interactive dashboard and alerts for key metrics such as CPU usage, transaction errors, and memory usage, offering a unified observability solution across diverse infrastructures including Azure, AWS, and on-premises setups. By centralizing telemetry data, New Relic supports cross-team collaboration and helps organizations transition from reactive to proactive management, enhancing decision-making and reducing service disruptions. The quickstart includes a pre-configured system with alerts for Apdex score, memory usage, and transaction errors, enabling organizations to maintain application performance and customer satisfaction.

New Relic website performance monitoring is a free tool that simplifies the task of monitoring your website's speed and reliability without requiring complex engineering setup. It offers continuous performance tracking across multiple pages, allowing you to proactively identify and address issues before they impact revenue. With timely alerts for outages and visibility into areas for improvement, New Relic helps improve customer experience and boost funnel conversion by providing a proactive solution for optimizing website performance. Many websites fail to meet Google core web vitals, which are essential for assessing overall user experience and influencing SEO rankings, but with this tool, you can monitor your site's performance and take measures to address low scores, ultimately increasing traffic and conversions.

New Relic's website performance monitoring tool offers a free and innovative solution for businesses looking to enhance their website's speed and reliability without complex engineering setups. It provides continuous tracking across multiple web pages, allowing users to proactively identify and resolve issues that can negatively impact revenue. The tool simplifies the process of monitoring by offering automated alerts for outages, broken links, and other performance issues, while also providing insights into improving user experience and SEO. Users can enter a URL to set up a dashboard for real-time performance metrics, including Google core web vitals, and receive recommendations for optimizing their site. With the option to upgrade for more extensive checks, New Relic's tool aims to improve customer experience and conversion rates by ensuring websites are fast and error-free, addressing the significant portion of sites that fail to meet critical performance standards.

In today's complex technological landscape, maintaining robust and reliable infrastructure is crucial for businesses to deliver seamless digital experiences to their customers. Root cause analysis (RCA) is a systematic approach to problem-solving that aims to identify and address the underlying causes of incidents or anomalies within an infrastructure. Infrastructure monitoring plays a pivotal role in supporting effective RCA by providing real-time visibility into the performance and health of infrastructure components. This includes collecting and visualizing data, generating alerts and anomaly detection, log management and correlation, integration with other monitoring tools, historical data analysis, and leveraging the right tools for RCA. To conduct an effective RCA, organizations should establish a standardized process, use appropriate tools, involve multiple stakeholders, document results, and continuously improve the process. By following these best practices and using infrastructure monitoring platforms like New Relic, businesses can maximize their infrastructure monitoring capabilities to support effective root cause analysis and prevent incidents from recurring.

Root cause analysis (RCA) is a systematic approach to identifying and resolving the underlying causes of incidents in complex infrastructure systems. Effective RCA involves understanding the importance of identifying root causes, utilizing infrastructure monitoring tools like the New Relic infrastructure agent, and following best practices such as establishing a standard RCA process, using appropriate tools, involving multiple stakeholders, and documenting results. Infrastructure monitoring supports RCA by providing real-time data collection, alerting, log management, integration with other tools, and historical data analysis, which collectively enhance system visibility and stability. Challenges in RCA, such as limited visibility and complex system dependencies, can be mitigated using comprehensive monitoring tools that offer advanced analytics and collaborative features. By leveraging these capabilities, organizations can minimize downtime, improve system performance, and foster a culture of continuous improvement and effective problem-solving.

This blog post provides tips and code examples for engineers using AWS to set up serverless instrumentation with New Relic, a monitoring tool. The example three-tiered application includes API Gateway, Lambda, and Amazon Relational Database Service (RDS). It offers guidance on instrumenting serverless functions and debugging strategies using Lambda layers or manual instrumentation in New Relic. Monitoring serverless applications is crucial for identifying and responding to issues, optimizing resource utilization, and improving performance. The step-by-step guide sets up the AWS integration, installs the New Relic AWS integration, configures the budget policy, and enables function logs. It also provides an example of how to instrument a Lambda function using the serverless framework and demonstrates how to troubleshoot common issues. With proper instrumentation, developers can gain better visibility into their serverless functions, identify performance issues, locate the source of errors, and optimize their function's performance.

The blog post discusses setting up serverless instrumentation for AWS applications using New Relic, focusing on enhancing visibility into serverless functions, essential for cloud-native customers. It guides engineers through using AWS services like API Gateway, Lambda, and Amazon RDS for a three-tiered application, providing tips and code examples for efficient monitoring. The post emphasizes the importance of monitoring serverless applications to optimize resource utilization, identify performance issues, and improve overall application performance. It offers a step-by-step guide on configuring New Relic serverless monitoring through AWS integrations, Metric Stream, and Lambda layers, highlighting the ease of instrumenting Lambda functions without code-level changes for supported languages. By following the guide, users can achieve better observability, detect anomalies, and ensure the reliability and scalability of their serverless applications.

As your applications grow in size and complexity, managing logs becomes increasingly challenging. Open source logging tools can help you manage your logs, whether you’re implementing a fully customized open source solution or combining open source tools with observability tools like New Relic. These tools enable the import, parsing, transformation, filtering, and export of log data, enhancing your observability practice. They also provide flexibility to structure logs, obfuscate sensitive data, and make logs more readable before sending them to New Relic. Many open source logging tools include plugins and other options for forwarding log data, but sometimes additional solutions are needed. To properly correlate and compare log data, a centralized log management solution is essential, which can be achieved by using open source logging tools that standardize and format your logs. The use cases for these tools include exporting and importing log data, centralizing log data, standardizing and structuring your logs, and obfuscating sensitive data. OpenTelemetry, Logstash, Fluent Bit, Fluentd, and Rsyslog are some of the top open source logging tools that can be integrated with New Relic to maximize observability and logging across your stack. These tools provide vendor-neutral solutions for collecting and sending log data to tools like New Relic, ensuring maximum flexibility and control over your log management practice.

Managing logs in increasingly complex applications can be challenging, prompting the use of open-source logging tools that can be combined with observability platforms like New Relic to enhance log management and observability. This blog post explores various top open-source logging tools like OpenTelemetry, Logstash, Fluent Bit, Fluentd, Rsyslog, Syslog-ng, Graylog, Nagios, and Grafana Loki, which facilitate tasks such as log data import, parsing, transformation, filtering, and exportation. These tools offer customization, flexibility, and scalability, allowing organizations to centralize, standardize, and structure their log data effectively. Moreover, they can obfuscate sensitive information and make logs more readable before being forwarded to New Relic. By integrating these tools with New Relic, users can achieve a comprehensive observability solution that supports automatic and custom instrumentation, thereby enabling better monitoring and analysis of application performance.

Modern observability (o11y) offers a more comprehensive understanding of system health and performance compared to traditional monitoring methods. It focuses on collecting and analyzing logs, traces, and events in real-time, providing proactive insights into system behavior and potential issues. By adopting modern o11y, businesses can enhance productivity, reduce costs, and mitigate risks, fostering operational excellence. The shift to o11y requires a new perspective, prioritizing user experience and measuring what matters - the experience of people using the service. To implement modern o11y, organizations should add observability capabilities, integrate their tools, and simplify their inputs. This involves identifying missing capabilities, installing and training on new solutions, integrating data from existing monitoring tools, and removing redundant inputs to achieve peak observability.

Modern observability, often abbreviated as o11y, is a transformative approach that offers real-time insights into system health, surpassing traditional monitoring methods by integrating new techniques with existing ones for a balanced monitoring approach. This shift prioritizes user experience, enabling a more comprehensive understanding of system behavior through the collection and analysis of logs, traces, and events, rather than just metrics. Observability solutions allow systems to autonomously report their state, facilitating proactive issue identification and resolution, enhancing productivity, reducing costs, and mitigating risks. The transition to modern observability does not necessitate abandoning traditional monitoring tools; instead, it encourages a change in perspective, focusing on the customer experience while maintaining essential low-level data. This approach empowers businesses to efficiently manage system performance, ensuring operational excellence and informed decision-making regarding system updates and development.

Understanding log patterns is crucial for understanding application behavior and identifying potential issues. However, having too many logs can make it challenging to manage and find relevant information. The solution lies in breaking logs into individual fields and removing unnecessary attributes using appropriate log-matching techniques and drop filters. This allows you to focus on critical data and gain valuable insights quickly. Regular expressions (regex) are powerful tools for finding and matching text data patterns, making them a fast way to filter and analyze log data. Mastering regex can help you gain valuable insights into your application and infrastructure performance, troubleshoot issues, and make data-driven decisions to improve system health. By using the pattern attribute in New Relic infrastructure for client-side filtering and UI drop filters for server-side filtering, you can remove unnecessary attributes, focus on critical log data, and maximize the potential of New Relic for log analysis.

Understanding and managing log patterns is essential for analyzing application behavior and identifying issues efficiently. The text highlights techniques to break down logs into individual fields and use drop filters to eliminate unnecessary data, focusing on critical information to gain valuable insights. It emphasizes the use of regular expressions (regex) to filter and match text patterns, facilitating quick analysis of large log volumes. By employing both client-side filtering with the pattern attribute in New Relic infrastructure and server-side filtering using drop filters, users can enhance log quality and make informed decisions to improve system performance. The article provides practical guidance on using these techniques within New Relic to maximize the potential of log analysis, including setting up and configuring log sources, applying regex for pattern matching, and creating drop filters for unwanted data, ultimately improving the efficiency and effectiveness of log management.

As a DevOps detective, tracking down details about system issues is crucial. Logs can provide detailed information to reconstruct the incident, but they need to be configured for granularity and correlated with other telemetry data to detect and resolve issues efficiently. Correlated log data with New Relic logs in context enables faster detection and resolution of incidents by providing contextual information, allowing users to identify the root cause of problems more quickly. This leads to improved mean time to detection (MTTD) and mean time to resolution (MTTR), which are key performance indicators for stabilizing system availability and performance. By leveraging correlated log data with New Relic logs in context, organizations can minimize MTTD and MTTR, improve product reliability, and reduce downtime, ultimately enhancing the digital customer experience.

The blog post explores the importance of utilizing logs in context to enhance the efficiency of detecting and resolving system incidents, particularly through New Relic's capabilities. It explains the significance of mean time to detection (MTTD) and mean time to resolution (MTTR) as key performance indicators for system reliability and uptime, emphasizing how correlated log data can reduce these times by providing contextual information that links logs with other telemetry data. By integrating logs with performance metrics, events, and traces, New Relic enables users to form a comprehensive view of their technology stack, facilitating faster identification and resolution of issues. The post highlights the integration of New Relic's logs in context feature with various telemetry sources and discusses additional New Relic functionalities for managing log data, such as log parsing, obfuscation, and pattern recognition, which collectively aim to optimize system performance and enhance the digital customer experience.