This repository has been archived by the owner on Jul 18, 2024. It is now read-only.
Add active debuggee support #76
Assignees
Comments
jasonborg
added a commit
to GoogleCloudPlatform/cloud-debug-java
that referenced
this issue
Dec 2, 2022
The Firebase client now adds two new fields to the Debuggee entry in the Firebase RTDB, `registrationTimeMsec` and `lastUpdateTimeMsec`. The first time the Debuggee entry is written to the RTDB, both fields are set. Thereafter only the `lastUpdateTimeMsec` will be changed, which is done periodically every hour when the agent is running continuously, it is also updated when the agent first starts up. This is in support of GoogleCloudPlatform/snapshot-debugger#76.
jasonborg
added a commit
to GoogleCloudPlatform/cloud-debug-java
that referenced
this issue
Dec 5, 2022
The Firebase client now adds two new fields to the Debuggee entry in the Firebase RTDB, `registrationTimeMsec` and `lastUpdateTimeMsec`. The first time the Debuggee entry is written to the RTDB, both fields are set. Thereafter only the `lastUpdateTimeMsec` will be changed, which is done periodically every hour when the agent is running continuously, it is also updated when the agent first starts up. This is in support of GoogleCloudPlatform/snapshot-debugger#76.
jasonborg
added a commit
that referenced
this issue
Dec 8, 2022
In support of #76 the `list_debuggees` command now: - Shows only active debuggees by default - Supports a `--include-inactive` flag - Sorts the output with the most recently active debuggees being shown first.
jasonborg
added a commit
that referenced
this issue
Dec 9, 2022
In support of #76 the `list_debuggees` command now: - Shows only active debuggees by default - Supports a `--include-inactive` flag - Sorts the output with the most recently active debuggees being shown first.
|
This is now complete and released in v0.3.0 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To support active debuggees, we need to add timestamp fields to Debuggees.
Two new fields will be required, which will be set/updated by the agents:
The Agents when registering for the first time for a given debuggee ID will need to first perform a read from the DB to see if this is the first time a Debuggee is being registered or not. For simple re-registrations the
lastUpdateTimeMsecwould only need to be updated. The agents would be responsible for ensuring to periodically updatelastUpdateTimeMsecas well so the Debuggee will remainactive.The CLI
list_debuggeescommand will make use of these timestamps to only list the active debuggees by default.The text was updated successfully, but these errors were encountered: