Babu Srinivasan

Abilash Ravikumar

[Datadog](https://www.datadoghq.com/) is a well-known monitoring and security platform for cloud applications. Datadog’s software-as-a-service (SaaS) platform integrates and automates infrastructure monitoring, application performance monitoring, and [log management](https://docs.datadoghq.com/logs/log_collection/) to provide unified, real-time observability of a customer’s entire technology stack.

MongoDB Atlas on Amazon Web Services (AWS) already supports [easy integration with Datadog](https://www.mongodb.com/docs/atlas/tutorial/datadog-integration/) for alerts and events right within the Atlas UI (select the three vertical dots → Integration → Datadog). With the Log Forwarding feature, it's now possible to send Atlas Application Services logs to Datadog. This blog outlines the configuration steps necessary as well as strategies for customizing the view to suit the need.

![Datadog Configuration from Atlas ](https://mongodb-devhub-cms.s3.us-west-1.amazonaws.com/datadog_configuration_atlas_00347e84a6.png)

[**Atlas Application Services**](https://www.mongodb.com/docs/atlas/app-services/) (formerly MongoDB Realm) is a set of enhanced services that complement the Atlas database to simplify the development of backend applications. App Services-based apps can react to changes in your MongoDB Atlas data, connect that data to other systems, and scale to meet demand without the need to manage the associated server infrastructure.

App Services provides user authentication and management, schema validation and data access rules, event-driven serverless functions, secure client-side queries with GraphQL, and best of all, synchronization of data across devices with the Realm Mobile SDK.

With App Services and Datadog, you can simplify the end-to-end development and monitoring of your application. **Atlas App Services** specifically enables the forwarding of logs to Datadog via a serverless function that can also give more fine-grained control over how these logs appear in Datadog, via customizing the associated tags.

## Atlas setup

We assume that you already have an Atlas account. If not, you can sign up for a [free account](https://www.mongodb.com/realm/register) on MongoDB or the [AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-pp445qepfdy34). Once you have an Atlas account, if you haven't had a chance to try App Services with Atlas, you can follow one of our [tutorials](https://www.mongodb.com/docs/atlas/app-services/tutorials/) to get a running application working quickly.

To initiate custom log forwarding, follow the instructions for App Services to configure [log forwarding](https://www.mongodb.com/docs/atlas/app-services/logs/forward-logs/). Specifically, choose the “To Function” option:

![MongoDB Atlas Log configuration](https://mongodb-devhub-cms.s3.us-west-1.amazonaws.com/mongodb_atlas_log_configuration_1f15e0de05.png)

Within Atlas App Services, we can create a custom function that provides the mapping and ingesting logs into Datadog. Please note the intake endpoint URL from Datadog first, which is [documented by Datadog](https://docs.datadoghq.com/logs/log_collection/?tab=host).

Here’s a sample function that provides that basic capability:

```
exports = async function(logs) {
  // `logs` is an array of 1-100 log objects
  // Use an API or library to send the logs to another service.
  await context.http.post({
    url: "https://http-intake.logs.datadoghq.com/api/v2/logs",
    headers: {
      "DD-API-KEY": ["XXXXXX"],
      "DD-APPLICATION-KEY": ["XXXXX"], 
      "Content-Type": ["application/json"]
    },
    body: logs.map(x => {return {
      "ddsource": "mongodb.atlas.app.services",
      "ddtags": "env:test,user:igor",
      "hostname": "RealmApp04",
      "service": "MyRealmService04",
      "message" : JSON.stringify(x)
    }}),
    encodeBodyAsJSON: true
  });
}
```

One of the capabilities of the snippet above is that it allows you to modify the function to supply your Datadog [API and application keys](https://docs.datadoghq.com/account_management/api-app-keys/). This provides the capability to customize the experience and provide the appropriate context for better observability. You can change [ddtags](https://docs.datadoghq.com/getting_started/tagging/), the hostname, and service parameters to reflect your organization, team, environment, or application structure. These parameters will appear as facets helping with filtering the logs.

Note: Datadog supports log ingestion pipelines that allow it to better parse logs. In order for the MongoDB log pipeline to work, your *ddsource* must be set to `mongodb.atlas.app.services`.

![Select the MongoDB as a source in Datadog](https://mongodb-devhub-cms.s3.us-west-1.amazonaws.com/select_mongodo_source_datadog_c9abd3a85a.png)

## Viewing the logs in Datadog

Once log forwarding is configured, your Atlas App Services logs will appear in the Datadog Logs module.

![Datadog Logs](https://mongodb-devhub-cms.s3.us-west-1.amazonaws.com/datadog_logs_73ed6659cd.png)

You can click on an individual log entry to see the detailed view:

![Datadog Event Attributes](https://mongodb-devhub-cms.s3.us-west-1.amazonaws.com/datadog_event_attributes_d4d8228ed3.png)

## Conclusion

In this blog, we showed how to configure log forwarding for Atlas App Services logs. If you would like to try configuring log forwarding yourself, sign up for a [14-day free trial of Datadog](https://www.datadoghq.com/free-datadog-trial/) if you don’t already have an account. To try Atlas App Services in AWS Marketplace, sign up for a [free account](https://aws.amazon.com/marketplace/pp/prodview-pp445qepfdy34).

With the Log Forwarding feature, it's now possible to send Atlas Application Services logs to Datadog. This blog outlines the configuration steps necessary as well as strategies for customizing the view to suit the need.

Abilash Ravikumar

Content by Abilash Ravikumar

Integrate Atlas Application Services Logs into Datadog on AWS