Heap Dump Management

As the filesystem in Kubernetes pods is not directly accessable we developed a sidecar approach where written heap dumps are collected and stored in an encrypted format on a central S3 Bucket per cluster.

This approach consists of 3 parts:

• heap dump service
• notify sidecar
• heap dump companion

Please read the individual documentation to understand the individual parts.
This architectual overview should help to understand the interactions in between the components

Maintainers

This project is maintained by:

• Tobias Trabelsi (tobias.trabelsi+github@dbschenker.com)