Data Source Heartbeat Monitoring
L
Leo Sivak
Port currently lacks a heartbeat functionality for data sources. This makes it difficult to distinguish between active data sources with functioning exporters and those without proper configuration or deployment. We propose implementing a heartbeat feature to address this issue.
Proposal:
- Implement a heartbeat mechanism for Port data sources.
- Data sources will send periodic heartbeat signals to Port.
- Port will monitor these heartbeat signals.
- Port will display the active/inactive status of data sources based on heartbeat reception.
Benefits:
- Clear visibility of data source status (active vs inactive)
- Easy identification of data sources with deployment or configuration issues
- Improved data source management and maintenance
- Enhanced system reliability and troubleshooting
This feature will enable users to quickly identify inactive data sources, allowing them to either remove them from Port or address exporter deployment issues, thus improving overall system health and data accuracy.
Matan Grady
Merged in a post:
Ocean - Indicate when the Pod is failing / disconnected from Port
Matar Peles
Today it is not possible to understand the health of your deployment when installing Ocean on K8s, so it would be helpful to have an indication in the UI of Port for whenever the integration is disconnected and not syncing the portal.
Matan Grady
open
Aidan O'Connor
In addition to this, it would be ideal to have a centralized audit log for all data sources. Currently, Port builders must go into the audit log for each data source (can be overwhelming with many data sources) or go to the general audit log (where data source issues might get drowned out by other audit log items)