# Logs are not showing from APM

**URL:** <https://discuss.elastic.co/t/logs-are-not-showing-from-apm/201049>\
**Category:** APM\
**Created:** [September 25, 2019, 1:41pm UTC](https://discuss.elastic.co/t/logs-are-not-showing-from-apm/201049 "2019-09-25T13:41:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mahendra.garg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mahendra.garg/32/53499_2.png) [@mahendra.garg](https://discuss.elastic.co/u/mahendra.garg)\
**Post date:** [September 25, 2019, 1:41pm UTC](https://discuss.elastic.co/t/logs-are-not-showing-from-apm/201049/1 "2019-09-25T13:41:37Z")

</div>

Hello Guys

I have configured the Kibana, APM, elasticsearch, For APM I have created a domain [https://example.com](https://example.com) as APM Agent in flask application, When I run the application on development environment logs are getting showing inside APM tab, but in production environment I'm not seeing any logs.

For Kibana  
server.host: "0.0.0.0"  
elasticsearch.hosts: [http://IP](http://IP):PORT  
elasticsearch.ssl.certificateAuthorities: ["ca.pem"]

For APM Server  
host: "0.0.0.0:8200"  
output.elasticsearch:  
hosts: ["[http://IP:9200](http://IP:9200)"]  
ssl.certificate\_authorities: ["ca.pem"]

For Elasticsearch  
network.host: IP  
discovery.seed\_hosts: ["IP"]

For Flask APM Agent:

```
current_app.config['ELASTIC_APM'] = {
        # Set required service name. Allowed characters:
        # a-z, A-Z, 0-9, -, _, and space
        'SERVICE_NAME': app_name,

        # Use if APM Server requires a token
        'SECRET_TOKEN': '',

        # Set custom APM Server URL (default: http://localhost:8200)
        'SERVER_URL': "https://example.com",
        'LOGGING': True,
        'DEBUG': True,
        'VERIFY_SERVER_CERT': False,
    }

    apm = ElasticAPM(current_app, logging=True)
    apm.init_app(current_app, service_name=app_name, secret_token='')

```

Please let me know where I need to make correction to make it work?

---

<div class="post-metadata">

**Author:** ![jalvz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jalvz/32/45613_2.png) [@jalvz](https://discuss.elastic.co/u/jalvz)\
**Post date:** [September 26, 2019, 10:35am UTC](https://discuss.elastic.co/t/logs-are-not-showing-from-apm/201049/2 "2019-09-26T10:35:59Z")

</div>

Hello,

What does `curl https://example.com/` says when executed from the machine where your Flask app runs?

---

<div class="post-metadata">

**Author:** ![mahendra.garg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mahendra.garg/32/53499_2.png) [@mahendra.garg](https://discuss.elastic.co/u/mahendra.garg)\
**Post date:** [September 26, 2019, 10:50am UTC](https://discuss.elastic.co/t/logs-are-not-showing-from-apm/201049/3 "2019-09-26T10:50:12Z")

</div>

curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none  
More details here: [http://curl.haxx.se/docs/sslcerts.html](http://curl.haxx.se/docs/sslcerts.html)

curl performs SSL certificate verification by default, using a "bundle"  
of Certificate Authority (CA) public keys (CA certs). If the default  
bundle file isn't adequate, you can specify an alternate file  
using the --cacert option.  
If this HTTPS server uses a certificate signed by a CA represented in  
the bundle, the certificate verification probably failed due to a  
problem with the certificate (it might be expired, or the name might  
not match the domain name in the URL).  
If you'd like to turn off curl's verification of the certificate, use  
the -k (or --insecure) option.

but it works fine with -k option.

---

<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:** [October 24, 2019, 10:50am UTC](https://discuss.elastic.co/t/logs-are-not-showing-from-apm/201049/4 "2019-10-24T10:50:13Z")

</div>

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