Deploy Sidecar Manually

[smeubank]

The first phase of our PoC we want to ensure there is a simple way to deploy relay as a sidecar with a PHP application manually

Problem Statement

We need to first evaluate the practicality and value of deploying a server side application with a sidecar. The potential value add during this phase is reduce round trip latency to call the sidecar application hosted next to the PHP application. Thereby hopefully increasing the capacity for high throughput applications.

Outcome

• simple set of instructions for a developer to deploy their app and the sidecar

  • need a new option to flag that the Sentry instrumented application is using a sidecar
    • can just be boolean flag

• Once this is done we begin to measure if we see performance gains

  • we can then evaluate investigating the value in finding ways to possibly deploy this more seamlessly and add more functionality to relay to support unique nature of PHP

For extra consideration:

• could add a test (kinda health check)
• extra tools to help users with setting it up
  • supervisor then copy these lines etc
  • docker OS level

[smeubank]

after the last sync: we agreed that for now an option for using local relay will not be moved on yet

& we will focus on ensuring the documentation and process for deploying relay for PHP is simple and clearly defined

PHP Performance: Getting Started

first thoughts, are that we do already outline the limitations and nature of PHP, maybe we could link to some external documentation/wiki with more info if that would be helpful to users

then already describe what realy could enable in the future with offloading logic to relay and enabling more Sentry functionality for more developers

• client reports
• higher throughput
• 429
• auto session

maybe i am forgetting something in this list, and maybe something in list is incorrect, but it's my first thoughts

[vladanpaunovic]

Given that in our docs we are currently asking users to manually set up their own Relay, I am closing this issue until we figure out how to better proceed here.