CURL - https not supported or disabled in libcurl

How to make curl work from command prompt. (I know APIKEY, will keep later). How to solve this protocol error?

D:\nr\platform_installer_win32>curl -X GET ‘https://api.newrelic.com/v2/applications.json’ \ -H “X-Api-Key:${APIKEY}” -i
curl: (1) Protocol “'https” not supported or disabled in libcurl
curl: (6) Could not resolve host: \

D:\nr\platform_installer_win32>curl -X GET ‘http://api.newrelic.com/v2/applications.json’ \ -H “X-Api-Key:${APIKEY}” -i
curl: (1) Protocol “'http” not supported or disabled in libcurl
curl: (6) Could not resolve host: \

D:\nr\platform_installer_win32>curl --version
curl 7.41.0 (i386-pc-win32) libcurl/7.41.0 OpenSSL/0.9.8zf zlib/1.2.8
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile SSPI Kerberos SPNEGO NTLM SSL libz

If you don’t already have a New Relic account, you can get full access for free

Hey @Praveen.Thatikonda

I believe the first warning you’re seeing is due to wrapping the url in single quotes instead of double.

Could you try this and tell me if it works for you?

D:\nr\platform_installer_win32>curl -X GET "https://api.newrelic.com/v2/applications.json" \ -H "X-Api-Key:${APIKEY}" -i

It is working. Thanks a lot. So, How can I add this output to my custom dashboard??

Hi @Praveen.Thatikonda - what kind of output are you wanting to add to a dashboard? And what sort of dashboard are you using - Insights Dashboards or standard custom dashboards?

I am using Insights dashboards. I would like display the summary data statistics bar (as explained in https://docs.newrelic.com/docs/apis/rest-api-v2/application-examples-v2/summary-data-examples-v2) in my dashboards.

It’s not possible to display the exact statistics from the summary data in an Insights or APM dashboard currently, but you can display the related metrics for recent time periods, either by using a metric chart (closer match, but requires at least a 30 minute timeframe) or an event-based query (allows a shorter timeframe, but may not match the metric as closely).

Which one would better suit your needs?