You can use this document to learn about the default data types that the Edge Delta agent sends to the Edge Delta backend.
These data types are different from the data collected by inputs.
To learn more about inputs, see Inputs.
Review the following table:
|Data Type||Description||Collected by Default?|
This data type can be collected from the environment, such as system_stats, or generated by a processor.
|Log Cluster Patterns||
Patterns are reduced versions of the original log line where specific parts are placed with asterisks ( * ).
Typically, these patterns do not contain sensitive data.
This data type can be enabled by adding a cluster processor.
|Log Cluster Samples||
This data type represents the raw logs that match a specific pattern.
For each distinct cluster pattern found by the agent, the agent also sends a few samples of that cluster.
This data type represents the logs generated from an issue.
An issue can be an anomaly detected by an individual agent or by the backend processing jobs.
Contextual logs are useful to investigate an issue and find a root cause.
In the Edge Delta App, you can use the Insights page to view all signals and findings.
|Raw Log Forwarding||
This data type is the raw line collected by the agent.
By default, raw logs are discarded; the Edge Delta backend never collects raw logs.
This data type is based on the input settings in the agent configuration.
This data type represents the compressed storage of raw logs on a cloud storage service, such as S3.
Edge Delta maintains separate S3 buckets per customer organization.
This data type populates the Log Search page where you can filter for specific logs.
This data type represents a signal detected by the agent regarding an unexpected event.
This information and corresponding metadata are sent to the Edge Delta backend by default.
This data type is based on the threshold settings in the agent configuration.
An event is a Kubernetes-based anomaly.
By default, Edge Delta consumes Kubernetes system events, and then displays those events on the Insights page.
This data type represents the heartbeat that the agent sends to the backend every minute.
Edge Delta uses this information to ensure that the agent is running.
This information populates the Pipeline Status page of the Edge Delta App.
|Agent Health Data||
This data type represents the various critical internal components of the agent.
This data includes:
The default settings listed above may be different for your account.
To view which logs are collected for your account:
- In the Edge Delta App, on the left-side navigation, click Data Pipeline, and then click Global Settings.
- Review the Data Ingestion Preferences section.
If you believe that any of these data types contain sensitive data that should not be sent to the Edge Delta backend, then please contact Support.
Additionally, the Edge Delta agent can operate in an offline mode. Specifically, the agent can run with a local YAML file and never communicate with the Edge Delta backend.