Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(PHP): Clarify Docker compatibility #15594

Merged
merged 2 commits into from
Jan 12, 2024
Merged

fix(PHP): Clarify Docker compatibility #15594

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3f3ae69
fix(PHP): Clarify Docker compatibility
austin-schaefer Dec 20, 2023
9f1256f
Merge branch 'develop' into NR-161020
homelessbirds Jan 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 5 additions & 8 deletions ...advanced-installation/docker-other-container-environments-install-php-agent.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,10 @@ signupBanner:
freshnessValidatedDate: never
---

You can install the PHP agent on a Docker container or other container to monitor one or more of your PHP applications. This is supported for containers that meet [PHP agent requirements](/docs/agents/php-agent/getting-started/php-agent-compatibility-requirements).
You can install the PHP agent on a Docker container or other container to monitor one or more of your PHP applications. This is supported for containers that meet the standard [PHP agent compatibility and requirements](/docs/agents/php-agent/getting-started/php-agent-compatibility-requirements).

<Callout variant="caution">
The PHP Agent's daemon transmits data to New Relic periodically during the minute-long [harvest cycle](/docs/using-new-relic/welcome-new-relic/getting-started/glossary#harvest-cycle). If you're starting up and tearing down containers often, ensure that you leave the daemon container running long enough to transmit any remaining data.
<Callout variant="important">
The PHP agent's daemon transmits data to New Relic periodically during the minute-long [harvest cycle](/docs/using-new-relic/welcome-new-relic/getting-started/glossary#harvest-cycle). If you're starting up and tearing down containers often, ensure that you leave the daemon container running long enough to transmit any remaining data.
</Callout>

## Container options [#overview]
Expand All @@ -29,12 +29,9 @@ The PHP agent requires two components to work: the PHP agent (one for each appli

## Install agent and daemon in different containers [#install-diff-containers]

Requirements:

* Meet [PHP agent requirements](/docs/agents/php-agent/getting-started/php-agent-compatibility-requirements)
* PHP agent version 9.2 or higher
Installing the agent and daemon in different containers is supported on PHP agnet versions 9.2 and higher.

To see an example application, go to [New Relic's Support Forum](https://discuss.newrelic.com/t/relic-solution-php-agent-and-daemon-containers/84841). If you're using short-lived application containers, we recommend you use a separate container for the PHP Agent's daemon.
To see an example application, go to [New Relic's Support Forum](https://discuss.newrelic.com/t/relic-solution-php-agent-and-daemon-containers/84841). If you're using short-lived application containers, we recommend you use a separate container for the PHP agent's daemon.

<Callout variant="caution">
Data transmitted from the agent to the daemon is **not** encrypted. The only exception to this is the [SQL obfuscation](/docs/agents/php-agent/configuration/php-agent-configuration#inivar-tt-sql) that happens before sending data to the daemon. If the agent and daemon are running on different hosts, we recommend that you use a private network connection between the agent and daemon.
Expand Down
Loading