For AI agents: a documentation index is available at https://www.mongodb.com/zh-cn/docs/llms.txt — markdown versions of all pages are available by appending .md to any URL path.

Troubleshoot Product Usage Telemetry

This page describes how to resolve issues with product usage telemetry in Ops Manager 9.0.2, 8.0.28, and later. To learn how product usage telemetry works, see Product Usage Telemetry.

If the Product Telemetry Collection toggle is locked on, the installed license key doesn't include an active telemetry exemption. Without an exemption, product usage telemetry is mandatory.

To turn off product usage telemetry, you need an active telemetry exemption on the installed license key. To learn how exemptions work, see Telemetry Exemption. Then use the following procedure.

1

Click Admin, License Keys.

2

Check whether the active key lists the Telemetry Exemption entitlement.

3

If the key doesn't list the exemption, contact your MongoDB account team. If your exemption was approved after you generated your key, generate a new key that includes it and install that key. For instructions, see Manage License Keys in Ops Manager.

4

Reload the Telemetry tab and turn off the Product Telemetry Collection toggle.

You can also generate and install a license key with the Administration API. For instructions, see Manage License Keys with the API.

If a banner appears on the Deployment pages, Ops Manager hasn't sent product usage telemetry to MongoDB for 8 or more days. To resolve the banner, work through the following steps.

1

Click Admin, General, Ops Manager Config, Telemetry. Check Last Successful Upload and Next Scheduled Upload. If Ops Manager was installed or upgraded less than seven days ago, the first send may not be due yet.

2

From each Ops Manager host, check that the host can open an HTTPS connection to cloud.mongodb.com on port 443.

3

Check /opt/mongodb/mms/logs/mms0.log for these messages:

Log message
Description
Resolution

Unable to send the product-usage-metrics payload.

The send to MongoDB failed. The entry includes the underlying error. Ops Manager keeps the unsent snapshot and retries it automatically.

Continue with the next step to fix connectivity.

Unable to collect the product-usage-metrics payload.

Ops Manager couldn't build the snapshot. The entry includes the underlying error. No snapshot was created; Ops Manager retries collection at the next scheduled run.

Check the same log entry for the underlying error.

Unable to read the license exemptions; treating usage telemetry as mandatory.

Ops Manager couldn't read the license key state, so it treats product usage telemetry as mandatory.

Verify that the license key is installed. If the message persists, contact your MongoDB account team.

Product-usage snapshot <id> delivered.

A send succeeded.

No action needed. The banner clears after a successful send.

The mms0.log file rolls over daily. The logs are compressed and kept for 30 days.

4

Fix any firewall, TLS-inspection, or proxy rule that blocks the connection.

5

Wait for the next job run, within six hours. Ops Manager retries unsent snapshots automatically, and the banner clears after a successful send.

6

If your environment can't send data outside your network, contact your account team about a telemetry exemption.