Splunk logs for Workflows
POPFORHTML-402 - Getting issue details... STATUS
Overview:
'Splunk Logs' is a feature in Popflow Studio wherein you can track logs such as exceptions and errors that occur for a specific workflow. These logs are retrieved from the Splunk Server. They are sent to Splunk whenever any error/exception occurs inside a Workflow.
What is Splunk?
Splunk is a software technology which provides the engine for monitoring, searching, analyzing, visualizing and acting on voluminous streams of real-time machine data. Its wide application and suitability make it a versatile technology. It captures, indexes, and correlates real-time data in a searchable repository from which it can generate graphs, reports, alerts, dashboards, and visualizations. Splunk is a horizontal technology used for application management, security and compliance, as well as business and web analytics.
How to view the logs?
You can open up any workflow designer and click the 'Logs' tab at the top right corner as highlighted in the below diagram. It will display a result consisting of various log details like 'Time', 'Message Type', 'Message', 'Details' and a 'Download' option to download a particular log to a text file.
The 'Page size' drop down allows you to set number of records you want to view in a single page. After selecting the page size, the number of pages and the number of records on each page is adjusted accordingly.
The 'Log Type' drop down allows you to view logs of a particular type. For example, you can only view 'Exceptions' or only view 'Errors'. By default, it is 'All Types' to view logs of all levels.
The 'Time frame' drop down allows you to select logs from a particular time frame. For example you can view logs that occurred in the last 15 minutes. By default, it is 'All Logs' to view all time logs for that workflow.
Additionally, to view more details of the log, you can use the 'Details' column and select a particular record. It will open a popup which contains more details like host, source, time, etc.
This document may contain confidential and/or privileged information belonging to OpenMethods. If you are not the intended recipient (or have received this document in error) please notify the sender immediately and destroy this document. Any unauthorized copying, disclosure, or distribution of the material in this document is strictly forbidden.