Files
fn_registry/functions/infra/log_warn.md
T
egutierrez 47fac22230 chore: auto-commit (799 archivos)
- .claude/CLAUDE.md
- .claude/commands/subagentes.md
- .claude/rules/INDEX.md
- .mcp.json
- bash/functions/cybersecurity/analyze_dns.md
- bash/functions/cybersecurity/audit_http_headers.md
- bash/functions/cybersecurity/audit_ssh_config.md
- bash/functions/cybersecurity/check_firewall.md
- bash/functions/cybersecurity/detect_suspicious_users.md
- bash/functions/cybersecurity/encrypt_file.md
- ...

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-14 00:28:20 +02:00

1.5 KiB

name, kind, lang, domain, version, purity, signature, description, tags, uses_functions, uses_types, returns, returns_optional, error_type, imports, params, output, tested, tests, test_file_path, file_path
name kind lang domain version purity signature description tags uses_functions uses_types returns returns_optional error_type imports params output tested tests test_file_path file_path
log_warn function go infra 1.0.0 impure func LogWarn(logger *Logger, msg string, fields ...any) Emite un log a nivel warn en el Logger. Los fields son pares key-value variadicos. Indica situaciones anomalas que no impiden el funcionamiento del sistema.
logging
log
warn
slog
infra
pendiente-usar
Logger_go_infra
false error_go_core
name desc
logger Logger al que emitir el mensaje. Si es nil la funcion no hace nada
name desc
msg mensaje principal del log
name desc
fields pares key-value variadicos (ej: "retry_count", 3, "endpoint", "/api/users")
nada (side effect: escribe al Output del Logger) true
LogWarn emite nivel WARN
filtra mensajes debajo del nivel configurado
functions/infra/logger_test.go functions/infra/log_warn.go

Ejemplo

logger, _ := LoggerNew(LogLevelInfo, os.Stdout, "json")
LogWarn(logger, "retry attempt", "attempt", 2, "max", 5, "err", "timeout")
// {"time":"...","level":"WARN","msg":"retry attempt","attempt":2,"max":5,"err":"timeout"}

Notas

Funcion impura — delega a slog.Logger.Warn(). Usar para eventos recuperables: reintentos, fallos de cache, deprecaciones, datos inesperados pero no invalidos. Si el evento requiere intervencion humana usar LogError.