--- title: Default infrastructure monitoring data source: https://docs.newrelic.com/docs/infrastructure/infrastructure-data/default-infra-data --- New Relic's infrastructure agent collects and displays data using six primary [events](https://docs.newrelic.com/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data), each with associated [attributes](https://docs.newrelic.com/docs/accounts-partnerships/education/getting-started-new-relic/glossary#attribute) that represent assorted metrics and metadata. Understanding infrastructure data can help you: - Better understand our infrastructure monitoring UI. - [Manage your infrastructure data](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/manage-your-agent/manage-infrastructure-data-reporting). - Run better [queries of your data](#query-data). - Set up better monitoring solutions using [custom attributes](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/configuration/configure-infrastructure-agent#attributes). > #### 💡 TIP > > Check out our [troubleshooting tutorial](https://docs.newrelic.com/docs/tutorial-troubleshoot-infra-hosts/diagnose-app-infra-data) for your infrastructure host data. The tutorial series walks you through how to find data in the infrastructure UI to resolve an alert event and make a resource decision about your hosts. ## Infrastructure events The following are [events](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/understand-data/new-relic-data-types#events-new-relic) reported by default by the infrastructure agent and some [infrastructure integrations](https://docs.newrelic.com/docs/intro-infrastructure-integrations). The attributes attached to these events are the metadata and metrics used to create our infrastructure UI visualizations. You can also [create custom queries and charts](#query-data) of this data. If you're using integrations, see that integration's doc for more on reported data. For common AWS attributes, see [AWS data](#shared-attributes). Select an event name in the following table to see its attributes. | Event | Description | | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [`SystemSample`](/attribute-dictionary/?event=SystemSample) | `SystemSample` contains data describing the current overall state of the entire server, including CPU, memory, disk, and network. We take a snapshot of this data every 5 seconds and package it into a `SystemSample` event, which is then sent to New Relic. This data appears on the [**Systems** UI tab](https://docs.newrelic.com/docs/infrastructure/infrastructure-ui-pages/infra-hosts-ui-page#system). | | [`ProcessSample`](/attribute-dictionary/?event=ProcessSample) | `ProcessSample` gathers detailed resource usage information from programs running on a single system. We take a snapshot of this data every 20 seconds for every active process and package it into a `ProcessSample` event, which is then sent to New Relic. This data appears on the [**Processes** UI page](https://docs.newrelic.com/docs/infrastructure/infrastructure-ui-pages/infra-hosts-ui-page#processes). > #### ⚠️ IMPORTANT > > Process metrics are not reported by default. To report this data, [enable process metrics](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/configuration/infrastructure-configuration-settings#enable-process-metrics). | | [`StorageSample`](/attribute-dictionary/?event=StorageSample) | `StorageSample` represents a single storage device that contains partitions currently mounted on the server. Each sample gathers descriptive information about the device, the type of file system it uses, and its current usage and capacity. We take a snapshot of this data every 20 seconds for each mounted file system and package it into a `StorageSample` event, which is then sent to New Relic. This data appears on the [**Storage** UI page](https://docs.newrelic.com/docs/infrastructure/infrastructure-ui-pages/infra-hosts-ui-page#storage). > #### ⚠️ IMPORTANT > > If your server uses disks with file systems other than the supported file systems in the following table, `StorageSample` events will not be generated for those disks. **Supported Linux storage systems** Supported Linux storage file systems: - `xfs` - `vxfs` - `btrfs` - `ext` - `ext2` - `ext3` - `ext4` - `hfs` - `zfs` **Supported Windows storage systems** Supported Windows storage file systems: - `NTFS` - `ReFS` (version 1.0.976 and higher) | | [`NetworkSample`](/attribute-dictionary/?event=NetworkSample) | `NetworkSample` captures the descriptive and state information for each network device associated with a server. It includes the device's interface and address information, as well as current usage data. We take a snapshot of this data every 10 seconds for each attached network interface and package it into a `NetworkSample` event, which is then sent to New Relic. This data appears on the [**Network** UI page](https://docs.newrelic.com/docs/infrastructure/infrastructure-ui-pages/infra-hosts-ui-page#network). > #### ⚠️ IMPORTANT > > Not all the network devices will be included by default, the filters in the following table will not generate `NetworkSample` for the matching interfaces unless the [network-inferface-filters](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#network-interface-filters) config attribute is modified. **Linux** Default network interface filters for Linux: - Network interfaces that start with `dummy`, `lo`, `vmnet`, `sit`, `tun`, `tap`, or `veth` - Network interfaces that contain `tun` or `tap` **Windows** Default network interface filters for Windows: - Network interfaces that start with `Loop`, `isatap`, or `Local` | | [`ContainerSample`](/attribute-dictionary/?event=ContainerSample) | `ContainerSample` collects the descriptive and state information for each Docker container. It includes the container's ID, name, image, image name, as well metrics about CPU, memory and networking. We take a snapshot of this data every 15 seconds for each container and package it into a `ContainerSample` event, which is then sent to New Relic. This data appears on the [**Containers** UI page](https://docs.newrelic.com/docs/infrastructure/infrastructure-ui-pages/infra-hosts-ui-page#containers). For more information, see [Docker monitoring](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/data-instrumentation/docker-instrumentation-infrastructure). | | [`InfrastructureEvent`](/attribute-dictionary/?event=InfrastructureEvent) | `InfrastructureEvent` describes changes (deltas) that occur in a system's live state. When an inventory or system state is added, removed, or changed, we'll generate an `InfrastructureEvent` that logs that activity. This data appears on the [**Events** UI page](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/infrastructure-ui-pages/infrastructure-events-page-live-feed-every-config-change). | To learn about infrastructure integration data, see the [documentation for a specific integration](https://docs.newrelic.com/docs/infrastructure/infrastructure-integrations/get-started/introduction-infrastructure-integrations). If an AWS integration is enabled, your infrastructure events may also have [AWS attributes](#shared-attributes) attached. ## Query infrastructure data [#query-data] You can [query your infrastructure data](https://docs.newrelic.com/docs/using-new-relic/data/understand-data/query-new-relic-data) to troubleshoot a problem or create a chart, or to understand what data is available. For example, to see what data is attached to `ProcessSample`, you would run this NRQL query: ```sql SELECT * FROM ProcessSample ``` Metrics from the New Relic infrastructure agent (`SystemSample`, `StorageSample`, `NetworkSample`, and `ProcessSample`) get aggregated into buckets to improve the query performance over longer periods of time. NRQL queries spanning less than one hour directly access the raw data. For queries exceeding one hour, data is retrieved from the following aggregated buckets: - 1 minute (scopes of 1 hour to 6 hours) - 10 minutes (scopes of 6 hours to 3 days) - 1 hour (scopes of 3 days to 14 days) - 3 hours (scopes of 14+ days) You can also [query infrastructure using dimensional metrics](https://docs.newrelic.com/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/query-infrastructure-dimensional-metrics-nrql). > #### ⚠️ IMPORTANT > > Historically, these aggregated event buckets only contained one average value per metric. We are gradually migrating the aggregation to use the [gauge format](https://docs.newrelic.com/docs/data-apis/understand-data/metric-data/metric-data-type/) instead. This allows you to differentiate between `max()`, `min()`, and `average()` values. > > To check if your data is using the gauge format, run a query like this: > > ```sql > FROM SystemSample SELECT cpuPercent SINCE 90 minutes ago > ``` > > If the result shows `"type": "gauge"`, your data is using the new format. ## Manage data For tips on managing data ingest and reporting, see [Manage infrastructure data](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/manage-your-agent/manage-infrastructure-data-reporting). ## Add custom attributes [#custom-attributes] You can create [custom attributes](https://docs.newrelic.com/docs/meatballs-configuring-your-agent#attributes) in the infrastructure agent's YAML file. Use this metadata to: - Filter your entities in the [entity filter bar](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities) - Populate the [**Group by**](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/filter-group/group-infrastructure-results-specific-attributes) menu - Annotate your infrastructure data ## Common Amazon EC2 attributes [#shared-attributes] If you use our Amazon Elastic Compute Cloud (EC2) integration, we report data from your Amazon EC2 instances. Amazon EC2-related attributes are common attributes present for any events reported from your EC2 instances. These attributes and their values are subject to change if Amazon changes the data they expose. **`awsAccountId`** The AWS account id (determined by Amazon Web Services). **`awsRegion`** The region (determined by Amazon Web Services) where the AWS server exists. **`awsAvailabilityZone`** The availability zone (determined by Amazon Web Services) where the AWS server exists. **`ec2InstanceType`** The Amazon Web Services instance type, displayed in AWS-specific codes. **`ec2InstanceId`** The Amazon Web Services instance's unique identifying number for the server. **`ec2AmiId`** The Amazon Machine Image (AMI) identification number of the image used by Amazon Web Services to bootstrap the Amazon EC2 instance. **`ec2SubnetId`** The networking sub-net identifier on which the server is connected. **`ec2VpcId`** The Virtual Private Cloud identifier (if any) for this server. **Other Amazon EC2 attributes** If Amazon Web Services changes the metadata they make available to us, other attributes and values collected also may be available. A sub-set of these attributes are collected from the infrastructure agent when installed in the EC2 instances: - `awsAccountId` - `awsRegion` - `awsAvailabilityZone` - `ec2AmiId` - `ec2InstanceType`