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, a...
See more...
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" @ITWhisperer