This might be a bug. As you can see FR is already collecting data from one CF instance, not sure what this popup means.

0 connected clients

client? I do not know what that is.

I did a dumb thing and installed on-premise FR on a server that doesn't need it. What's the simplest and least destructive way to remove it? Alternatively, I could just leave it there unlicensed, but I'm not sure what or how serious the downsides are. It must consume "some" resources, I'd think. Thoughts anyone?

I'm not on an FR roll today it seems... On the server where I installed FR, the FRAM is running, and it discovered the CF instance it needs to monitor, but it's disconnected from it. • It couldn't restart it after the install • The instance manager says it's stopped but the site itself is working fine • The instance manager link says "This page isn’t working [that ip] didn’t send any data." I'm sure I've monkeyed something simple, but all I meant to do was run the full installer. If anyone has any ideas, they're welcome, else I'll keep digging into the various config pieces, and talk to support on Monday if I haven't gotten joy.

ln old versions of CF and FR, an exact match restriction of "/connector" (no quotes) worked to filter out FR's heartbeat requests. With CF 2021 and FR 8.8.0, that no longer works, I see tons of these:

<http://localhost/__cf_connector_heartbeat__>

I tried adding an exact match restriction like this:

__cf_connector_heartbeat__

, but it gets rejected, "The path you have entered is invalid, this will prevent restrictions from occurring. Press ok to continue or cancel to modify your request URL." Same happens without the leading and trailing underscores. EDIT: Using a regex of

cf_connector_heartbeat

also doesn't work, the heartbeat requests are still recorded. Same with

*cf_connector_heartbeat*

. What's the recommended approach?

This message was deleted.

I'm not sure what your asking. The plugs folder will by design will be empty and the UI will unpack in the OSGI directory. Everything behind /fusionreactor/ is dynamically loaded so it's not something you can just place in a path

On a new CF 2021 server we recently stood up to replace a much older version, FR is recording web requests, but doesn't seem to be recording 500s. I know some happened because we got the emails, but there's nothing in FR. Have I missed a config? If we caught the crashes, wouldn't they still show in FR? This is Revision: 8.8.0, Build: fusionreactor.10647.964d5a1e.8.8.0.

As discussed in a long thread on the #cfml-general channel, one of our CF servers (CF 2018) has an intermittent problem, where after some days, it starts throwing a lot of nonsense errors. In several recent specific cases, nothing was promoted up to production in the past week, so zero code changes, and mid-day we got a blast of these:

Element EXECUTIONMODE is undefined in THISTAG
Could not find the included template

