You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I’ve stumbled across 2 issues where both help articles recommended configuring a proxy server for DD logs. However, the documentation surrounding what is required for the proxy server/service is somewhat lacking.
Describe the solution you'd like
I would like some more clear documentation about provisioning a serverless (Lambda) proxy server. Additionally, Adding something similar to the documentation for configuring the DataDog Forwarder CloudFormation templates wwould be ideal.
Describe alternatives you've considered
An alternative that would be acceptable would be custom domains to prevent CORS issues or network filters/tracking blockers.
The text was updated successfully, but these errors were encountered:
Feel free to reach out to our awesome support team - they can definitely help you get this sorted out. The Serverless engineering team is also super responsive on our Datadog public slack. We'll also look at updating the documentation, but these other channels can help with your specific problem sooner.
Is your feature request related to a problem? Please describe.
I’ve stumbled across 2 issues where both help articles recommended configuring a proxy server for DD logs. However, the documentation surrounding what is required for the proxy server/service is somewhat lacking.
References:
Missing Data in RUM
Cross origin read blocking warning
Describe the solution you'd like
I would like some more clear documentation about provisioning a serverless (Lambda) proxy server. Additionally, Adding something similar to the documentation for configuring the DataDog Forwarder CloudFormation templates wwould be ideal.
Describe alternatives you've considered
An alternative that would be acceptable would be custom domains to prevent CORS issues or network filters/tracking blockers.
The text was updated successfully, but these errors were encountered: