Skip to main content
I
ismaelo47306097
Participant
January 16, 2019
Question

Performance Monitoring Toolset Server Config howto

  • January 16, 2019
  • 1 reply
  • 2083 views

I'm trying to give it a go to the newly developed Performance Monitoring Toolset (PMT) for CF2018

We have CF2018 Standard in a Windows Environment.

I have installed PMT in a Windows VM that will be our Monitoring Server.

However after install no CF instance gets detected, even entering the CF server details (ip, port) doesnt work in order to get the CF instance detected by PMT.

We only have one application in that CF server and no J2EE

Any help on setting that monitoring toolset up will be most welcome.

Thanks in advance.

Just to give you some more info on steps I did follow and documentation I read first to try and setup this:

ColdFusion Help | Configure ColdFusion Performance Monitoring Toolset settings

ColdFusion Help | Auto-discovery of ColdFusion nodes and clusters

And this is as far as I get

This is the instance I want to monitor

Monitoring is not enabled how can I enable it? Is there some config changes required in the server first to allow detection?

From the documentation (and the options available in the Server Administration UI) I can't see any option.

    This topic has been closed for replies.

    1 reply

    D
    dreynaud
    Participant
    February 12, 2020

    We have the same problem. Any help ?

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    February 12, 2020

    Dreynaud, when you say "same", can you confirm first that you mean that you have the pmt installed on another server (vm or not)?

     

    To you both, the running the pmt must be able to "see" the cf server. So next, do make sure that any firewall on each server (and the network between them) does allow each to teach/talk to the other.

     

    You can use any of various tools to test that, like ping. As for telnet, you could try port 80. I don't think the pmt talks via another port but I'm not at a computer to test. But let us know first what you find as for any general firewall block.

     

    Finally, as for that page in the cf admin, it merely confirms IF a pmt (anywhere) is monitoring that instance. It's one way, passive. You don't use it to POINT to a pmt, or to ENABLE that instance to BE monitored by one.

     

    There are some additional diagnostics we can discuss and consider further, if needed. It all can be rather confusing and frustrating. Also, certain key Adobe folks have chimed in on pmt questions, offering helpful specifics that go beyond the documentation, which is quite substantial as it is. 

    /Charlie (troubleshooter, carehart. org)
    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    October 14, 2020

    Indeed, alano5550924

    We made sure all the servers concerned were in the same private network, and shared access.


    I'm glad to see this post (from early 2020) getting attention again. And I see that alano5550924 proposed two things for folks to consider: a set of hosts file entries, and an AWS Security group.

     

    For those not on AWS, let's make things more generic--and this is new info since I last replied here in Feb 2020, the day ismaelo created the question and dreynaud also had chimed in. Notice how it is the 9250 port that is being opened up, as well as the suggestion about 9101. That's indeed about the elasticSearch (es) datastore (ds), which the PMT uses. And it turns out that the CF instance needs to be able to reach THAT! (And if you want the "auto-discovery" feature of the PMT to work, the port used for that by CF and the PMT is 46864, by default.)

     

    We would all reasonably presume that the comms are between CF and the PMT, and the PMT and ES. But it's also between CF and the ES, which most would NOT expect. So yes, the port for ES needs to be open to the CF instance (even though you are configuring things in the PMT, rather than in CF itself, and that's where the error appears). And in fact that error in dreynaud's last comment that day did show that was the issue.

     

    And dreynaud had in fact said that day, "Were cannot understant why PMT cannot communicate with ElasticSearch ! Both are on the same compûter AAA.x". Again, that was NOT the problem, it was that CF and the ES could not communicate.

     

    FWIW, Adobe did a webinar on the topic, which folks setting up the PMT will find fascinating, I think.  It includes also some config file changes that one may need to make if they made some wrong choices initially. See this post about the video, which anyone can register to view:

    https://community.adobe.com/t5/coldfusion/a-bird-s-eye-view-of-pmt-architecture-and-how-to-harness-its-true-potential/td-p/11300105?page=1

     

    It would be wonderful if the info in that video were translated into the docs about the PMT, which start here:

     

    https://helpx.adobe.com/coldfusion/user-guide.html?topic=/coldfusion/morehelp/pmt.ug.js

     

    Instead, most of what is shared in the video is NOT documented there, nor in that post itself, which is a shame. I am planning to do some posts on it, but of course anyone is welcome to if they want to give it a shot.

     

    If either ismaelo or dreynaud sees this and has success with it (or with alano's comment), I hope you'll let us know, or if anyone else who finds this does. The more info shared, the better.

    /Charlie (troubleshooter, carehart. org)
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices