Create a Script

Scripts can be written directly from a live editor or can be uploaded by dropping files over the Files & Scripts' creation window. The live editor will recognize the notation language (interpreter) once you name the script file and set an extension (e.g. Bash, Python, Perl, Node and bat files are recognized, but any script can be executed as long as the interpreter is available in the destination host.

TheEye will carry out the script execution over tasks. Check the tasks' documentation to find out how scripts are used.

You can also use a script to create a Monitor, please take a look at the monitors' documentation to see how scripts are used.

Writing Scripts

TheEye will use the output from your scripts to determine whether or not the execution was successful. The last line of the scripts will be parsed looking for a string which represents a state or a json result object. So it is mandatory to indicate the execution status when writing scripts.

A state could be any state or event linked to the task or monitor of this script. Default build-in events are success and failure.

So if you script ended as expected (success state), you will have to make it print "success" as the last output line of your script.

  • success, normal and ok are accepted success states.

  • failure and fail are accepted failure states.

Passing Arguments in Workflow.

There are different ways of passing arguments from monitor to task and from task to task.

Monitor to Task

In this case the state is always required or a failure will be assumed. There are two options to provide output:

  • The first option is to print a JSON formatted string with two properties: state and data. data must be an array with the arguments list that need to be provided to the next triggered task in the workflow. Each index of the array will be mapped in order to each argument of the triggered task.

# do your things here...
if [ true ]; then
echo { \"state\":\"success\", \"data\": [ \"val1\", \"val2\" ] }
echo { \"state\":\"failure\", \"data\": [ \"val1\", \"val2\" ] }
  • The second option is similar to the first one, but we use an object in the data property instead of an array. The difference is that the object will be passsed untouch as the firt argument of the next task.

# do your things here...
if [ true ]; then
echo { \"state\":\"success\", \"data\":{ \"val1\":$varTwo, \"val2\":$varUno } }
echo { \"state\":\"failure\" }

Task to Task

This scenario is the same as the previous, but as the state is not explicitly required and can be ignored, the output is quite more simple. In task the output state is always "success", unless a "failure" is provided to stop the workflow.

Output can be an array (each index will be mapped to each argument of the triggered task):

echo [\"arg1\",\"arg2\",\"arg3\"]

or an object (that will be the first argument of the triggered task):

echo { \"val1\": $varTwo, \"val2\": $varUno }


The only detected limitation so far is the size of the string used as output. Dependeding on the operating system, the output buffer varies. Be aware that if the string exceded the output buffer, some characters can be lost, a json error will be arise (due to parsing errors) and the output of the monitor/task will be a failure. This situation can be detected analizing the output of the monitor or task.


This is a simple check with success and failure states

# Some commands and checks here
# ...
# And at the end of the script...
if [ $check == true ]; then
echo "success"
echo "failure"
# or you can keep doing more things, you can control the flow of your script and end it anytime
echo "success"

If you need to report extra information to the API, you'll have to print the information to the stdout in json format like this

# This will output a valid JSON and will be parsed by TheEye agent
# Manually writing a JSON string is not quite pleasant, we know that and we will improve this in the future
if [ true ]; then
echo { \"state\":\"success\", \"data\":{ \"val1\":$varTwo, \"val2\":$varUno } }
echo { \"state\":\"failure\", \"data\":{ \"val1\":$varTwo, \"val2\":$varUno } }

The JSON output must have a state property with a the state value from your script execution, and a data property with any extra information you consider, TheEye will show the data value in the execution log.

If you need to validate the JSON output of your scripts, you can use this simple nodejs script - there are also nice web sites that can validate JSON for you too. Change it for your case


// test.js
var exec = require('child_process').exec;
exec('./', function(err, stdout, stderr){
var obj = JSON.parse(stdout);
// if the stdout string was parsed successfuly the next sentence will give the members number - which is 1
console.log( );

the script looks like this

# this is valid json when send to stdout
echo { \"state\" : \"$state\" , \"data\" : { \"members\" : $members } }
# this will echo { "state": "normal" , "data" : { "members": 1 } }

Scripts RunAs

Scripts run by default...

  • Linux: adding execution permission to the file and including the interpreter shebang in the first line.

  • Windows: setting the interpreter that should use the OS by the file extension.

Script RunAs allows to execute the script in a specific way, by using a different binary interpreter or in Linux using sudo. Remember that RunAs is part of the Tasks' configuration, as Tasks are responsible for Scripts' execution. Please check the Script Task Documentation section for further details.


The runas text could be any command line combination, using fixed variables, environment settings, command or anything that agent user(by default theeye-a) can do within the default shell (usually bash or cmd). We recommend to keep it simple and short. The only requirement is that the runas has to include the %script% KEYWORD. This KEYWORD indicates which part of the runas text will be replaced with the script path and its arguments.

In Linux


To run the script using sudo, use one of the following runas syntax


sudo -u user -c "%script%" # (remember to add the " or the arguments won't be visible by the script)


sudo -u user $(%script%)

Custom binaries

Some times is required to run the script with a binary which is not registered in the global or user paths.

One case is to run a Nodejs script with a different interpreter version. To achive that include the full path to the interpreter in the runas

/usr/local/lib/nodejs/v4/bin/node %script%

In Windows

The same aproach to execute custom scripts with unregistered interpreters apply both to Windows and Linux.

You will have to provide the absolute path to script interpreter.

Powershell Scripts Execution

To execute a powershell script you must add this line to the "RunAs" tasks' field.

powershell.exe -NonInteractive -ExecutionPolicy ByPass -File "%script%"

Use this line if you're using arguments in your script. Keep in mind that the filename of the ps1 script must not have white spaces.

powershell.exe -NonInteractive -ExecutionPolicy ByPass -File %script%

Sudo note.

On Windows there are some alternatives to achieve the same result you can get using sudo. The native way is by using [runas]( The main important difference is that you should provide the user password at least once.

There are other alternative tools and configurations you will have to find out by yourself.

Theeye Sample Scripts