# Display last device connection timestamp independently of measurements **URL:** \ **Category:** Forum\ **Tags:** device-connectivity, cumulocity\ **Created:** [November 6, 2024, 10:32am UTC](https://community.cumulocity.com/t/display-last-device-connection-timestamp-independently-of-measurements/7777 "2024-11-06T10:32:00Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Stefan\_Witschel](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/stefan_witschel/32/31955_2.png) [@Stefan\_Witschel](https://community.cumulocity.com/u/Stefan_Witschel)\ **Post date:** [November 6, 2024, 11:30am UTC](https://community.cumulocity.com/t/display-last-device-connection-timestamp-independently-of-measurements/7777/3 "2024-11-06T11:30:20Z")
Check your code and add the Header Korbinian mentioned to ignore the requests for the device connectivity status. > [@Microservices Best Practices: Updating Device Connectivity Status with Java SDK](https://community.cumulocity.com/t/microservices-best-practices-updating-device-connectivity-status-with-java-sdk/491): > > Overview As you might have read in the [Microservice Best Practices: Getting Started](https://community.cumulocity.com/t/microservice-best-practices-getting-started/4392) article already, Microservices can be used to implement multiple patterns. One of the most used patterns for Cumulocity IoT is the server-side device agent which retrieves/fetches data from devices, maps it to the Cumulocity IoT Domain model, and implements the REST Open API to transport the data to Cumulocity. When updating the device connectivity status with a microservice this often leads to the case that t… --- _[View the full topic](https://community.cumulocity.com/t/display-last-device-connection-timestamp-independently-of-measurements/7777)._