Entities
An entity is a monitored object — a WordPress site, a Vault cluster, or a Vault node. Each entity has its own credentials, rules, dashboards, and ingestion history.
Adding an entity
- Go to Entities → Add Entity
- Select the entity type (WordPress or Vault)
- Enter a name, URL (for WordPress) or node address (for Vault)
- Complete the wizard — credentials are generated for you
After creating the entity, connect your plugin or agent using the credentials on the Credentials tab.
Entity list
The entity list shows all entities in your account. For each entity:
- Name — the label you assigned
- Type — WordPress or Vault
- Status — Enabled or Disabled
- Health — a health score based on recent signal activity
Use the search box to filter by name. Use the type filter to narrow to WordPress or Vault entities.
Entity details
Each entity has several sub-sections:
Details
Edit the entity name, URL/node address, and description. The entity type cannot be changed after creation.
Credentials
The API Token and API Secret used by the plugin or agent to authenticate with the Logystera gateway. Copy these during initial setup.
If you regenerate credentials, the old credentials stop working immediately. Update the plugin or agent configuration before regenerating.
Rules
Enable or disable individual alert rules for this entity. Rules that are disabled will not fire alerts, even if the conditions are met.
Some rules are recommended for all entities (shown highlighted). Disabling them is possible but will reduce coverage.
Ingestion
Tracks every batch of logs received from the plugin or agent, through to processing.
Statistics (last 24h):
| Metric | Description |
|---|---|
| Total batches | All batches received |
| Completed | Successfully processed |
| Failed | Processing errors |
| Skipped | Duplicate or filtered batches |
| Logs received | Raw log events received |
| Logs processed | Events that matched metric definitions |
| Processing time | Average time from receipt to completion |
| Drop rate | Percentage of logs that were not processed |
Batch table columns:
| Column | Description |
|---|---|
| Batch ID | Unique identifier for the batch |
| Log type | Source type (e.g. audit, wordpress) |
| Status | Completed / Failed / Skipped / Processing |
| Logs | Processed / received count |
| Duration | Processing time |
| Matches | Metrics, rules, and signals detected in this batch |
| Latency | Time from batch receipt to processing start |
Filter by status using the tabs at the top of the table.
Access
Control which team members can see this entity. By default, all tenant members have access.
To restrict access: 1. Set access to Restricted 2. Add specific users who should have access
Users not on the list will not see the entity in their entity list or dashboards.
Webhooks
Configure webhook endpoints to receive alerts from this entity. See Webhooks for the full reference.
Notifications
Configure how alerts from this entity are delivered (email, webhook). Entity-level notification settings override account-level defaults for this entity.
Subscription
Shows which subscription plan this entity is assigned to. An entity must be assigned to an active subscription to receive full monitoring coverage.
Disabling an entity
Disabling an entity pauses monitoring without deleting it. No alerts will fire, and the agent or plugin will continue to send data (it is buffered but not processed).
To disable: entity Details → toggle the Enabled switch.
Deleting an entity
Deleting an entity is permanent. All associated ingestion history and alert history is removed.
The credentials for the deleted entity stop working immediately. Update or remove the plugin/agent configuration to avoid failed delivery attempts.