@coreyCLI, thank you for this. Adding "flex-basis" resolved the issue for me. ... View more

Here is the JS.  I gave the input id="user_name". require([ "splunkjs/mvc", "splunkjs/mvc/simplexml/ready!" ], function (mvc) { // get default token model var tokens = mvc.Components.getInstance("default"); var user_name = document.getElementById("user_name"); // Set required style if init value is undefined to channel if (tokens.get("user_name") === 'Enter a User') { user_name.classList.add("required"); } // Dropdown change on channel tokens.on("change:user_name", function (model, value) { if (value === 'Enter a User') { user_name.classList.add("required"); } else { user_name.classList.remove("required"); } }); });   Here is the CSS again just to capture it all in the same reply. .required button{ border: 2px solid #f6685e !important; }   I use this code (more or less) on other dashboards to perform the same "required" function on other inputs like drop downs and it works by creating a red outline around the drop down until a choice is made.   ... View more

Hi ! I am facing a very similar issue : after adding a new field to my KV store automatic lookup doesn't work and never returns my new field in my events but I can manually retrieve it with this query : | inputlookup my_kvstore but that one : index=my_index | lookup my_kvstore... throws an error : [comma separated of my indexers list] phase_0 - Streamed search execute failed because: Error in 'lookup' command: Cannot find the destination field 'my_new_field' in the lookup table 'my_kvstore'.. still, with this query : index=my_index | lookup local=true my_kvstore... I can retrieve my new field... Regards,   ... View more

Have you tried: splunk cmd mongod -version ... View more

I have no "unset" configured for that token so I don't believe so. ... View more

I don't know if you noticed but this thread is already 12 years old and the post you're asking about is 4 years old. You have better chance of getting a response by writing a new question (maybe pointing to this old thread for reference) instead of digging up such ancient history 😉 ... View more

Did you ever find a solution for this issue? ... View more

How did you fix this? I am currently experiencing the same error after adding a new search head to our cluster. ... View more

Please explain your use case.  Why would you want a broken (because macros are missing) search to complete successfully?  Wouldn't that run the risk of returning incorrect results? ... View more

Sounds good, thanks1 4.0.2 ... View more

Shortly, you could run rest towards all defined search peers. This is the reason why it works on MC. Basically you could add additional peers (like HFs, currently as indexers) and then get that information from them. ... View more

I had the same issue after copying a known working server.conf file (with encrypted pass4symmkey) to new peer, and once i had it on the new peer I updated the password (so that it wasnt encrypted) and saved.     BUT then i realized it was in "DOS" format, and I used vim command ":set ff=unix" and then saved.  Switching from DOS to UNIX file format is what mangled it so that it could no longer be used. To resolve, i opened server.conf and removed the encrypted pass4symmkey and replace it with the unencrypted value and restarted. ... View more

Thanks for the quick reply Jacob.  While that didnt work for our specific case I do appreciate the response.  In the end, and I am usure why TBH, this is whats currently in place and working for us to blacklist files that start with a dot (.) blacklist = \/dir\/dir\/syslog\/\.\S+ ... View more