I don't know how to disable this message for my dashboard properly. I have added to a css style block within my dashboard .splunk-choice-input-message { visibility: hidden } This...
See more...
I don't know how to disable this message for my dashboard properly. I have added to a css style block within my dashboard .splunk-choice-input-message { visibility: hidden } This suppresses all of the text beneath all of the inputs in the dashboard which is fine as it's better than causing concern with the "Duplicate values causing conflict" message. So if anyone knows a way to manipulate the CSS to only suppress that message I'd be grateful. I don't have to allow duplicates in the dropdown and that in general it's probably a good hint but sometimes it just makes sense or so I think to ignore such warnings. I [mis]use the dropdown to also show a relative timeline of events in the order they appear in a an splunk event (which is comprised of many lines of text). The user can drill down to the specific log line within a splunk event that they they want to examine in detail. I also realise that I could solve this with condition on change and split the $value$ selected so that I get the id part without breaking the built in idea of duplicates being bad.. I don't know that I should have to do extra calculations just to achieve the simple idea. Data below is my justification and it works really well for the use case which actually has hundreds of lines in the combo box. | makeresults
| eval events="1147,Event A [1]
1066,Event B [2..3]
1147,Event A [4]
1156,Event C [5..8]
1147,Event A [9]
1073,Event D [10..14]
1050,Event E [15..20]
1073,Event D [21..40]
1156,Event C [41..44]
1050,Event E [45..46]
1147,Event A [47]
1090,Event F [48]
1678,Event G [49]
1090,Event F [50]
1180,Event H [51]
1127,Event I [52]
1097,Event J [53]
1127,Event I [54..55]
1180,Event H [56]
1068,Event K [57..60]
1138,Event L [61..63]
1122,Event M [64]"
| rex max_match=0 field=events "(?<event>.*)\n"
| table id event
| mvexpand event
| rex max_match=0 field=event "(?<id>.*),(?<event>.*)" It's true that the label in this case will be unique and the id will be duplicated. Yet it's the label that holds the human readable useful data and the id just refers to a lookup key to present.