Skip to content

Commit

Permalink
Merge pull request #13170 from alvarocabanas/develop
Browse files Browse the repository at this point in the history
Add wmi_enable_proc_data flag to infrastructure agent configuration
  • Loading branch information
x8a authored May 23, 2023
2 parents 70f23e1 + 7544b02 commit 651d86e
Showing 1 changed file with 72 additions and 14 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -624,13 +624,13 @@ For an example of how all these variables can be used, see our [sample configura
</tr>
</tbody>
</table>
</Collapser>
</Collapser>
</CollapserGroup>

## Cloud variables

If the agent is running in a cloud instance, the agent will try to detect the cloud type and fetch basic [metadata](/docs/integrations/new-relic-integrations/getting-started/understand-use-data-infrastructure-integrations#overview).
Metrics can also be enriched with extended cloud metadata (including custom resource tags) when [connecting the cloud provider](/docs/infrastructure/infrastructure-integrations/get-started/introduction-infrastructure-integrations#cloud) account with New Relic.
Metrics can also be enriched with extended cloud metadata (including custom resource tags) when [connecting the cloud provider](/docs/infrastructure/infrastructure-integrations/get-started/introduction-infrastructure-integrations#cloud) account with New Relic.

<CollapserGroup>
<Collapser
Expand Down Expand Up @@ -1692,7 +1692,7 @@ Metrics can also be enriched with extended cloud metadata (including custom reso
A list of environment variables that will be passed to all integrations. If an integration already has an existing configuration option with the same name, then the environment variable takes precedence.

Starting with infrastructure agent 1.24.1 passthrough_environment supports regex for variable names.

<table>
<thead>
<tr>
Expand Down Expand Up @@ -1757,16 +1757,16 @@ Metrics can also be enriched with extended cloud metadata (including custom reso
```
NRIA_PASSTHROUGH_ENVIRONMENT="HOST,PORT,NRIA_.*"
```

For Windows hosts:
`PATHEXT` is an MS Windows environment variable. The function is to determine which file extensions mark files that are executable from every command line. This will resolve any errors reporting '... is not recognized as the name of a cmdlet, function, script file..." for common Flex integrations:

```
passthrough_environment:
- PATHEXT
```


</Collapser>

<Collapser
Expand Down Expand Up @@ -2128,7 +2128,7 @@ Metrics can also be enriched with extended cloud metadata (including custom reso
</tbody>
</table>
</Collapser>

<Collapser
className="freq-link"
id="enable-async-inventory"
Expand Down Expand Up @@ -2247,8 +2247,8 @@ Metrics can also be enriched with extended cloud metadata (including custom reso
Example as a YAML attribute:

```
ignored_inventory:
- files/config/stuff.bar
ignored_inventory:
- files/config/stuff.bar
- files/config/stuff.foo
```

Expand Down Expand Up @@ -2794,7 +2794,7 @@ Metrics can also be enriched with extended cloud metadata (including custom reso
From version [v1.28.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes) on, you can use the built-in log rotation feature.
By default, log rotation is disabled. To enable it, you have to specify the maximum size of the log file with the `max_size_mb` option.
When the infrastructure agent log file reaches that size, the current log file will be rotated into a new file.

```yml
log:
level: info
Expand All @@ -2812,7 +2812,7 @@ Metrics can also be enriched with extended cloud metadata (including custom reso
id="rotate-max_size_mb"
title="max_size_mb"
>
`max_size_mb` specifies the maximum size in MegaBytes of the infrastructure agent log file. When the file has reached this size, the current logs will be rotated into a new file.
`max_size_mb` specifies the maximum size in MegaBytes of the infrastructure agent log file. When the file has reached this size, the current logs will be rotated into a new file.
When the `max_size_mb` is `0`, built-in log rotation is disabled.

<table>
Expand Down Expand Up @@ -3075,7 +3075,7 @@ Metrics can also be enriched with extended cloud metadata (including custom reso


<Callout variant="tip">
Infrastructure agent version 1.28.0 introduced backward-compatible improvements in logging configuration.
Infrastructure agent version 1.28.0 introduced backward-compatible improvements in logging configuration.
See our [github documentation](https://github.com/newrelic/infrastructure-agent/blob/master/docs/log_configuration.md) to understand the legacy settings and how to map them to the new structure.
</Callout>

Expand Down Expand Up @@ -6092,6 +6092,64 @@ If you are having problems with proxy configuration, see [Proxy troubleshooting]
</tbody>
</table>
</Collapser>

<Collapser
className="freq-link"
id="wmi_proc_data"
title="wmi_proc_data"
>
If you set it to true, you'll get process information from WMI and you'll skip the query access check on a restricted environment.

<table>
<thead>
<tr>
<th style={{ width: "200px" }}>
YML option name
</th>

<th style={{ width: "200px" }}>
Environment variable
</th>

<th>
Type
</th>

<th>
Default
</th>

<th>
Version
</th>
</tr>
</thead>

<tbody>
<tr>
<td>
`enable_wmi_proc_data`
</td>

<td>
`NRIA_ENABLE_WMI_PROC_DATA`
</td>

<td>
boolean
</td>

<td>
`false`
</td>

<td>
[1.3.1](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1420)
</td>
</tr>
</tbody>
</table>
</Collapser>
</CollapserGroup>

## HTTP Client
Expand All @@ -6108,7 +6166,7 @@ Configure the HTTP client used for backend communication.

```
http:
headers:
headers:
"Proxy-Authorization": "myToken"

```
Expand Down

0 comments on commit 651d86e

Please sign in to comment.