Structured logging in Go

golang
Always use structured logging with field-based approaches instead of string formatting when logging in Go.
Bad:
```go
logger.Info(fmt.Sprintf("User %s logged in from IP %s with status %d", username, ipAddress, statusCode))
```
Good:

Install this rule for wispbit

Add this rule to wispbit and it will run when you open a pull request

Install this rule for Coderabbit

Copy the configuration below and add it to your repository as .coderabbit.yml in your project root.

reviews:
  path_instructions:
    - path: "*.go"
      instructions: |
                
        Always use structured logging with field-based approaches instead of string formatting when logging in Go.
        
        Bad:
        
        ```go
        logger.Info(fmt.Sprintf("User %s logged in from IP %s with status %d", username, ipAddress, statusCode))
        ```
        
        Good:
        
        ```go
        logger.Info("User authentication",
            "username", username,
            "ip", ipAddress,
            "status", statusCode,
        )
        ```

Install this rule for Greptile

Greptile rules can be added through the web interface. Please see this documentation for details on how to add custom rules and context.

Always use structured logging with field-based approaches instead of string formatting when logging in Go.
Bad:
```go
logger.Info(fmt.Sprintf("User %s logged in from IP %s with status %d", username, ipAddress, statusCode))
```
Good:
```go
logger.Info("User authentication",
    "username", username,
    "ip", ipAddress,
    "status", statusCode,
)
```

File Path Patterns:

*.go

Install this rule for GitHub Copilot

Copilot instructions can be added through the interface. See the documentation for details on how to create coding guidelines.

Always use structured logging with field-based approaches instead of string formatting when logging in Go.
Bad:
```go
logger.Info(fmt.Sprintf("User %s logged in from IP %s with status %d", username, ipAddress, statusCode))
```
Good:
```go
logger.Info("User authentication",
    "username", username,
    "ip", ipAddress,
    "status", statusCode,
)
```

File Path Patterns:

*.go

Install this rule for Graphite Diamond

Diamond custom rules can be added through the interface. See the documentation for details on how to create custom rules.

Always use structured logging with field-based approaches instead of string formatting when logging in Go.
Bad:
```go
logger.Info(fmt.Sprintf("User %s logged in from IP %s with status %d", username, ipAddress, statusCode))
```
Good:
```go
logger.Info("User authentication",
    "username", username,
    "ip", ipAddress,
    "status", statusCode,
)
```

File Path Patterns:

*.go

Use with Cline

Copy the rule below and ask Cline to review your code using this rule

Always use structured logging with field-based approaches instead of string formatting when logging in Go.
Bad:
```go
logger.Info(fmt.Sprintf("User %s logged in from IP %s with status %d", username, ipAddress, statusCode))
```
Good:
```go
logger.Info("User authentication",
    "username", username,
    "ip", ipAddress,
    "status", statusCode,
)
```

Use with OpenAI Codex

Copy the rule below and ask OpenAI Codex to review your code using this rule

Always use structured logging with field-based approaches instead of string formatting when logging in Go.
Bad:
```go
logger.Info(fmt.Sprintf("User %s logged in from IP %s with status %d", username, ipAddress, statusCode))
```
Good:
```go
logger.Info("User authentication",
    "username", username,
    "ip", ipAddress,
    "status", statusCode,
)
```

Use with Cursor

Copy the rule below and ask Cursor to review your code using this rule

Always use structured logging with field-based approaches instead of string formatting when logging in Go.
Bad:
```go
logger.Info(fmt.Sprintf("User %s logged in from IP %s with status %d", username, ipAddress, statusCode))
```
Good:
```go
logger.Info("User authentication",
    "username", username,
    "ip", ipAddress,
    "status", statusCode,
)
```

Use with Claude Code

Copy the rule below and ask Claude Code to review your code using this rule

Always use structured logging with field-based approaches instead of string formatting when logging in Go.
Bad:
```go
logger.Info(fmt.Sprintf("User %s logged in from IP %s with status %d", username, ipAddress, statusCode))
```
Good:
```go
logger.Info("User authentication",
    "username", username,
    "ip", ipAddress,
    "status", statusCode,
)
```

Install this rule for Windsurf

To set up rules for Windsurf Reviews, please see this documentation 

Always use structured logging with field-based approaches instead of string formatting when logging in Go.
Bad:
```go
logger.Info(fmt.Sprintf("User %s logged in from IP %s with status %d", username, ipAddress, statusCode))
```
Good:
```go
logger.Info("User authentication",
    "username", username,
    "ip", ipAddress,
    "status", statusCode,
)
```