# No Data streams

**URL:** <https://discuss.elastic.co/t/no-data-streams/344985>\
**Category:** Kibana\
**Tags:** datastreams\
**Created:** [October 13, 2023, 10:26am UTC](https://discuss.elastic.co/t/no-data-streams/344985 "2023-10-13T10:26:03Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jean-Claude](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jean-claude/32/7732_2.png) [@Jean-Claude](https://discuss.elastic.co/u/Jean-Claude)\
**Post date:** [October 13, 2023, 10:26am UTC](https://discuss.elastic.co/t/no-data-streams/344985/1 "2023-10-13T10:26:03Z")

</div>

Hello, i hope you are doing well  
This my infra

ELASTIC

```auto
v-elkmaster01.sys.u-bordeaux.fr
v-elkmaster02.sys.u-bordeaux.fr
v-elkmaster03.sys.u-bordeaux.fr
p-elkhot01.sys.u-bordeaux.fr
p-elkhot02.sys.u-bordeaux.fr
p-elkwarm01.sys.u-bordeaux.fr

```

KIBANA

```auto
v-kibana01.sys.u-bordeaux.fr

```

FLEET

```auto
http://v-elkfleet01.sys.u-bordeaux.fr

```

has a public certificate

Elastic has self-signed certificate  
kibana has public cerficate

For Elasitic,kibana,and fleet all seem good

I add an agent policy with the integration HAProxy

I had 2 agents

all seems ok, the status is Healthy for all

But In the Data streams tab, there is "No data streams"

Did i miss something

Thanks in advance

Best Regards

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [October 13, 2023, 5:29pm UTC](https://discuss.elastic.co/t/no-data-streams/344985/2 "2023-10-13T17:29:44Z")

</div>

Hi @Jean-Claude Hope This Helps

> [@Jean-Claude](#):
>
> Elastic has self-signed certificate

Did you carefully read through this...

> **[Configure SSL/TLS for self-managed Fleet Servers | Fleet and Elastic Agent...](https://www.elastic.co/guide/en/fleet/current/secure-connections.html)**

If Elasticsearch is using a self-signed cert , then the Elastic Agents need that CA or [trusted fingerprint](https://www.elastic.co/guide/en/elasticsearch/reference/8.10/configuring-stack-security.html#_use_the_ca_fingerprint_5) because Agents send Data directly to Elasticsearch

See [Here](https://www.elastic.co/guide/en/fleet/current/secure-connections.html#_encrypt_traffic_between_elastic_agents_fleet_server_and_elasticsearch)

> To encrypt traffic between Elastic Agents, Fleet Server, and Elasticsearch:
> 
> 1. Configure Fleet settings. These settings are applied to all Fleet-managed Elastic Agents.
> 
> 2. In Kibana, open the main menu, then click **Management \> Fleet \> Settings**.
> 
> 3. Under **Fleet Server hosts** , specify the URLs Elastic Agents will use to connect to Fleet Server. For example, [https://192.0.2.1:8220](https://192.0.2.1:8220/), where 192.0.2.1 is the host IP where you will install Fleet Server.
> 
> For host settings, use the `https` protocol. DNS-based names are also allowed.
> 
> 1. Under **Outputs** , search for the default output, then click the **Edit** icon in the **Action** column.
> 2. In the **Hosts** field, specify the Elasticsearch URLs where Elastic Agents will send data. For example, [https://192.0.2.0:9200](https://192.0.2.0:9200/).
> 3. Specify either a CA certificate or CA fingerprint to connect securely Elasticsearch:  
> File path example:
> 
> - If you have a valid HEX encoded SHA-256 CA trusted fingerprint from root CA, specify it in the **Elasticsearch CA trusted fingerprint** field. To learn more, refer to the [Elasticsearch security documentation](https://www.elastic.co/guide/en/elasticsearch/reference/8.10/configuring-stack-security.html).
> - Otherwise, under **Advanced YAML configuration** , set `ssl.certificate_authorities` and specify the CA certificate to use to connect to Elasticsearch. You can specify a list of file paths (if the files are available), or embed a certificate directly in the YAML configuration. If you specify file paths, the certificates must be available on the hosts running the Elastic Agents.File path example:
> 
> `ssl.certificate_authorities: ["/path/to/your/elasticsearch-ca.crt"]`

Look at the diagram on [this](https://www.elastic.co/guide/en/fleet/current/fleet-server.html) page

 ![Screenshot 2023-10-13 at 10.22.46 AM](https://us1.discourse-cdn.com/elastic/original/3X/5/c/5cba20e98ddef11ceb68ce741f1d9dca2a55ba0d.png)

 ![Screenshot 2023-10-13 at 10.20.10 AM](https://us1.discourse-cdn.com/elastic/original/3X/4/f/4fad083b7270717ebeafd6328669d500c8786a2a.png)

Note: if you use the Advanced YAML configuration

`ssl.certificate_authorities: ["/path/to/your/elasticsearch-ca.crt"]`

That path / CA will need to be available and readable on all hosts you deploy the agent to.

---

<div class="post-metadata">

**Author:** ![Jean-Claude](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jean-claude/32/7732_2.png) [@Jean-Claude](https://discuss.elastic.co/u/Jean-Claude)\
**Post date:** [October 13, 2023, 7:24pm UTC](https://discuss.elastic.co/t/no-data-streams/344985/3 "2023-10-13T19:24:32Z")

</div>

Hello Stephen  
Thanks for the reply  
I did this, i used the trusted fingerprint  
With tcpdump i see that the agent send data to ```  
[v-elkmaster01.sys.u-bordeaux.fr](http://v-elkmaster01.sys.u-bordeaux.fr)

```auto
But there is no data in the Data stream
Regards
```

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [October 13, 2023, 9:10pm UTC](https://discuss.elastic.co/t/no-data-streams/344985/4 "2023-10-13T21:10:23Z")

</div>

Hi @Jean-Claude Not enough information for me to help.

What integration are you using?

Exactly which Data Streams are you expecting?

What Version ?

What do the agent logs show?

You are going to need to dig into the agent logs ...

Or log on to the host and troubleshoot the agent

> **[Troubleshoot common problems | Fleet and Elastic Agent Guide \[8.10\] | Elastic](https://www.elastic.co/guide/en/fleet/current/fleet-troubleshooting.html#_check_the_elastic_agent_status)**

---

<div class="post-metadata">

**Author:** ![Jean-Claude](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jean-claude/32/7732_2.png) [@Jean-Claude](https://discuss.elastic.co/u/Jean-Claude)\
**Post date:** [October 16, 2023, 2:10pm UTC](https://discuss.elastic.co/t/no-data-streams/344985/5 "2023-10-16T14:10:30Z")

</div>

Hello,  
Thanks for your reply  
the probleme is solved after adding ingest roles to elastic servers  
Best regards

---

<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:** [November 13, 2023, 2:11pm UTC](https://discuss.elastic.co/t/no-data-streams/344985/6 "2023-11-13T14:11:09Z")

</div>

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