Effortless integration and enhanced visibility with OpenTelemetry in Blazor WebAssembly Challenges in observing WebAssembly applications Observing WebAssembly applications presents unique challenges that stem from its design and execution environment. Unlike traditional web applications, where monitoring tools can hook directly into JavaScript and the Document Object Model (DOM), WebAssembly runs as binary code executed within the browser’s sandbox. This layer of abstraction complicates direct introspection, as traditional monitoring tools are not designed to interact with the lower-level operations of WebAssembly.

Streamlining Container Log Management for Clarity and Control Hello, New Relic aficionados! Picture this: you’re at a bustling local user group meetup, exchanging ideas and sharing tech stories. Amidst the animated discussions and clinking coffee cups, a fellow developer—let’s call him Alex—shares a frustrating puzzle. Alex’s Docker Compose applications are acting like rebellious teenagers, sending their logs to the New Relic Host UI instead of their designated New Relic Container UI.

Empowering Developers with Real-Time Security Insights and Proactive Vulnerability Management Amidst the ever-evolving landscape of cybersecurity, the recent revelation of a zero-day vulnerability in Fortinet’s FortiOS serves as a stark reminder of the constant cat-and-mouse game between defenders and attackers. Staying ahead of potential security threats isn’t just a best practice; it’s a necessity. For developers, the challenge lies not only in identifying vulnerabilities but in doing so proactively, especially when it comes to zero-day exploits.

Learn how to collect all the telemetry from the .NET Aspire eShop application and send it to an OpenTelemetry backend such as New Relic .NET Aspire is the new kid on the block when it comes to an opinionated, cloud-ready stack for building observable, production-ready, distributed applications. Having a built-in dashboard for the monitoring data is nice during development. But how do you configure OpenTelemetry correctly to send it to an observability backend?

A practical guide to Active Directory Federation Services for a resilient Microsoft 365 ecosystem In our previous blog on how to monitor Microsoft 365 (M365), we delved into service overviews and the critical importance of synthetic user login monitoring. In this blog, we set our sights on a core component that forms the backbone of secure identity and access management: Active Directory Federation Services (AD FS). As organizations increasingly migrate their operations to the cloud, ensuring the robustness of identity and authentication mechanisms becomes paramount.

Your adventure in the world of observability, performance optimization, and security begins here. In the fast-paced world of software development, the quest for smoother, more efficient applications feels like a never-ending adventure. But in this adventure, it’s not about slaying dragons or uncovering hidden treasures; it’s about ensuring your code performs seamlessly and your users are happy. As a developer, I’ve faced the challenges of reactive observability, where we typically identify and resolve issues only after they’ve disrupted our applications.

One of the most popular and widely adopted business tool suites is Microsoft 365 (previously known as Microsoft Office 365) or just M365 for short. M365 offers a comprehensive array of applications and services, including email, document collaboration, video conferencing, and more, all hosted on the cloud. M365 provides numerous benefits in terms of flexibility and accessibility, but it also introduces new security, performance, and compliance challenges. This is why monitoring M365 applications is critically important for organizations of all sizes.

Enabling a true “shift-left” in software security by empowering DevOps and security teams to work together In some recent articles I shared how you as a developer can add security to your skillset by using New Relic capabilities. I also dug deeper into ways on how to mitigate hidden security risks of open source software libraries. Both of these blogs focused on third-party code and how it can impact the security of your software applications.

Check your source code for any vulnerable libraries and start mitigating these issues Open source software libraries have become an integral part of modern software development. They are widely used by developers to accelerate the development process and reduce costs. On average, open source libraries make up 70-90% of an entire software application. However, the use of open source libraries also comes with hidden security risks that could potentially harm your organization’s reputation and financial well-being.

Not every developer is a security expert, but use these tips to improve your skills In today’s digital age, security is a major concern for individuals and organizations alike. With the increasing number of cyber-attacks and data breaches, it’s crucial for developers to have a thorough understanding of security best practices. The security of an application is of the utmost importance, as it can directly impact the safety and privacy of users’ data.

In a recent post I wrote about the ability to send all your application security vulnerabilities found by Snyk directly to your New Relic observability platform. Now, New Relic made it even easier to achieve that by providing a dedicated security ingest processor that ‘understands’ the payload from a Snyk webhook. All the details on how to get started, create and configure a Snyk webhook to send into your New Relic account is provided in this docs page: https://docs.

Security and observability data go hand in hand when it comes to application health. If you can put those two sources of data behind a single pane of glass you can make your life a lot easier. By leveraging the different options that the Snyk platform provides, you can send all your application security vulnerabilities found by Snyk directly to your New Relic observability platform. Let’s see how! Prerequisites Here are all the necessary links to get started:

I am working with a global enterprise on rolling out the entire New Relic platform capabilities across their organization. The technical teams are happy and very confident in using the New Relic One platform. They have pretty much all the information they need and get all the way from high-level overviews of their entire stack down to code-level views. However, for management and executive leadership it is hard to get an overview themselves.

How-To: Set-up New Relic to collect and observe metrics, traces and logs from Dapr and the underlying applications. Enable Dapr metrics and logs with New Relic Kubernetes integration for Azure Kubernetes Service (AKS) and application traces using OpenTelemetry. Prerequisites Azure Kubernetes Service kubectl An installation of Dapr on Kubernetes Perpetually free New Relic account, 100 GB/month of free data ingest, 1 free full access user, unlimited free basic users Enable New Relic Kubernetes integration The Kubernetes integration monitors worker nodes.

As a fun project in some spare time, I recently worked on a way to tell Amazon Alexa how to talk to New Relic Insights and retrieve some high-level information about an account. I was just curious on what it would take to get Alexa to access our Insights API with a voice command and Alexa to speak out some result of this query. You typically start by creating an Amazon developer account and register a new Alexa Skill with the Alexa Skills Kit.

One of the things I am very interested in is the .NET stack and especially the .NET Core platform. In this blog post I want to briefly highlight what it takes to get a sample .NET Core application up and running on Azure and how to use New Relic’s Application Performance Monitoring (APM) to monitor this application. Please note: while I am writing this, the latest version of .NET Core SDK is .

Last week, we had the chance to present at a local Cloud Foundry Meetup in Stuttgart/Germany and the key topic was around IBM BlueMix (BM). My idea was to show and demo something around New Relic and BM. Due to my ignorance, I actually did not know that IBM BM is also based upon the open source platform Cloud Foundry (CF). Interestingly enough, I was involved in quite some CF engagements in my previous life and so I knew what it would take to get a so-called Spring-Boot type application (https://projects.