Python (Django) Setup

🚧

Any issues?

Integrations can be tricky! Contact support if you have any questions/issues.

Overview

If you're a developer, it takes a few small steps to send your API logs to ReadMe so your team can get deep insights into your API's usage with ReadMe Metrics. Here's an overview of how the integration works:

• You install the ReadMeMetrics Django Middleware and configure your Django app to use it.
• You write a grouping function, which is used to tie each API request to the user or API key that initiated the request.
• The middleware will send to ReadMe the request and response objects that your server generates each time a user makes a request to your API. The entire objects are sent, unless you deny or allow specific keys from the request.
• ReadMe extracts information to display in Metrics, such as which endpoint is being called, response code, and error messages. It also identifies the customer who called your API, using the data returned by your grouping function.

Steps

1. From the directory of your codebase, run the following command in your command line to install the Django variant of the readme-metrics package from pypi. You can also add this to your requirements.txt file.

pip install "readme-metrics[Django]"

2. In your codebase, write a grouping function to inform ReadMe of the user or API key holder that is responsible for a given request. The grouping function receives the current Django WSGIRequest object as input, and should return a data structure describing the current user or API key holder. A basic grouping function would look like this:

def grouping_function(request):
    # You can lookup your user here, pull it off the request object, etc.
    # Your grouping function should return None if you don't want the request
    # to be logged, and otherwise return a structure like the one below.
    if user_is_authenticated:
        return {
            "api_key": "unique api_key of the user",
            "label": "label for us to show for this user (account name, user name, email, etc)",
            "email": "email address for user"
        }
    else:
        return None

3. Add a README_METRICS_CONFIG setting to your Django settings.py file, using the MetricsApiConfig helper object:

from readme_metrics import MetricsApiConfig

README_METRICS_CONFIG = MetricsApiConfig(
    api_key="<<user>>",
    grouping_function="module.path.to.your.grouping_function"
)

The MetricsApiConfig object takes the following parameters:

• Your ReadMe API Key. If you're logged in to these docs, this string is automatically populated in the preceeding code.
• A function that takes the Request object and returns a dict describing the user, or None if the request should not be logged
• Additional options: see details below

4. Add our MetricsMiddleware to your list of middleware, also in your app's settings.py file:

MIDDLEWARE = [
    ...,
    "readme_metrics.django.MetricsMiddleware",
    ...
]

Identifying the API Caller

There are three fields that you can use to identify the user making the API call. We recommend passing all three to make API Metrics as useful as possible.

Configuration Options

There are a few options you can pass in to change how the logs are sent to ReadMe. These are passed in as parameters to the MetricsApiConfig constructor.

README_METRICS_CONFIG = MetricsApiConfig(
    api_key="<<user>>",
    grouping_function=path.to.your.grouping_function,
    buffer_length=1,
    background_worker_mode=False,
    allowlist=["city", "state", "postal_code", "country"],
    timeout=15
)