The missing template error refers to a template that DOES exist and is used on lots of pages, and is also the one that throws the EXECUTIONMODE error. These are the same errors we've seen before. Clearing the template cache has fixed it, every time, but typically it comes back some days later. In the #cfml-general discussion, one hypothesis is that there's some sort of race condition or conflict between the background processes that compile, cache and execute CFML code. I wondered if FusionReactor has any visibility into those processes, or more generally, if you have any thoughts on what FR can tell us about the cause of these problems, or potential remediations. (As it stands, our standard error handling catches these errors, logs them, and sends email to devs, so they don't show up in FR at all. That's not what I'm asking about. I'm looking for info that can help us understand the compilation and caching mechanisms in CF, and determine if somewhere in there is what's breaking.) Any thoughts are welcome.

I'm using the CFWheels framework and for some reason FusionReactor isn't tracking the errors. However, you can see that it tracks errors for a vanilla CF app that I'm also running. Any idea how fix this? Do I need to install a plugin on CFWheels?

@Tim Badolato do you have an explicit error handler for your CFWheels app?

CFWheels has an

onError

handler built in

@davidtat Do I need to pass the error to FusionReactor in the

onError

method?

Within FusionReactor errors will be tracked when an exception is fired during a transaction or the response code is in the 5xx state. You can define what errors or status codes will be in the error settings. For any exceptions fired the stack trace will be captured in the transaction details. If you have the Ultimate or Developer editions of FusionReactor you will also have access to the event snapshots. Let me see if I can grab someone from support who can help you here

@channel In case anyone missed it - I just wanted to let everyone know that we've recently released FusionReactor 9.0. which represents a major milestone for FusionReactor and has been almost 2 years in the making. It adds a lot of new capability to the cloud platform, such as log monitoring, a new alerting engine and lots of new dashboards to help you analyze metrics more effectively. You can read the blog post here and download FusionReactor 9.0 here.

Howdy. Am trying to untangle some password craziness we have with our FusionReactor config we have in our Lucee container. We're setting a bunch of environment variables for the JVM FR uses, one of which is

fradminpassword

(https://docs.fusion-reactor.com/Configuration/FusionReactor-System-Properties/) Now I would have assumed that that is the admin password for the FR UI. But it's... not. That is set in

fusionreactor/conf/reactor.conf

. So what is that env var for?

I'd like to detect heavy load and dynamically enable rate limiter code (crafted out of some great (old) code by J Moberg/Arehart). (Can't use IIS request restrictions - not granular enough) I'm running lucee 5.3.10.., with IIS 3/4 times a week my servers get hammered for ~40mins by a pretty sketchy crawler of sorts (runs ~10 IPs (regularly changing IP, plus changes his user agent every call & is not cookie-less) out of AWS, hitting me with 50+ requests/s on complex/resource intensive pages. I see there's some fantastic 'Protection' features in FR to help manage the load, as well as the FRAPI. I will use the WebRequest quantity protection with queue strat, but ideally I would like to throttle the bad IPs, rather than just queue everything so that legit users don't have to wait behind all the garbage requests. Wondering what the best way to detect load is. Looking at the historic FR metrics from when my servers are facing high req/s - seems like the the earliest sign is a high running request count - say > 75. CPU and Memory are not maxed. I see FRAPI has getRunningRequests() - is that too expensive to call often to check load? Any better options? thanks!!

I am having trouble with Fusionreactor in a Lucee Docker container. The Lucee image is:

FROM lucee/lucee:5.3.10.97-nginx-tomcat9.0-jdk11-openjdk

In the Dockerfile I am copying the FR files into a folder fusionreactor.jar libfrjvmti_x64.so

COPY ./cms/fusionreactor /custom-libs/fusionreactor

And in setenv.sh I am setting the FR opts:

setenv.sh
# FusionReactor opts
FR_OPTS="$FR_OPTS-javaagent:/custom-libs/fusionreactor/fusionreactor.jar=name=cms,address=8088 -agentpath:/custom-libs/fusionreactor/libfrjvmti_x64.so -Dfrlicense=$FR_LICENSE -Dfrshutdownaction=remove -Dfrlicenseservice.leasetime.hint=10 -Dfrregisterhostname=$FR_SERVERNAME -Dfr.cloud.group=cms"

But when I access FR in my browser I get the message: Fusion Reactor Fusion Reactor is not ready please try again in a few seconds. Already waited more the 10 minutes, the message doesn't change. Any hint would be appreciated!

Can FR tell me any details about ColdFusion's template caching? We're running a fairly large 24x7 app on CF2018. Every so often, seemingly nonsense crashes start happening on a page that hasn't changed in a while, errors like

Element EXECUTIONMODE is undefined in THISTAG

and

Could not find the included template

on pages that have run many times for weeks without problems and haven't been modified since. Clearing the template cache from CF Admin fixes it, instantly, haven't run into a case where it didn't. Trusted cache and Save class files are both unchecked, and have been for a long time, and I cleared out the cache directory manually a while ago too. We're not dynamically writing pages to disk, or using the in-memory file system. It's mostly old- or semi-old-school code, cfms that call CFCs for data, business logic, and sometimes rendering, some common includes, the usual, straight-up ninja-free stuff. Clearing the template cache doesn't change the code but fixes the problem (until next time), which on the face of it seems to say the problem isn't our code, but some kind of foobar in the CFML engine itself. I've raised a ticket with Adobe, but without steps to reproduce it's hard for them to get any traction. How can I get FR to give me maximum details about the state of CF's template cache? I looked at every FR metric I could think of around the time of the last crash, didn't see any spikes or obviously bent stuff, but (hopefully) I just don't know what to look for. One theoretical possibility that matches the symptoms is that something is interrupting the caching process while it's writing, but I don't know how to get a handle on what might cause that. I don't even know why template caching is in play at all, when it seems to me shut off in cf admin. Any thoughts are most welcome. (The crashes I know about were caught by our error handling, so they don't show up in FR, but the crash dumps we capture just show specific errors like the ones above, nothing directly related to the template cache.)

How do I prevent FusionReactor from losing historical data after it's restarted?

When using Coldfusion Sessions, FusionReactor rarely ever shows any as destroyed. The created count just seems to climb infinitely. I do have a long session time, but if the website visitor is not logged in, I delete the session at the end of each request. Here's the code from onRequestEnd:

if(isNull(session.user.id)) {
    StructClear(session);
  }

Though doing this doesn't seem to end the session. Is this the official way or is there another way in Lucee to officially destroy the session in a way that FusionReactor would recognize?

I do this because I have a high traffic site, and creating a session for every single visitor was causing the server to crash due to high memory usage. This fixed it.

Version? What's your session timeout set to?

Lucee s Controller thread runs every minute and purges expired scopes

Is there a way to prevent some/all environment variables from being shown in the Server Information page? It contains sensitive values that are best not shown in an APM. Thanks in advance.

Is it normal to see static assets (js,css,svg) files showing in WebRequest Transaction History? I'm using Lucee 5.3, latest commandbox and Brad's fusionreactor extension. I'd say most of my configuration is mostly "out of the box".. apart from Transaction Naming/Grouping in server.json.

depends, if you have a webserver out front, it can be configured to serve the static assets

Big thank you to the FR guys for making some fixes to their debugger in 9.2. It's rock solid now and saving me a lot of time. Appreciate the fast turn around on the ticket.

Is there a video or a blog post that talks about how to use FR for debugging? Specifically how to add break points and then inspect variables at each breakpoint?