# Metricsbeat sends bad request to kibana at /api/saved\_objects/\_find

**URL:** https://discuss.elastic.co/t/metricsbeat-sends-bad-request-to-kibana-at-api-saved-objects-find/357865
**Category:** Beats
**Tags:** metricbeat
**Created:** [April 21, 2024, 3:33pm UTC](https://discuss.elastic.co/t/metricsbeat-sends-bad-request-to-kibana-at-api-saved-objects-find/357865 "2024-04-21T15:33:51Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Moemad-711](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/moemad-711/32/133700_2.png) [@Moemad-711](https://discuss.elastic.co/u/Moemad-711)
#### Post date: [April 21, 2024, 3:33pm UTC](https://discuss.elastic.co/t/metricsbeat-sends-bad-request-to-kibana-at-api-saved-objects-find/357865/1 "2024-04-21T15:33:51Z")

</div>

I've setup elastic cloud for k8s on my cluster and I have deployed metricbeat using Beats CRD with daemonset

My Cluster is on version 8.13.0

Kibana's logs:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/7/872145b3eee572b27ea79f421a27200d9871ad0c.png)

Upon debugging I found these requests are coming from metricbeat pods on the endpoint kibana at /api/saved\_objects/\_find and is missing the query parameter "type" and it should like that /api/saved\_objects/\_find?type=index-pattern or another type

Is there a work around for this or a fix?

---

<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: [April 22, 2024, 1:12am UTC](https://discuss.elastic.co/t/metricsbeat-sends-bad-request-to-kibana-at-api-saved-objects-find/357865/2 "2024-04-22T01:12:30Z")

</div>

Hi @Moemad-711 Welcome to the community.

Known issue does not cause harm etc

> <https://github.com/elastic/elastic-agent-libs/issues/181>
>
> Our new KibanaIsServerless check causes hard to track down noise in the Kibana l…og in stateful environments.
> 
> From discuss: https://discuss.elastic.co/t/elasticsearch-output-of-filebeat-is-empty-displays-http-error-400-bad-request/352407
> 
> https://github.com/elastic/elastic-agent-libs/blob/473983911d7c78e57bf30af91f66f5bca50d0a59/kibana/client.go#L351-L359
> \`\`\`
> GET kbn:/api/saved\_objects/\_find
> {
> "statusCode": 400,
> "error": "Bad Request",
> "message": "\[request query.type\]: expected at least one defined value but got \[undefined\]"
> }
> \`\`\`
> 
> !\[image\](https://github.com/elastic/elastic-agent-libs/assets/6384545/341d2ec1-3051-45c4-80ff-f613986364ed)