In the Splunk app, the exception message column has multiple line message in it. However, when same query is applied to the table event in the Splunk Dashboard Studio, the newline isn't considered, and message is read continuously.
Below is the Splunk app result.
Below is the table shown in the Studio.
Below is the Splunk Query.
index="eqt-e2e"
| spath suite_build_name | search suite_build_name="PAAS-InstantInk-Stage-Regression-Smooth-Transition"
| spath unit_test_name_failed{} output=unit_test_name_failed
| mvexpand unit_test_name_failed
| spath input=unit_test_name_failed
| where message!="Test was skipped"
| spath suite_build_number | search suite_build_number="*"
| where (if("*"="*", 1=1, like(author, "%*%")))
| where (if("*"="*", 1=1, like(message, "%*%")))
| spath suite_build_start_time
| sort - suite_build_start_time
| eval suite_build_time = strftime(strptime(suite_build_start_time, "%Y-%m-%d %H:%M:%S"), "%I:%M %p")
| table suite_build_name, suite_build_number, suite_build_time, author, test_rail_name, message
| rename suite_build_name AS "Pipeline Name", suite_build_number AS "Pipeline No.", suite_build_time AS "Pipline StartTime (UTC)", author AS "Test Author", test_rail_name AS "Test Name", message AS "Exception Message"
The solution to this (like a lot of issues with Studio) is to use Classic SimpleXML dashboards (until Studio catches up with all the missing functionality of Classic)! (Or try and forget what Classic can do and live with the limitations of Studio!) 😎 You could also raise a support case with Splunk identifying the problem so it can be added to the (long) list of outstanding deficiencies!
Apologies @ITWhisperer, will remember it!😅😅
I just tried to create table in the classic dashboard, and here the new line is shown.
The solution to this (like a lot of issues with Studio) is to use Classic SimpleXML dashboards (until Studio catches up with all the missing functionality of Classic)! (Or try and forget what Classic can do and live with the limitations of Studio!) 😎 You could also raise a support case with Splunk identifying the problem so it can be added to the (long) list of outstanding deficiencies!
@vinodkumarK Please do not tag / mention me in your posts - I, like many people here, am a volunteer, and, as such I can choose which posts to comment on. I do not appreciate having demands made on my time. I tend to prioritise which posts I answer. Given that this is a Dashboard Studio question, my first response would be, does it also happen in Classic / SimpleXML dashboards?