Ver feed de atividades

O Atlas Organization Activity Feed exibe eventos selecionados que ocorreram para uma determinada organização do Atlas , como faturamento ou eventos de acesso.

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.

Acesso necessário

Para visualizar o Feed de atividades da organização, você deve ter pelo menos Organization Member acesso à organização.

Para visualizar o Feed de atividades do projeto, você deve ter pelo menos Project Read Only acesso ao projeto.

Veja o feed de atividades

Selecione o tipo de feed de atividades e como você gostaria de acessar os eventos.

Tipo de feed de atividades

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.

Isole a atividade específica do usuário com filtros de auditoria personalizados

Importante

In the updated Data Explorer interface, the Project Activity Feed no longer generates individual entries for CRUD operations or regular index builds. When you access a collection through Data Explorer, the Project Activity Feed records only the following entries, which include the Atlas username:

user connections when you open Data Explorer
A single listIndexStats entry when you access a collection, regardless of how many read or write operations you perform within that collection

To track additional user activity, 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" }

Por exemplo, você pode criar um filtro de auditar personalizado semelhante ao seguinte:

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

Para saber mais sobre registros de auditar e analisar exemplos específicos de filtros de função, consulte Configurar filtro de auditoria.

Voltar

Equipes

Configurações