---
title: "Eyeglass"
url: "https://axoflow.com/docs/axoflow/0.86/data-sources/appliances/superna/eyeglass/"
last_modified: "2026-05-12T12:48:47+02:00"
---

> For the complete documentation index, see [llms.txt](https://axoflow.com/docs/axoflow/0.86/llms.txt).

# Eyeglass

Eyeglass:
Manages and automates data protection, DR, and reporting for PowerScale environments.

The following sections show you how to configure [Superna Eyeglass](https://docedit.supernaeyeglass.com/home/en-us/) to send their log data to Axoflow.

**CAUTION:**

Make sure to set data forwarding on your appliances/servers as described in this guide. Different settings like alternate message formats or ports might be valid, but can result in data loss or incorrect parsing.

## Prerequisites

- You have administrative access to Superna Eyeglass.
- You have an [AxoRouter deployed and configured](https://axoflow.com/docs/axoflow/0.86/provisioning/axorouter/index.md) with a [webhook connector](https://axoflow.com/docs/axoflow/0.86/data-sources/webhook/index.md). This device is going to receive the data from Superna Eyeglass.
- You know the IP address the AxoRouter. To find it:

  1. Open the AxoConsole.
  2. Select the **Routers** or the **Topology** page.
  3. Select on AxoRouter instance that is going to receive the logs.
  4. Check the **Networks > Address** field.

## Steps

Note: The steps involving the Superna Eyeglass user interface are just for your convenience, for details, see the [official documentation](https://manuals.supernaeyeglass.com/project-eyeglass-administration-guides/HTML/custom-email-routing-by-application.html#h3__1549642802).

1. Log in to Ransomware Defender and open the Zero Trust menu.
2. Click the plus sign to add a webhook target.
3. Set the parameters of the webhook.

   - **Name**: Enter a name for the webhook, for example, `Axoflow`.
   - **URL**: Enter the URL of the [webhook connector](https://axoflow.com/docs/axoflow/0.86/data-sources/webhook/index.md) of the AxoRouter instance where you want to post messages.
   - **Event Severity Filter**: Select the severities of the events that you want to forward to the webhook.
   - **Lifecycle filter**: Select the lifecycle changes that trigger a post message to the webhook.
4. Click **Save**, then the **Test webhooks** button. This will send a post message with a sample payload.
5. Add the source to AxoConsole.

   1. Open the AxoConsole and select **Topology**.
   2. Select **Add Item > Source**.

      ![Add Source](https://axoflow.com/docs/axoflow/0.86/img/add-source_hu_47110bad1427b1fb.webp)

      - If the source is actively sending data to an AxoRouter instance, select **Detected**, then select your source(s) and select **Add Selected Source(s)**.
      - Otherwise, select the vendor and product corresponding to your source from the **Predefined** sources, then enter the parameters of the source, like **IP address** and **FQDN**.

        ![Add Source parameters](https://axoflow.com/docs/axoflow/0.86/img/add-source-config_hu_fc34536e87d6ce37.webp)
      > **Note:**
      > During [log tapping](https://axoflow.com/docs/axoflow/0.86/onboard-hosts/log-tapping/index.md), you can add hosts that are actively sending data to an AxoRouter instance by clicking **Register source**.
   3. (Optional) Add [custom labels](https://axoflow.com/docs/axoflow/0.86/onboard-hosts/hosts/add-host-metadata/index.md) as needed.
   4. Select **Add**.
   5. (Optional) **Add Path** manually. That’s needed only when AxoConsole can’t detect the path based on the IP address and the FQDN, and you haven’t yet configured the source to send data to the router. If you’ve added the source from the **Detected** list, you can skip this step, as the path is created automatically.

      Create a path between the source and the AxoRouter instance.

      If you’ve added the source from the **Detected** list, you can skip this step, as the path is created automatically.

      1. Select **Topology > Add Item > Path**.

         ![Add a new path](https://axoflow.com/docs/axoflow/0.86/img/data-management/flow-management/paths/add-path_hu_bedfdb7f0050673a.webp)
      2. If not set automatically, select the beginning of the path in the **Source host** field.
      3. Select the target router or aggregator this source is sending its data to in the **Target host** field, for example, `axorouter`.
      4. Select the **Target connector**. The connector determines how the destination receives the data (for example, using which protocol or port).
      5. Select **Add**. The new path appears on the **Topology** page.

         ![The new path](https://axoflow.com/docs/axoflow/0.86/img/data-management/flow-management/paths/path-created_hu_8e6634dca1ed0d1a.webp)

## Labels

Axoflow automatically adds the following labels to data collected from this source:

| Analytics label | Message field | Value |
| --- | --- | --- |
| `vendor` | [`meta.vendor`](https://axoflow.com/docs/axoflow/0.86/reference/message-schema/reference/index.md#meta.vendor) | `superna` |
| `product` | [`meta.product`](https://axoflow.com/docs/axoflow/0.86/reference/message-schema/reference/index.md#meta.product) | `eyeglass` |

You can use the labels as:

- **Filter labels** on the [Analytics page](https://axoflow.com/docs/axoflow/0.86/metrics/analytics/index.md),
- in the **Filter By Label** field during [log tapping](https://axoflow.com/docs/axoflow/0.86/onboard-hosts/log-tapping/index.md).

You can use the message fields

- in [Flow Processing steps](https://axoflow.com/docs/axoflow/0.86/data-management/processing/index.md), for example, in the **Query** field of **Select Messages** steps,
- in AQL expressions in the search bars.

## Sending data to Splunk

When sending the data collected from this source to Splunk, Axoflow uses the following sourcetype and index settings:

| sourcetype | index |
| --- | --- |
| `superna:eyeglass` | `main` |

If the Axoflow classification doesn’t set the source field for the message automatically, and you haven’t set it in a [flow processing step](https://axoflow.com/docs/axoflow/0.86/data-management/processing/index.md#set-fields) manually (by setting the `meta.destination.splunk.source` field), AxoRouter automatically sets the source to the [name of the AxoRouter connector](https://axoflow.com/docs/axoflow/0.86/reference/message-schema/reference/index.md#meta.connector.name) that received the message (for example, `axorouter-syslog-tcp-514`).

## Sending data to Google SecOps

When sending the data collected from this source to a [*dynamic* Google SecOps destination](https://axoflow.com/docs/axoflow/0.86/destinations/google/secops/index.md), Axoflow sets the following log type: `SUPERNA_EYEGLASS`.

## Sending data to Microsoft Sentinel

When sending the data collected from this source to a [Microsoft Sentinel destination](https://axoflow.com/docs/axoflow/0.86/destinations/microsoft/sentinel/index.md), Axoflow normalizes the data and sends it to the following table: `Syslog`.