Understand which external sites are posting to /newsletter/

[alexgibson]

Description

We have a URL/view here that allows signing up to newsletters. Bedrock is no longer using this view itself as pages now POST directly to Basket instead, however some external sites may still be using it. The form on https://foundation.mozilla.org/en/ is one such example.

We need to understand if there are any more external sites still posting to this URL. Can we do this via logging? Once we have a list, we can do some outreach to help them to POST directly to Basket instead.

---

Success Criteria

• List of sites that are still actively using the /newsletter/ endpoint.

[alexgibson]

/cc @pmac

[pmac]

We can probably get pretty far loggin the source_url values that come through. The question is where to log this info so that we can extract it. We can just spit it out into the app logs and use our log viewer to search for the values, but I think our retention of those logs is very short.

@stevejalim @robhudson any ideas?

[robhudson]

If we may need things like this frequently can we use Grafana + statsd like we do in basket? I think it would be interesting to wire up more metrics to get some extra insight into bedrock.

[pmac]

we used to have that but the move to prometheus messed us up a bit. We could do a similar thing to what we do for basket, which is to run a statsd collector that outputs the prometheus stats that can be consumed by grafana. We tried having bedrock output these settings but ran into issues due to the multiple processes outputting their own stats and managing discovery of all the pods in all of the locations. We should talk to @bkochendorfer about it.