# Getting Appdynamics Data into ELK

**URL:** <https://discuss.elastic.co/t/getting-appdynamics-data-into-elk/245905>\
**Category:** Logstash\
**Created:** [August 21, 2020, 10:22am UTC](https://discuss.elastic.co/t/getting-appdynamics-data-into-elk/245905 "2020-08-21T10:22:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sriram28](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sriram28/32/56590_2.png) [@sriram28](https://discuss.elastic.co/u/sriram28)\
**Post date:** [August 21, 2020, 10:22am UTC](https://discuss.elastic.co/t/getting-appdynamics-data-into-elk/245905/1 "2020-08-21T10:22:47Z")

</div>

Hi All,  
Need your help.  
I am trying to get Appdynamics Data into Logstash . I am getting connect time out when trying to connect from logstash to appdynamics .

## +++++++++++++ t http\_request\_failure.error connect timed out

t http\_request\_failure.name urlname  
t http\_request\_failure.request.method get

+++++++++++++++++++++++

I am able to get the output for the URL in Postman.

Config file:

input {  
http\_poller {  
urls =\> {  
urlname =\> "[https://xyz.saas.appdynamics.com/controller/rest/applications/MCC%20Publish%20APP%20Prod%20-%20EU/metric-data?metric-path=Business%20Transaction%20Performance|Business%20Transactions|\*|\*|Average%20Response%20Time%20(ms)&time-range-type=BEFORE\_NOW&duration-in-mins=60](https://xyz.saas.appdynamics.com/controller/rest/applications/MCC%20Publish%20APP%20Prod%20-%20EU/metric-data?metric-path=Business%20Transaction%20Performance%7CBusiness%20Transactions%7C*%7C*%7CAverage%20Response%20Time%20%28ms%29&time-range-type=BEFORE_NOW&duration-in-mins=60)"  
}  
request\_timeout =\> 300  
user =\> "_**"  
password =\> "**_"  
schedule =\> { cron =\> "\* \* \* \* \*"}  
codec =\> "json"  
metadata\_target =\> "http\_poller\_metadata"  
}  
}  
filter  
{  
mutate { gsub =\> ["message", "\< ", "\<"] }  
mutate { gsub =\> ["message", "/ ", "/"] }  
xml {  
source =\> "message"  
store\_xml =\> true  
target =\> "theXML"  
force\_array =\> false  
}  
}  
output {  
elasticsearch {  
hosts =\> ["https:\*\*\*\*\*\*\*\*:9200"]  
ssl =\> false  
cacert =\> '/etc/logstash/ssl/cl-root.crt'  
manage\_template =\> false  
index =\> "appdynamics-1-%{+YYYY.ww}"  
}  
}

++++++++++  
From proxy side I have the following settings.

http\_proxy="[http://xyz.net:83](http://xyz.net:83)"  
https\_proxy="[http://xyz.net:83](http://xyz.net:83)"

When doing curl I am getting following output:

curl -k [https://xyz.saas.appdynamics.com/controller/rest/applications/MCC%20Publish%20APP%20Prod%20-%20EU/metric-data?metric-path=Business%20Transaction%20Performance|Business%20Transactions](https://xyz.saas.appdynamics.com/controller/rest/applications/MCC%20Publish%20APP%20Prod%20-%20EU/metric-data?metric-path=Business%20Transaction%20Performance%7CBusiness%20Transactions) -u \*\*\*\*\*\*\* -vvv  
Enter host password for user '\*\*\*\*\*\*':

- Trying 10.244.1.3...
- TCP\_NODELAY set
- Connected to [xyz.net](http://xyz.net) (10.244.1.3) port 83 (#0)
- allocate connect buffer!
- Establish HTTP proxy tunnel to [xyz.saas.appdynamics.com:443](http://xyz.saas.appdynamics.com:443)
- Server auth using Basic with user '\*\*\*\*\*\*\*\*'

> CONNECT [xyz.saas.appdynamics.com:443](http://xyz.saas.appdynamics.com:443) HTTP/1.1  
> Host: [xyz.saas.appdynamics.com:443](http://xyz.saas.appdynamics.com:443)  
> User-Agent: curl/7.58.0  
> Proxy-Connection: Keep-Alive

\< HTTP/1.1 200 Connection established  
\<

- Proxy replied 200 to CONNECT request
- CONNECT phase completed!
- ALPN, offering h2
- ALPN, offering http/1.1
- successfully set certificate verify locations:
- CAfile: /etc/ssl/certs/ca-certificates.crt  
CApath: /etc/ssl/certs
- TLSv1.3 (OUT), TLS handshake, Client hello (1):
- CONNECT phase completed!
- CONNECT phase completed!
- TLSv1.3 (IN), TLS handshake, Server hello (2):
- TLSv1.2 (IN), TLS handshake, Certificate (11):
- TLSv1.2 (IN), TLS handshake, Server key exchange (12):
- TLSv1.2 (IN), TLS handshake, Server finished (14):
- TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
- TLSv1.2 (OUT), TLS change cipher, Client hello (1):
- TLSv1.2 (OUT), TLS handshake, Finished (20):
- TLSv1.2 (IN), TLS handshake, Finished (20):
- SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
- ALPN, server did not agree to a protocol
- Server certificate:
- subject: C=US; ST=California; L=San Francisco; O=AppDynamics LLC; CN=\*.saas.appdynamics.com
- start date: Jun 30 00:00:00 2020 GMT
- expire date: Sep 8 12:00:00 2021 GMT
- issuer: C=US; O=DigiCert Inc; CN=DigiCert SHA2 Secure Server CA
- SSL certificate verify ok.
- Server auth using Basic with user '\*\*\*\*\*\*\*'

> GET /controller/rest/applications/MCC%20Publish%20APP%20Prod%20-%20EU/metric-data?metric-path=Business%20Transaction%20Performance%7CBusiness%20Transactions HTTP/1.1  
> Host: [xyz.saas.appdynamics.com](http://xyz.saas.appdynamics.com)  
> Authorization: Basic c2l5ZXJAdm9sdm9jYXJzOnZvbHZvQDEyMw==  
> User-Agent: curl/7.58.0  
> Accept: _/_

\< HTTP/1.1 400 Time range type is not specified  
\< Content-Language:  
\< Content-Type: text/html  
\< Date: Fri, 21 Aug 2020 10:01:54 GMT  
\< Server: AppDynamics  
\< Set-Cookie: JSESSIONID=077b662105ffb6cf22217d6f7f1f; Path=/controller; HttpOnly; Secure  
\< X-Content-Type-Options: Nosniff  
\< X-Frame-Options: SAMEORIGIN  
\< X-XSS-Protection: 1; mode=block  
\< Content-Length: 1085  
\< Connection: keep-alive  
\<

AppDynamics - Error report 
# HTTP Status 400 - Time range type is not specified

* * *

**type** Status report

**message** Time range type is not specified

**description** The request sent by the client was syntac\* Connection #0 to host xyz.net left intact

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 18, 2020, 10:22am UTC](https://discuss.elastic.co/t/getting-appdynamics-data-into-elk/245905/2 "2020-09-18T10:22:57Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.