Configure Monitoring for PHP

Configuring GermainUX PHP Monitoring: Profiles, Components, and Performance Metrics Configure GermainUX PHP monitoring to tailor profiling, transactions, sampling, network and SQL monitoring, integrations, correlation, analytics, privacy, alerts, automation, dashboards, and RCA.

​

Access PHP Monitoring Configuration

Start from: Open the PHP monitoring configuration associated with the PHP environment. Use the Wizard-generated configuration as the starting point rather than manually recreating the standard PHP configuration.

​

Configure the Application

Verify that PHP telemetry is associated with the correct monitored application. Use consistent names across: Correct application association is essential for correlation across browser, PHP, API, database, and infrastructure telemetry.

​

Configure the PHP Server

Verify that the correct PHP application server is associated with the monitoring configuration. The server identifies where the monitored PHP application executes and where the relevant Engine, Agent, and server profile apply.

​

Configure the PHP Monitoring Profile

PHP monitoring profiles are configured through: germain.apm.monitoringClient.phpMonitoringProfiles The standard PHP configuration documented by GermainUX includes: Basic Sampling Use the appropriate PHP monitoring profile for the application and environment.

​

Configure Sampling

Configure PHP profiling sampling according to the visibility required and acceptable overhead. Sampling determines how frequently or how broadly PHP execution is profiled. Use deeper profiling selectively when troubleshooting performance issues and lighter sampling for continuous production monitoring where appropriate. Validate overhead after changing the sampling configuration.

​

Configure Monitoring Components

PHP components are represented through: germain.apm.monitoringConfig.components Configure the monitoring components required for the environment. Enable only the components needed for the selected monitoring scope.

​

Configure Component Templates

Component templates are represented through: germain.apm.monitoringConfig.componentTemplates Use component templates to maintain consistent configuration across similar PHP environments. Different templates can be used when applications or environments require different monitoring behavior.

​

Configure the PHP Server Profile

Server profiles are represented through: germain.apm.monitoringConfig.serverProfiles The standard profile documented for PHP is: PHP Server Verify that the PHP Server profile is applied to each PHP application server that should be monitored.

​

Configure the PHP Agent

Verify the configuration in: germainapm.php including: GERMAIN_SERVICES_URL PROFILE_NAME and other environment-specific settings. The profile configured in the Agent must match the GermainUX PHP monitoring profile intended for the application.

​

Configure PHP Code Profiling

Configure which PHP execution needs deeper profiling. Code profiling can help identify: Use profiling selectively according to the troubleshooting objective.

​

Configure PHP Transaction Monitoring

Configure meaningful PHP transactions for analysis. Transactions can represent: Analyze each transaction with its associated:

​

Configure Network Request Monitoring

Configure monitoring for downstream network interactions initiated by PHP. Examples include:

• HTTP calls
• REST APIs
• External services

Analyze: Preserve parent transaction context so downstream latency can be attributed to the affected PHP transaction.

​

Configure SQL Monitoring

Configure SQL monitoring for database interactions executed within PHP transactions. Analyze: Where GermainUX database observability is also deployed, correlate the PHP SQL transaction with database-level telemetry.

​

Configure Integration Transactions

Configure monitoring for integration-level transactions. Examples include: Maintain correlation between the PHP parent transaction and the integration activity.

​

Configure Browser-to-PHP Correlation

Where browser monitoring is deployed, configure correlation between user activity and PHP processing. For example: or: or: This helps connect server-side PHP performance with the actual affected user experience.

​

Configure Stream Correlation Scenarios

PHP monitoring includes: germain.apm.analytics.streamCorrelationScenarios Configure stream correlation scenarios for relationships such as: Browser Event → PHP Transaction PHP Transaction → PHP Code PHP Transaction → SQL PHP Transaction → Network Request PHP Transaction → Integration A broader correlation path can be:

​

Configure KPIs

PHP KPIs are represented through: germain.apm.monitoringConfig.keyPerformanceIndicators Configure KPIs for important PHP conditions. Examples include: Use custom KPIs where the application’s critical operations require additional monitoring.

​

Configure SLAs

Create SLAs for PHP KPIs requiring threshold-based evaluation. Examples: PHP Transaction Duration > Threshold PHP Execution Time > Threshold Network Request Time > Threshold SQL Execution Time > Threshold Integration Duration > Threshold Use thresholds appropriate to the individual application and operation.

​

Configure Categorization

Categorize PHP telemetry into meaningful groups. For example: Categorization simplifies analysis, dashboards, reporting, and alerting.

​

Configure Root Cause Analysis

Configure correlation and analytics so PHP conditions can be analyzed from symptom to contributing component. Examples:

​

Configure RCA Dashboards

PHP monitoring includes: germain.apm.workspace.rcaDashboards Configure RCA dashboards to present correlated PHP telemetry. Useful content includes: Prefer correlated views rather than isolated technology metrics.

​

Configure Privacy & Exclusions

Review information captured by PHP monitoring. Potentially sensitive information may occur in:

Show all 9

• Authentication data
• API requests
• External-service payloads

Configure GermainUX privacy controls to:

• Mask
• Anonymize
• Exclude

Collect only information required for the monitoring objective.

​

Configure Alerts

Configure alerts for PHP conditions requiring attention. Examples include: Configure:

​

Configure Automation

PHP conditions can trigger GermainUX automation. For example: Actions can include:

​

Configure Dashboards

Configure dashboards for PHP application monitoring. Useful views include: Combine browser, PHP, database, and infrastructure telemetry where appropriate.

​

Configure Reports

Configure automated reports for: Set the appropriate schedule and recipients.

​

Configure Engine & Node

Verify the GermainUX Engine responsible for PHP monitoring. Where Engine configuration needs to be changed, use: Confirm:

​

Verify in Germain State

Navigate to: Verify the operational state of the Engine and monitoring environment. Check that expected PHP monitoring activity is running and telemetry is being received.

​

Validate the Configuration

Execute representative PHP activity and verify:

Show all 22

• PHP transactions
• Code profiling
• Network requests
• SQL
• Integrations
• Browser correlation where deployed
• KPIs
• SLAs
• Categorization
• Stream correlation
• RCA
• Privacy
• Alerts
• Automation
• Dashboards
• Reports

Also verify that profiling and monitoring introduce acceptable overhead.

​

Advanced Configuration

The documented PHP monitoring configuration includes these major areas: Use these advanced configuration areas when the Wizard-generated defaults need to be customized.

​

Get More Information

PHP environments can vary significantly depending on storefront customization, extensions, integrations, infrastructure, and security requirements. The GermainUX team can help configure the appropriate monitoring scope, privacy controls, analytics, alerts, and automation for your PHP environment. Please contact us for any help.

​

Get Help

The content of this document is proprietary to GERMAIN SOFTWARE LLC.