Context

INTPYTHON-530 set-up the django-mongodb-backend repo with performance monitoring. A Splunk alert was configured here based on the PyMongo alert here.

SPS only surfaces data pertaining to mainline commits to Splunk (implementation) and change points are only created when a "meaningful difference" is detected. Change points are also sensitive to the number of commits made and may occur retroactively.

A performance degradation was manually introduced (and later reverted) in PR #536 but did not surface any change points at the time. You can verify if a change point was made in the django-mongodb-backend project with the following Splunk query:

index="server-tig-prod"
(message="New change point detected." OR message="Change point h_score moved from -1 to a positive value.")
| spath output=project path="change_point.time_series_info.project"
| spath output=h_score path="change_point.h_score"
| search project="django-mongodb-backend"

Definition of done

Confirm surfacing of a Django Splunk alert in #dbx-python-perf-notifications

Pitfalls

N/A