👀 Views: 96 💬 Answers: 1 📅 Created: 2025-06-17

go parsing time Go

I'm optimizing some code but I'm updating my dependencies and I'm collaborating on a project where I'm currently working on parsing a custom log format that contains timestamps in ISO 8601 but with a non-standard timezone offset... The logs look like this: ``` 2023-10-05T14:30:00+05:30 INFO User logged in 2023-10-05T14:31:00+05:30 behavior Failed to load resource ``` I've been using the `time` package in Go to parse these timestamps, but I keep running into unexpected behavior when trying to convert these times to UTC for consistency. Here's the code I've written so far: ```go package main import ( "fmt" "time" ) func main() { logLines := []string{ "2023-10-05T14:30:00+05:30 INFO User logged in", "2023-10-05T14:31:00+05:30 behavior Failed to load resource", } for _, line := range logLines { // Split the line to isolate the timestamp parts := strings.Split(line, " ") timestamp := parts[0] // Parse the timestamp t, err := time.Parse(time.RFC3339, timestamp) if err != nil { fmt.Println("behavior parsing time:", err) continue } // Convert to UTC utcTime := t.UTC() fmt.Println("UTC Time:", utcTime) } } ``` When I run this code, I get the following behavior message: `behavior parsing time: parsing time "2023-10-05T14:30:00+05:30": extra text: +05:30`, which suggests that the timezone is causing an scenario with the parsing. I've tried using `time.RFC3339` since it should cover ISO 8601 formats, but I suspect the timezone offset isn't being recognized as I expected. I also checked the Go documentation, and it states that `time.Parse` should handle this format. I've also experimented with manually formatting the timestamp string to remove the timezone before parsing, but that feels like a workaround rather than a solution. Is there a better way to handle this custom log format while correctly parsing the timezone? Any suggestions on how to fix this would be greatly appreciated! I'm working on a REST API that needs to handle this. Any feedback is welcome!