View Activity Feed

The Atlas Organization Activity Feed displays select events that occurred for a given Atlas organization, such as billing or access events.

The Atlas Project Activity Feed provides more granular detail about the state of your cluster. The Project Activity Feed displays select events that occurred for a given Atlas project, such as auto-scaling changes to a minimum or maximum cluster tier, log export status changes, and integration lifecycle events.

Required Access

To view the Organization Activity Feed, you must have at minimum Organization Member access to the organization.

To view the Project Activity Feed, you must have at minimum Project Read Only access to the project.

View the Activity Feed

Select the activity feed type and how you would like to access events.

Activity Feed Type

Interface

Activity Feed Event Types

For a complete list of all event types that appear in the Activity Feed, see Atlas Alert Event Types.

The following event types are specific to log export:

Log export has failed. Check your integration settings and credentials.
Log export is failing after multiple attempts. Logs are being queued and will be sent once the connection is restored.
Log export replay has failed to deliver records to an external platform, even after an automatic replay attempt. These records will be permanently deleted once their retention window expires. Contact MongoDB Support to request redelivery.
Log export has recovered. Queued logs are ready to resume sending.
Log export has recovered. Queued logs are now being sent.
All queued logs have been delivered to sink.

Isolate User-Specific Activity with Custom Audit Filters

Important

In the updated Data Explorer interface, the Project Activity Feed no longer logs the usernames of Atlas users when they read or modify data. Although the Project Activity Feed no longer logs usernames, it continues to log user connections from the Atlas UI to a cluster.

To track user activity, you can use database audit logs and create custom audit filters that isolate user activity associated with the following system-generated Administrator roles unique to Data Explorer:

{ role: "atlasDataAccessReadWrite", db: "admin" }
{ role: "atlasDataAccessReadOnly", db: "admin" }
{ role: "atlasDataAccessAdmin", db: "admin" }

For example, you could create a custom audit filter similar to the following:

{
  "roles": {
    "$elemMatch": {
      "$or": [
        {
          "role": "atlasDataAccessReadWrite",
          "db": "admin"
        },
        {
          "role": "atlasDataAccessReadOnly",
          "db": "admin"
        },
        {
          "role": "atlasDataAccessAdmin",
          "db": "admin"
        }
       ]
      }
     }
    }

To learn more about audit logs and review specific examples of role filters, see Configure Audit Filter.

Back

Teams

Settings