AppD Archive

HTTP Metrics Listener - only listen to localhost?

CommunityUser
Splunk Employee
Splunk Employee

I'm working with custom metrics into AppDynamics. My application only really generates stats daily, so I figured I'd have it POST them to the HTTP metrics listener. I've enabled this with the -Dmetric.http.listener=true command line setting, but notice that it listens to localhost and the machine's IP address (and is thus accessible over the network).

is there a way of starting the listener only on localhost/127.0.0.1 so that it's not accessible via the network? Is there a metric.http.listener.host parameter or something?

EDIT

Oh wow - this is really, really necessary. I just realised that the doco says:

 

To shut down the machine agent

GET /machineagent/shutdown

That's a pretty major security problem - you can shut down all machine agents running the HTTP metrics listener just by sending an unauthenticated GET request that contains no secret information, remotely across the network. This means I absolutely can't use the HTTP listener unless I can limit it to localhost, and even then, it's a horrible security risk. I really hope there's a way to disable this shutdown 'feature'.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hello ,

Will be filling an enhnacement request for this . but as of now is it possible to run a custom script to report metric instead of using http listener ? 

please let me know if this can help http://docs.appdynamics.com/display/PRO12S/Add+Custom+Hardware+Monitors

0 Karma
Get Updates on the Splunk Community!

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

 Prepare to elevate your security operations with the powerful upgrade to Splunk Enterprise Security 8.x! This ...

Get Early Access to AI Playbook Authoring: Apply for the Alpha Private Preview ...

Passionate about security automation? Apply now to our AI Playbook Authoring Alpha private preview ...

Reduce and Transform Your Firewall Data with Splunk Data Management

Managing high-volume firewall data has always been a challenge. Noisy events and verbose traffic logs often ...