# Elastic Agent TLS Metadata

**URL:** <https://discuss.elastic.co/t/elastic-agent-tls-metadata/370133>\
**Category:** Elastic Agent\
**Created:** [November 6, 2024, 3:17pm UTC](https://discuss.elastic.co/t/elastic-agent-tls-metadata/370133 "2024-11-06T15:17:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![axvfvv79zcx57xv7k](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@axvfvv79zcx57xv7k](https://discuss.elastic.co/u/axvfvv79zcx57xv7k)\
**Post date:** [November 6, 2024, 3:17pm UTC](https://discuss.elastic.co/t/elastic-agent-tls-metadata/370133/1 "2024-11-06T15:17:14Z")

</div>

Hello Elastic Community,

I'm currently transitioning from a Logstash-based pipeline to the Elastic Agent for managing our data collection and monitoring. However, I've run into an issue with capturing TLS metadata (such as the Common Name (CN), cipher suite, protocol version, and client IP) for the connections made by Elastic Agents to the Fleet Server or Elasticsearch. This was previously possible with Logstash, but I haven't found an equivalent method in the Elastic Agent.  
In my previous setup with Logstash i was able to extract metadata TLS metadata from incoming connection using

```auto
ssl_peer_metadata => true

```

Is there currently a way to capture TLS metadata from the Elastic Agent input without using logstash?  
Thank you in advance for your help!