Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Rails 3 and above includes a powerful instrumentation system, ActiveSupport::Notifications, which can be used to track performance and event information for all aspects of your application. Notifications are light-weight, easy to setup, and can be consumed by multiple subscribers (logs, audit trails, consolidated metrics, other parts of your application). In this session we'll start with the basics of ActiveSupport::Notifications and work our way to powerful advanced use cases. Topics we'll explore include: How to set up and use notifications Logging what you want from any tier of your system How to capture and aggregate performance/business data for the metrics you care about most Conditional monitoring in production: flag on and off data by system or customer to get to the root of problems more quickly Using ActiveSupport::Notifications in non-Rails applications and your own libraries
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the video titled "Digging Deep with ActiveSupport::Notifications", Matt Sanders discusses the powerful instrumentation system introduced in Rails 3 known as ActiveSupport::Notifications. This system allows developers to track performance and event information efficiently both in development and production environments. The session covers the following key points: - **Introduction to ActiveSupport::Notifications**: Matt emphasizes how ActiveSupport provides modular functionalities, enabling developers to tap into Rails features even in non-Rails applications. - **Core Concepts**: - **Subscribers**: Components that listen for specific events. They are set up to react to messages with defined names that trigger notifications. - **Instrument Calls**: These trigger the events to be processed and allow for data to be passed along with notifications. - **Importance of Event Tracking**: ActiveSupport::Notifications aids developers in gaining visibility into their applications’ performance metrics, enabling timely diagnosis of issues during production rather than solely in development. - **Conditional Monitoring**: The ability to toggle data collection based on the system or customer context can hasten troubleshooting without affecting performance. - **Data Tracking and Metrics**: The session outlines how to capture key performance data such as response times and database access, which are crucial for optimizing application performance. - **Real-World Examples**: Matt uses case studies such as tracking slow requests, understanding the performance across different servers, and the database query timing to illustrate the practical application of ActiveSupport::Notifications. - **Advanced Use Cases**: The discussion also delves into the integration of this system with external monitoring tools like New Relic, as well as custom logging solutions. Sanders encourages the audience to utilize various logging techniques to enhance visibility. - **Usage Beyond Rails**: ActiveSupport::Notifications can be implemented in non-Rails applications, promoting its versatility across different Ruby frameworks. - **Conclusion and Best Practices**: Matt concludes by stressing the need to think strategically about what metrics are essential for business success, urging developers to leverage this system to improve the user experience. The main takeaway from this presentation is the significant enhancement in application monitoring and debugging capabilities provided by ActiveSupport::Notifications, which, when properly implemented, can lead to improved performance insights and user satisfaction.
Suggest modifications
Cancel