mastersign/dashops

Control Panel for Script Execution and Monitoring on Windows

DashOps

A control panel for script execution and service monitoring

dashops's Issues

Auto facettes, auto tags

Generate facette values and tags automatically when certain conditions are met.

Examples:

• If facette host matches regex -production$ set facette environment to production
• If facette verb is install add tag setup

Support for arbitrary environment variables

A dashboard project should allow setting arbitrary environment variables for all command actions and command monitors.

The command actions and command monitors should support setting individual environment variables.

Default project file

If no command line argument is provided, a file called dashops.yaml in the current working directory, should be loaded as default.

Add button for editing target script

Show a button for each action to open the action target in a text editor, if the command points to a script file.

Prevent action buttons from firing twice if double clicked

Show full command as secondary info

Provide a way to see the complete expanded command, which is to be executed when pressing an action button.

This could be in the form of a tooltip or as grey text beneath the action description.

Pre- and Post-Execution commands

The dashops configuration should allow running a global pre- and post- execution command.
These commands are run directly before and after every command action and command monitor.

These hooks allow customizing the execution environment of the actual commands.

Navigation targets for hosts, services, and tags

Navigation targets would be helpful to speed administration tasks.

Possible types:

• Filesystem location
• URL to show in the browser (e.g. web UIs of service backends, possibly with credentials)
• Shell window on specific location

Navigation targets are annotated with facettes like actions.

Add support for action discovery

Implement a way to discover executable or script files in a folder structure by regular expressions.

Switch to control whether a PowerShell window keeps open or not

global flag: keep-action-open
local flag: keep-open

Automatic IDs for actions

Build an automatic ID for actions based on the exact command line which is executed.

Monitors

Add support for watchdog actions, which are executed repeatedly in an interval. An additional section in the UI to show the current state of the watchdogs.

• If a watchdog action returns 0 no log is saved and the UI element shows OK.
• If a watchdog action returns a value unequal 0 for the first time a log is saved and the UI element shows ERROR.
• If a watchdog action returns a value unequal 0 repeatedly, no log is saved but the UI element keeps showing ERROR.

Show meaningful title in PowerShell window

Add a line to the constructed powershell command, which changes the window title of the current PS-Host to the description/title of the action/monitor.

Add support for action patterns

Implement a way to build actions from lists of facette values.

Example

Facette values

• a → [A, B]
• b → [X, Y]

Command Pattern

• Description Template: run ${b} in project ${a}
• Command Template: %USERPROFILE%\scripts\Project ${a}\run.ps1
• Argument List: [${b}]

Result Actions

• run X in project A: %USERPROFILE%\scripts\Project A\run.ps1 X
• run Y in project A: %USERPROFILE%\scripts\Project A\run.ps1 Y
• run X in project B: %USERPROFILE%\scripts\Project B\run.ps1 X
• run Y in project B: %USERPROFILE%\scripts\Project B\run.ps1 Y

Button for showing last logfile for action

Add a button to show the last log file for an action

Add button to edit project file

Show a button to open the project file in a text editor. (see #7)

Web Monitors

Extension to #8: monitors to send HTTP requests

Suppress logs optionally

Add a flag to suppress writing logs for individual actions or monitors.

Documentation for project file format

Create an automated way to build a project file documentation from the Model.xml