aws / aws/amazon-sagemaker-feedback

LastUserActivityTimestamp should not be updated by automatic Health Checks

Open
#54 2 comments 6 reactions 0 assignees View on GitHub
feature-request studio
Dominant language
No language data
Stars
10
Forks
3
PR merge metrics
No merged PRs in 30d

Description

### Product Version

- [ ] Amazon SageMaker Studio Classic
- [X] Amazon SageMaker Studio
- [ ] It is not related to SageMaker Studio

### Product Category

Other

### Description

The LastUserActivityTimestamp element of the DescribeApp API cannot be used to determine when a user interacted with an app for the last time because SageMaker also updates it when health checks are performed ([as documented](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_DescribeApp.html#API_DescribeApp_ResponseSyntax)).

This element should not be updated on health checks since there is another dedicated field for this specific purpose (LastHealthCheckTimestamp).

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the DescribeApp API documentation linked in the issue, comparing LastUserActivityTimestamp with LastHealthCheckTimestamp during automatic health checks. The issue is done when LastUserActivityTimestamp changes only after user interaction, while health checks update only LastHealthCheckTimestamp; no repository files or tests are identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
api, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.