Question
Standard chartered global business services
IN
Last activity: 6 Nov 2018 20:02 EST
Pega Robotics - Openspan Monitoring
We are trying to identify the following while openspan automation is running
1. Hand state(with or without errors)
2. Running State(with or without errors)
3. Stop state(with or without errors)
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
US
What are you trying to track the states of? What's your question?
Standard chartered global business services
IN
We are trying to track the health of the automation which is running i.e.we want to monitor the running/loaded automation by using diagnostic events/logs. The following is what we want to know
1) Automation stopped or running.
2) Automation hanging (neither running or stopped)
Pls note that the use case is RDA and not RPA i.e. automation running on desktops.
Updated: 19 Dec 2017 7:34 EST
Pegasystems Inc.
US
- Technically an Automation is always running (in a standby state) so there is not anything to indicate when one has started or stopped.
- There are no predefined indicators of an automation hanging.
You can add your own diagnostics into your automations by using the DiagnosticsLog component.
Standard chartered global business services
IN
Thanks a lot for your response.
1. Can you give us some pointers on how to add our own diagnostics using the DiagnosticsLog component.
2. We have tried enabling the Log4net publisher within our automation. We enable debug log level in RuntimeConfig.xml.. And we see some messages like "session completed" when the automation completes. We would like to listen to these kind of events without switching the log at debug level. Any thoughts?
3) We also see some "hbeat" kind of parameters in diagnostics. Can we use this ? Will this give what we want? Or is there any alternative to this?.
Pegasystems Inc.
US
You can write out to your own log file but I think the recommended route is to use the already existing logging. I would recommend using the FilePublisher (RuntimeLog.txt) and not Log4Net. With the component, you can specify the level of logging that you want the message to output as. There are 4 levels. If you edit the RuntimeConfig, you can do a Find/Replace for "3 to "4 to set it to verbose (highest logging) or keep it as default. You can experiment with it to see what information you want from it.
- Curious how to read logs?
- DiagnosticLogs?
Standard chartered global business services
IN
Thanks a lot for your response.
1. Can you give us some pointers on whether the session information can be obtained without using the Debug Mode.
2. Can you also let us know the impact of turning on DEBUG logs