CArehart.org

It's that time again: another new version of CF has come out (CF2018), and it's time for veteran CF troubleshooter and presenter Charlie Arehart to continue his tradition of identifying "hidden gems" in the new release, as he's been doing since CF4. Sure, most people can name a few of the big, new features in each release, while others will lament "there's not much new", when in fact there is! Just as in every release of CF, there are always lots of things that go unheralded and which may be just what you've been waiting for or that may delight you, whether solving a long-standing problem for you or providing a new technique, and whether related to coding, troubleshooting, administration, enterprise integration, and more. Charlie will also help identify edition differences, pricing, migration issues, etc., and as always where to find out more.

In the previous session of this series, we looked at the features of FusionReactor that generally make it easy to see why a request or transaction is slow, but we acknowledged that sometimes those features don't identify the reason. In this session we will look at a few of the features of FusionReactor that can be used to understand some less obvious reasons for slowness: - Stack tracing requests - Profiling requests - CPU sampler - Memory profiler As useful as these features can be, they do all require that FR be running at the time of the hangup. What can you do when you are not able to get to FR during a hangup? Or if you are looking at it after a restart? We will cover that in the final part of this series.

In the previous session of this series, we took a broad view at how FusionReactor can help you understanding what is or has been going on recently in your server/instance, especially in terms of request or transaction processing. In this session, we will delve into using aspects of FusionReactor to help understand WHY requests or transactions are running slowly. There are some aspects which stand out quite clearly to explain a slow request, if you know where to look. As such, we will cover FR features like: - Request details - JDBC processing within requests - Other monitored relations/transaction types within requests - JDBC history over all requests and applications (recent, slow, longest, and errors) That said, some problems will remain elusive, because they have to do with a request doing something that is not so clearly identified with these features. In part 3, we will move on to using features of FR that can be used in such cases.

In this session, the first of 4 parts, we will focus on using the key aspects of FR related to finding what is or had been going on recently in a given server/instance. And whereas some folks tend to presume that problems are due to resource issues like high use of memory or CPU constraints, often it's more important to step back first and look at the overall state of request and transaction processing, which may give real insight into the nature of problems (or indeed to confirm where there IS a problem, even when users or other monitors are reporting problems). As such, this session will focus on making the most of these key features in FusionReactor: - Web Metrics - Request history (recent, slow, and longest) - Requests error history - CPU, memory and garbage collection information There can be many explanations for WHY requests are slow or WHY resource usage is high. We will delve into additional features to better understand that in later parts of the series. In this first session, the goal is to get a clear understanding of the overall nature of problems, before diving into their causes.

Have you ever wondered if database performance issues were killing your web applications? Whether running CFML or Java apps (FR can monitor both), did you know that FusionReactor lets you view the JDBC activity for every request? You can see the SQL in queries (select, insert, update, delete, etc.) as well as stored procedure calls, and the arguments to either of those types. You can also see JDBC activity you may not code yourself, such as the SQL underlying ORM calls, or the client variable database processing in ColdFusion or Lucee. In this webinar, veteran troubleshooter Charlie Arehart will guide you through the various aspects of how FR can watch every query, including how such monitoring is filtered by default and can be configured to suit your needs. He'll show you the various places JDBC activity is tracked in the FR web interface (including powerful aggregation across and within applications), as well as how it is tracked in Crash Protection alert emails, and how such activity is tracked in the FR logs (on an aggregate basis per request, or even logging individual slow queries). You can even optionally have FR track the query plan created by your DB server for each query! Armed with such information, you can better understand either hangups or slowdowns that may be caused by database activity. And while FusionReactor has no insight into what's going on IN your database or database server, specifically, it can arm you with evidence of when it detects slowness, so that you can present more factual information to work with DBAs, if indeed it helps clarify that a problem is in fact in the database.

In this webinar you'll learn about what's new in FusionReactor 7 and 7.1. Did you know there were 20+ completely new core features and 100+ major improvements and bug fixes? Obviously we can't chronicle them all, but if you are either moving to the latest release of FR or have been running on it, you'll learn about many of the key benefits. Among the new features covered will be the new CPU and heap profiling, thread visualization, JMX metric monitoring, AWS cloudwatch integration, support for more frameworks, and more. Among the enhancements we will discuss are enhanced tracking of request errors and calls to external resources, improvements to the interactive step debugger, auto detection of datasource names, and more. FusionReactor 7 also marked the production release of FusionReactor Cloud, and we will conclude with a brief introduction to that (covered already in another full webinar earlier in 2017).

FuseGuard is a web application firewall for CFML applications. It runs onRequestStart to detect malicious requests which it can then log or block. In this presentation you will learn how to add FuseGuard to an existing application and then see how it blocks exploitation of several security vulnerabilities within the application.

Need more reasons to fall in love with the technology that has defined your career as a web developer? Then this is the session to attend. This session will walk you through the journey that ColdFusion has had so far as well as give you an insight into the strong future that ColdFusion has with data points to back every single claim made. So the next time anyone challenges you on the viability of ColdFusion as a technology, you will have all the answers you need to defend your favorite technology

In this presentation, we will show you the fundamental steps of getting the logs into Excel, and then we'll go further with several specific sorts of analysis which can be done against such log data via spreadsheets, the kinds of useful troubleshooting information we can obtain this way, and we will take time especially to leverage the unique value of pivot tables. You'll see how easy it is for you to use such spreadsheet features, by demonstration of the simple (but not always obvious) steps to follow. This is a follow-up to last month's webinar, "Making the Most of FusionReactor's Logs". In that one, we discussed the benefits of analyzing FR's logs (for post-mortem, trend, or spot troubleshooting), and we reviewed at a high level the many tools available to do such analysis. In this webinar, we will go deeper into using spreadsheet tools like Excel (though the concepts apply as well to OpenOffice Calc and Google Sheets).