topic Re: Splunk IT Service Intelligence: Why am I getting error "URI Too Large" when trying to enable drilldown options from Deep Dive swim lanes? in Splunk ITSI

Splunk IT Service Intelligence: Why am I getting error "URI Too Large" when trying to enable drilldown options from Deep Dive swim lanes?

svendby90 — Tue, 11 Oct 2016 20:28:32 GMT

I'm trying to configure some drilldown options from swim lanes in the Deep Dive view in the Splunk IT Service Intelligence app, but having some difficulties doing that. My goal is to be able to drill down to different dashboards from various lanes.

When enabling overlay for a KPI's swim lane and selecting that lane, I get an error (see picture). Checking the console, I find the following error message: "Failed to load resource: the server responded with a status of 414 (Request-URI Too Large)". Any ideas on how/where I can fix/set this?

Re: Splunk IT Service Intelligence: Why am I getting error "URI Too Large" when trying to enable drilldown options from Deep Dive swim lanes?

sanjayguptag — Wed, 12 Jul 2017 13:41:35 GMT

hey did you able to resolve it, how you reached till custom drill down. i also want to open the custom dashboard from deep dive but not sure how to open that?

Re: Splunk IT Service Intelligence: Why am I getting error "URI Too Large" when trying to enable drilldown options from Deep Dive swim lanes?

markconlin — Tue, 19 Dec 2017 21:06:26 GMT

No result found yet. Have you fixed your issue?

Re: Splunk IT Service Intelligence: Why am I getting error "URI Too Large" when trying to enable drilldown options from Deep Dive swim lanes?

svendby90 — Wed, 20 Dec 2017 07:52:23 GMT

Hi! No fix yet. I haven't been able to work on this since I posted the question. Will update if I figure it out 🙂

Re: Splunk IT Service Intelligence: Why am I getting error "URI Too Large" when trying to enable drilldown options from Deep Dive swim lanes?

svendby90 — Tue, 29 Sep 2020 17:20:32 GMT

After updating to 3.0 the problem seems to have been resolved. No idea what caused the error unfortunately.

For the record, in order to enable drilldown from deep dive you need to create a deep_dive_drilldowns.conf in /etc/apps/itsi/local. See /etc/apps/itsi/README/deep_dive_drilldowns.conf for options 🙂
When created run http://yoursplunkserver:8000/en-GB/debug/refresh to activate the configuration.

Re: Splunk IT Service Intelligence: Why am I getting error "URI Too Large" when trying to enable drilldown opt

evanchitger — Wed, 25 Nov 2020 06:36:27 GMT

Under Apache, the limit is a configurable value, LimitRequestLine. Change this value to something larger than its default of 8190 if you want to support a longer request URI. Extremely long URLs are usually a mistake. If you keep URLs under 2000 characters , they'll work in virtually any combination of client and server software. URI actually have a character limit depending on several things. Chrome limits url length of 2MB for practical reasons and to avoid causing denial-of-service problems in inter-process communication. On most platforms, Chrome's omnibox limits URL display to 32kB ( kMaxURLDisplayChars ) although a 1kB limit is used on VR platforms. IE - 2083 characters, Firefox - 2047 characters, Safari 80000 characters and Opera 190,000 characters.

To resolve the problem :

By POST request: Convert query string to json object and sent to API request with POST
By GET request: Max length of request is depend on sever side as well as client side. Most webserver have limit 8k which is configurable. On the client side the different browser has different limit. The browser IE and Safari limit to 2k, Opera 4k and Firefox 8k. means the max length for the GET request is 8k and min request length is 2k.

If exceed the request max length then the request truncated outside the limit by web server or browser without any warning. Some server truncated request data but the some server reject it because of data lose and they will return with response code 414.