8. RED Vision¶
RED Vision is the web GUI of the RED framework. It provides operational monitoring, application and SLA tracking, lineage, security insight, licence and storage analytics, and the AI assistant AskWally in the browser.
8.1. Access¶
RED Vision runs on the RED server of each environment instance and is opened in the browser at https://<red-server>:<vis_port> (parameter vis_port in the section [REDVIS] of the instance configuration, see the RED-PSS Guide). It is operated with visctl.
Important
RED Vision only uses HTTPS if the parameter ssl_enabled is set to true (default false). The certificate and private key are taken from $REDENV_HOME/etc/ssl/VIS (by default a link to the certificates of the REST API); if they are missing or invalid, a self-signed certificate is created on start (see the RED-PSS Guide). Without HTTPS the login data is transmitted unencrypted, so always operate RED Vision with HTTPS.
8.1.1. Login and Roles¶
Important
RED Vision has no user management of its own: users are authenticated against the Exasol database.
Users log in with their personal database user name and password. RED Vision passes them to Exasol, which checks them, i.e. the database account and its authentication method apply:
For users authenticated via LDAP, Exasol checks the password with the LDAP directory.
Password policies, password expiry, and account locks are enforced by Exasol. An expired password (e.g. the initial password of a new user) has to be changed in the database, e.g. with a SQL client, before RED Vision can be used.
User accounts are the database accounts managed by the Security Manager or an IDM (see RED Authorisation Concept); there is no separate RED Vision account.
After a successful login, RED Vision determines the role of the user from the administrative roles:
DATABASE ROLE |
ROLE IN RED VISION |
ADDITIONAL FUNCTIONS |
|---|---|---|
R_APPMGR |
Application Manager |
approval of data quality results |
R_SECMGR |
Security Manager |
configuration of the language model for AskWally |
R_APPMON |
Application Monitor |
read-only monitoring |
A user with several roles is logged in as the first of them in the order above; the Security Manager functions remain available. Users without one of these roles are denied access.
All queries run with the user’s own database connection, so the user’s privileges as well as row and column level security apply: each user only sees what they may see in the database.
8.1.2. Sessions¶
A session is valid for 8 hours after the login, independent of the activity, and ends earlier with the logout.
To open database connections on behalf of the user, RED Vision keeps the password encrypted on the RED server for the duration of the session. It is not written to the database.
Changing the password or locking the account only prevents new logins and new database connections. Database connections already opened by an active session remain usable until the session ends; to cut off a user immediately, also kill the user’s database sessions.
8.2. Functions¶
PAGE |
CONTENT |
|---|---|
Dashboard |
load of the job monitor and the worker queues, PSA and TSA loader statistics, jobs and watchers |
Applications |
status of applications per business date (loaded, preliminary, final, data quality, materialisation), their components, actions, and objects; partial progress of unfinished milestones (e.g. 4 of 10 objects finished); data quality approval |
Object pipeline |
for an object, BDomain, and business date: the executed chain from the source via TSA to PSA, or the layer on which a delivery is waiting |
Calendar |
calendar definitions, business days, holidays, and delivery keys |
Lineage |
table lineage from the source via loader and TSA to the PSA, and column lineage across all layers and BI systems (with the Data Lineage module) |
Security |
users, sandboxes, object groups, tenants, security columns, and the refresh status of the security framework, depending on the user’s privileges |
Licences |
RED and Exasol licence status, storage growth, and the prognosis of the licence limits |
Status values are shown with the labels and severities of the status catalogue REDSYS.VIS_STATUS_CODES, so RED Vision and the monitoring views use the same vocabulary.
8.3. AskWally¶
AskWally is the AI assistant embedded in RED Vision. It answers questions about RED concepts from the RED documentation and questions about the current state of the system, e.g. why an application is not finished or on which delivery an object is waiting. It also explains the lineage and the impact of changes and helps to write SQL for questions about your data; the user runs this SQL with the Execute button, with their own access rights.
AskWally only uses read-only queries with the logged-in user’s own database connection; it sees exactly what the user may see.
Concept questions are only answered from the documentation; if nothing relevant is documented, AskWally says so instead of guessing.
The language model (e.g. OpenAI, Azure OpenAI, Anthropic, Google Gemini, Ollama) and its access key are configured in RED Vision by the Security Manager. The key is stored encrypted and never leaves the RED server.
The questions and the results of the queries AskWally runs are sent to the language model. With a cloud provider this content leaves your environment; for sensitive data use a locally operated model (e.g. Ollama) or the on-premise AI solution AiSEC from Sphinx, which keeps your data in your own infrastructure.