3 ms·

Would these tools still be useful in a cloud environment, such as EC2? Most dev teams I work with are actively reducing their actual managed server and replace

• mdekkers 3y ago
  > Most dev teams I work with are actively reducing their actual managed server and replace it with either Lambda, or docker images running in K8. There are plenty of services that don’t fit on k8s or Lambda. Not all pegs fit in those holes.
• yla92 3y ago
  It's still useful in EC2 (or any other VM-based environments) and Docker containers, as long as you can install the necessary packages (if they are not installed by default). Because after all, there are "servers" underneath, even for the serverless apps, I suppose. It's definitely harder for apps running in Lambda because we may not have access to the underlying OS. In such case, I kind of fallback to using the application level observability tools like Pyroscope (https://pyroscope.io https://pyroscope.io). It doesn't always work for all the cases and have some overheads/set up but it's still better than flying and more useful than the Cloud Provider's provided metrics.
• ranger207 3y ago
  IME there's always that one service that wasn't ever migrated to containers or lambdas is is off running on an EC2 somewhere, and nobody knows about it because it never breaks, but then the one time AWS schedules an instance retirement for it...
• cpuguy83 3y ago
  Containers are just processes running on the host where the process has a different view of the world from the "host". The host can see all and do all.