# Reporting error / Bad Request

**URL:** <https://discuss.elastic.co/t/reporting-error-bad-request/166848>\
**Category:** Kibana\
**Tags:** elastic-stack-reporting\
**Created:** [February 3, 2019, 3:45am UTC](https://discuss.elastic.co/t/reporting-error-bad-request/166848 "2019-02-03T03:45:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [February 3, 2019, 3:45am UTC](https://discuss.elastic.co/t/reporting-error-bad-request/166848/1 "2019-02-03T03:45:11Z")

</div>

Hello World!

Kibana' user added (very long) `Elasticsearch Query DSL` (via `filter`), followed by `Share`-\>`Generate CSV` CSV report, yet error bellow was displayed at the bottom right corner.

> Reporting error
> 
> Bad Request

I've looked at both elasticsearch and kibana logs, however didn't see any errors in the logs...

How does one troubleshoot issue like this?

Please advise.

---

<div class="post-metadata">

**Author:** ![nickpeihl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickpeihl/32/112622_2.png) [@nickpeihl](https://discuss.elastic.co/u/nickpeihl)\
**Post date:** [February 4, 2019, 11:04pm UTC](https://discuss.elastic.co/t/reporting-error-bad-request/166848/2 "2019-02-04T23:04:29Z")

</div>

You may try increasing the verbosity of the Kibana logs by setting `logging.verbose: true` in kibana.yml.

If the Kibana logs are not helpful, maybe check the web browser's console log for errors.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [February 6, 2019, 12:32am UTC](https://discuss.elastic.co/t/reporting-error-bad-request/166848/3 "2019-02-06T00:32:44Z")

</div>

after configure `logging.verbose` to `true` seeing following error:

> Event is being forwarded: clientError

not sure how useful it is... via web browser console log:

```
POST https://URL net::ERR_CONNECTION_RESET
(anonymous) @ commons.bundle.js:3
Promise.then (async)
(anonymous) @ commons.bundle.js:3
step @ vendors.bundle.dll.js:524
(anonymous) @ vendors.bundle.dll.js:524
(anonymous) @ vendors.bundle.dll.js:524
__awaiter @ vendors.bundle.dll.js:524
kfetch @ commons.bundle.js:3
_callee$ @ commons.bundle.js:4
tryCatch @ vendors.bundle.dll.js:490
invoke @ vendors.bundle.dll.js:490
prototype.(anonymous function) @ vendors.bundle.dll.js:490
step @ commons.bundle.js:4
(anonymous) @ commons.bundle.js:4
(anonymous) @ commons.bundle.js:4
(anonymous) @ commons.bundle.js:4
ReportingPanelContentUi._this.createReportingJob @ commons.bundle.js:3
ka @ vendors.bundle.dll.js:212
invokeGuardedCallback @ vendors.bundle.dll.js:212
invokeGuardedCallbackAndCatchFirstError @ vendors.bundle.dll.js:212
Fa @ vendors.bundle.dll.js:212
Ja @ vendors.bundle.dll.js:212
La @ vendors.bundle.dll.js:212
Ha @ vendors.bundle.dll.js:212
Oa @ vendors.bundle.dll.js:212
Pa @ vendors.bundle.dll.js:212
Td @ vendors.bundle.dll.js:212
batchedUpdates @ vendors.bundle.dll.js:212
dc @ vendors.bundle.dll.js:212
Xd @ vendors.bundle.dll.js:212
interactiveUpdates @ vendors.bundle.dll.js:212
Wd @ vendors.bundle.dll.js:212
commons.bundle.js:3 Detected an unhandled Promise rejection.
TypeError: Cannot read property 'status' of undefined
commons.bundle.js:3 Uncaught (in promise) TypeError: Cannot read property 'status' of undefined
    at commons.bundle.js:3

```

I believe it has something to do with using very long query... possibly a bug?

---

<div class="post-metadata">

**Author:** ![nickpeihl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickpeihl/32/112622_2.png) [@nickpeihl](https://discuss.elastic.co/u/nickpeihl)\
**Post date:** [February 6, 2019, 7:06pm UTC](https://discuss.elastic.co/t/reporting-error-bad-request/166848/4 "2019-02-06T19:06:29Z")

</div>

Yeah, that could be a bug. You can file an issue for it in the [Kibana repo](https://github.com/elastic/kibana). The engineers will want to be able to recreate the error, so any information about your setup that you can share will help.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [February 6, 2019, 8:07pm UTC](https://discuss.elastic.co/t/reporting-error-bad-request/166848/5 "2019-02-06T20:07:54Z")

</div>

I believe it's fairly easy to reproduce, as our Query DSL consist of ~14k lines.

Kibana has `state:storeInSessionStorage` in `Advance Settings`, yet when URL passed to `Reporting` Kibana no longer is using that feature and URL becomes too long and I believe that's what is causing error...

---

<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:** [March 6, 2019, 8:08pm UTC](https://discuss.elastic.co/t/reporting-error-bad-request/166848/6 "2019-03-06T20:08:06Z")

</div>

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