Search: log-message

Introduction During process execution, a message (Log) for each step along the way is generated

and stop. User defined logs: These logs are generated by RPA Developer when using the activity Log Message

tell how important a log message is related to the execution of a process. Here are the logging levels

Logs

** == During process execution, a message (**Log**) for each step along the way is generated

using the activity [[Log Message>>doc:Activities.[1] Core Activities.Activities.Log Message.WebHome

tell how important a log message is related to the execution of a process. Here are the logging levels

RCA.Activities.Core.AddLogFields Description This activity allows you to add customized log fields to each and every Log Message. (* for Mandatory) Properties Input Fields (Collection of String)* - The collection of string arguments to be added from subsequent log lines. Misc Public

Add Log Fields

Add Log Fields

" %) ((( RCA.Activities.Core.AddLogFields == **Description** == This activity allows you to add customized log fields to each and every Log Message. [[image:image-20220513103428-1.png]] (* for Mandatory) == **Properties** == **Input** * **Fields (Collection of String)*** - The collection of string arguments to be added from subsequent log

{        port => 5044        type => "log"      }    }    filter {      json {        source => "message

="[140178115] Message Box" sap:VirtualizedContainerService.HintSize="313.6,59.2" sap2010

="[140178115] Message Box" sap:VirtualizedContainerService.HintSize="313.6,59.2" sap2010

the message was logged. The following options are available: OFF, FATAL, ERROR WARNING, INFORMATION, DEBUG AND VERBOSE. Message The logged message. This can also be a message logged through the Log Message activity

or Edit a task, Start or Stop a task, and display the logs generated by it with just a click of the button

at | |Level|The severity level at which the message was logged. The following options are available: **OFF, FATAL, ERROR WARNING, INFORMATION, DEBUG AND VERBOSE.** | |Message|The logged message. This can also be a message logged through the Log Message activity in Studio. == **b. Search a task** == akaBot Center

with a custom message and title that prompts a user to add application credentials, and store the username and password that can be later used to log into applications. (* for Mandatory) Properties Input Message (String)* - Message to show on the dialog box. E.g: “Credential for program is needed” Title (String

" %) ((( RCA.Activities.Core.RequestCredential == **Description** == The activity allows you to display a dialog box with a custom message

be later used to log into applications. [[image:image-20220505152134-1.png]] (* for Mandatory) == **Properties** == **Input** * **Message (String)*** - Message to show on the dialog box. E.g: “Credential

log to center. Supported methods: Post Parameters Name Type Description robotName String messages

), VERBOSE(6) jobId String False queryString String False Keyword to query from log message page Integer

://botcenter.akabot.io/api/logs/v1 URL Request: Headers: Response: True 24. GetLogs Get Log collections

to query from log message |page|Integer|False|Page number of the requested page |size|Integer|False|Size

="color:#000000" %)**23. PushLogs**(%%) == Push log to center. Supported methods: Post Parameters |Name|Type|Description |robotName|String| |messages|Array(String)| Response ReturnType: Bool Example

as Failed. Hover with the mouse cursor over the Failed state to view the error message. To check if a job was successfully executed, click the View job logs button. It will redirect you to Orchestrator, where all

as **Failed**. Hover with the mouse cursor over the **Failed** state to view the error message. To check if a job was successfully executed, click the **View job logs** button. It will redirect you

of the akaBot Agent in your environment. 3 ActiveMQ Service Messaging application that support the queue-related functions in akaBot Center. 4 ELK Stack Comprehensive log analysis solution that aids in deep searching, analyzing, and displaying logs produced by akaBot Centers. 5 Redis Cache In-memory data structure store used

Agent in your environment. |3|ActiveMQ Service|(% style="width:690px" %)Messaging application

log analysis solution that aids in deep searching, analyzing, and displaying logs produced by akaBot

, message broker, and streaming engine, allows for fewer database accesses, which helps to reduce the amount

to the Output panel2 (* for Mandatory) In the body of activity Text (String) * - The message you want

of this activity will be shown in the log. Be careful, consider data security before using it. Display Name (String

. E.g: Write Line Text (String) * - The message you want to show in the Output panel. Text Writer

) *** - The message you want to show in the Output panel. Accept both Text and String variables. E.g

)** - If you check it, the data of this activity will be shown in the log. Be careful, consider data security

of the activity to organize and structure your code better. E.g: Write Line * **Text (String) *** - The message

 - If selected, the values of variables and arguments will be logged at Verbose level. Output Result

contains the following fields: Command, Id, Status, Error Message. Only DataTable variables supported

of the activity. * **Public** - If selected, the values of variables and arguments will be logged at Verbose level

variable. The DataTable variable contains the following fields: Command, Id, Status, Error Message. Only