Eye on Data

# Events and notifications

Various events are registered in Eye on Data. They are split into two groups:

  • Notifications and faults: everything related to deviations, notifications and alarms.
  • System and user log: everything around system processes, settings and user actions.

# 1. Notifications and faults

This category covers notifications and faults that you create manually or that are generated automatically.

# ℹ️ What is the difference between a notification and a fault?

  • A notification is an information event (Info), for example a remark or an observation that is added manually.
  • A fault is a deviation that requires attention, and falls under one of the following types:
    • Warning
    • Critical
    • Timeout

# 📌 Examples of events

Type Description
Info event Manual notification added by a user, with a remark. (Notification)
Warning Generated automatically when a value falls outside the configured limits. (Fault)
Critical Serious deviation, for example a standstill; follow up immediately. (Fault)
Timeout No new data has been received within the expected time. (Fault)

# 🔔 Setting alarm rules

With alarm rules you can configure warnings for measurements. This way you know immediately when something goes wrong.

# ✅ Creating an alarm rule

  1. Open the tile for which you want to set an alarm.
  2. Click the alarm bell at the top right.
  3. Choose the right measurement (if there are several).
  4. Set the limit values:
    • For example: Critical High > 50°C, Critical Low < -10°C.
  5. Choose the interval (how often the value is checked).
  6. Set the check time (how long the deviation has to persist before a notification is sent).
  7. Click save.

# 📈 Alarm levels

From low to high:

  • OK
  • Info (Notification)
  • Warning (Fault)
  • Critical (Fault)

# ⏱️ Timeout alarm

If no new data has been received within a certain time, a timeout alarm is triggered automatically. This is considered a fault.

# 🛠️ Creating tasks from an alarm

When an alarm is active you can start a task straight away to arrange follow-up.

  1. Go to the Alarm Console.
  2. Click the pencil next to the alarm.
  3. Click New task.
  4. The task is filled in automatically based on the alarm.

# 💤 Masking an alarm

If an alarm is temporarily not relevant (during maintenance, for example), you can mask it.

# Masking an alarm

  1. Open the Alarm Console.
  2. Click the pencil next to the alarm.
  3. Choose Mask.
  4. Options:
    • Mask until a certain time.
    • Mask until manually unmasked.
  5. Add a remark if you wish.

# Removing the masking

  1. Go to the Masked alarms tab.
  2. Click the pencil next to the alarm.
  3. Choose Unmask.
  4. Add a remark (optional).

ℹ️ Automatic remarks are added when masking expires because of the time limit.

# 📬 Setting notifications

  1. Click your user name at the top right.
  2. Go to the Notifications tab.
  3. Choose:
    • Which levels you want to follow (e.g. only Critical).
    • For which alarms you want notifications.
  4. Click Save.

Navigation

# ✍️ Creating a user event

You can also add a notification or fault yourself:

  1. Click a measurement in a tile.
  2. Choose Create event.
  3. Add your message or remark.
  4. Select the right level (Info for a notification, Warning/Critical/Timeout for a fault).
  5. The event appears in the log book and, if applicable, on charts.

# 2. System and user log

These events are recorded automatically by Eye on Data.

# 🖥️ System events

Examples:

  • Creating or restoring backups.
  • System actions in the background.

# 📝 Audit events

Examples:

  • Logging in and logging out.
  • Changing settings.
  • User management.

# 📊 Event overview

At the bottom of the portal you will find an overview of all events. Every line contains:

Field Description
Start time When the event started
End time When it ended (if applicable)
Measurement Sensor or measurement it relates to
Value Value at the start of the event
Message What happened?
Type New, comment, etc.
Level OK, Info, Warning, Critical
Status Active, closed, etc.
Data source Where does the data come from?
Comment Any extra explanation
Asset Device involved
Project What does this belong to?
Company Organisation or customer
Component Specific component of the software
User Who created or changed the event?

🔄 If an event evolves (e.g. from warning to critical), you see this as a history that you can unfold.

← Assets →