review(monitoring.proto): use google.protobuf.Timestamp instead of int64 #67

Closed
opened 2026-03-28 04:20:56 +00:00 by mfreeman451 · 1 comment
Owner

Imported from GitHub.

Original GitHub issue: #159
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/159
Original created: 2025-01-31T07:52:47Z


Consider using google.protobuf.Timestamp for timestamps instead of int64 to provide more semantic meaning. This would require updating how timestamps are handled in the Go code.

Imported from GitHub. Original GitHub issue: #159 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/159 Original created: 2025-01-31T07:52:47Z --- Consider using google.protobuf.Timestamp for timestamps instead of int64 to provide more semantic meaning. This would require updating how timestamps are handled in the Go code.
Author
Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/159#issuecomment-3813972631
Original created: 2026-01-28T21:15:34Z


closing, stale

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/159#issuecomment-3813972631 Original created: 2026-01-28T21:15:34Z --- closing, stale
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carverauto/serviceradar#67
No description provided.