Is there are tool for exporting FusionReactor configs? I know you can copy the reactor.conf, but that doesn't handle all the plugin configurations. If I just parse the cmconfig/com/intergral/fusionreactor/plugin/ folder for files that end in .conf and migrate them to a new install, would that suffice?

In migrating from Apache/ACF to Nginx/Tomcat/Lucee, one of the changes we're seeing in FusionReactor is that URIs using path_info are not showing up in the URI in FR. In ACF, we'd see something like: https://www.acme.com/index.cfm/item/a09sada1234/ But now we're just seeing: https://www.acme.com/index.cfm Our requests end up containing a

xajp-path-info

header which contains the

/item/a09sada1234/

value, which I can dump out to the URL summary, but it's not as clean as having it be part of the URL. Is there a trick to get this working in FR?

I don't recall whether I did ask this before, or whether I meant to, and then never got around to it. Getting old. Anyhow, sorry if this is the second time I've asked. I do not know much about FR, other that the theoretics of how I'd expect it to work. Is it normal to have the FR application installed on the very production servers it is monitoring, or would be be more normal to have it running on its own server, and just somehow connecting to the JVM it's monitoring via the network? (in my situation read "container" for "server"). We are installing and running FR from within the Lucee container that is serving our Lucee application, which seems... odd... to me. I would expect the Lucee container to have Lucee running, and another container running FR, and FR to just be listening to the Lucee container's JVM. Or just have like an agent running in the Lucee container that the FR server talks to, or whatever.

@mflewittintergral A few days ago, for reasons that aren't clear to me, email notifications from FR on two CF2018 servers stopped. It turned out that for unknown reasons, FR didn't think it was licensed any more. Since fixing that, neither of those servers have been sending daily email notifications. Then today, both of them are sending repeated weekly notifications literally every minute. What should I do here? One is a pretty active production server, so I'd rather not restart CF, or the whole box. The other is dev/test, so I could, but that's a random jiggle-the-handle possible "cure". Any thoughts?

Hello, We have a FusionReactor license for 6 servers. On those servers we run multiple adobe coldfusion instances. We are in the process of transitioning to Lucee servers in combination with commandbox. The question is: can we do that with the same license. Multiple Lucee servers will be running on the same host machine.

Is it possible to get a second trial licence of 14 days. I want to use that to run some tests on my dev machine.

@bdw429s I've been seeing the

FusionReactor 8.8.0 is now available

message for a while now, but commandbox doesn't seem to be updating it. Is this a CB or FR issue?

Long time observer, first time user! I can't find an explanation to the following type of transaction in my Application, as seen by FR 1. See screenshot. The profile says the request took 20ms and was a 500 error. Yet there is no error output.

I have a question about the dashboard configuration. I have a lucee instance running with a configured password of

passwordX

. I have confugured that instance to start and run with commandbox. I can access that fusion-reactor instance at

<http://localhost:8088>

I register that instance at a windows installation of fusion-reactor with that url and password. That works fine. After I restart the lucee instance, the dashboard wil show a

pwd

on the instance icon. If I go to the instance URL I can log in with the configured password. I have to go to the server manager of the dashboard and edit the monitored instance and put in the same password and save the instance. Then monitoring is fine again... until the next restart. What is happening here? Why would the monitoring page lose access after a restart of the monitored instance?

wait, should there be two instances of FR running? one for each CF instance?

Does anyone know of any issues with FR, LDAP and custom SSL certificates? Brief summary, we deploy an image without FR all is good, we deploy with FR then we get

Caused by: javax.naming.CommunicationException: simple bind failed: {redacted}:636 [Root exception is <http://javax.net|javax.net>.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target],

which suggests it's not using/seeing the certificate?

@mflewittintergral Hello. Can I help some remote support? I would like to set it up on a second cf instance and get tips on how to get useful error output.

I already searched the docs and found nada.

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!!