loglayer.dev valid
LogLayer for Go
Transport-agnostic structured logging for Go. A fluent API on top of zerolog, zap, logrus, phuslu/log, charmbracelet/log, log/slog, OpenTelemetry, or any custom transport. Module path: `go.loglayer.dev/v3`. GitHub: `github.com/loglayer/loglayer-go`.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T18:51:19.506Z. Cached copy · Source on loglayer.dev
# LogLayer for Go
> Transport-agnostic structured logging for Go. A fluent API on top of zerolog, zap, logrus, phuslu/log, charmbracelet/log, log/slog, OpenTelemetry, or any custom transport. Module path: `go.loglayer.dev/v3`. GitHub: `github.com/loglayer/loglayer-go`.
## Installation
```sh
go get go.loglayer.dev/v3
```
Most transports and plugins ship as their own modules. Install only what you import:
```sh
go get go.loglayer.dev/transports/structured/v3
go get go.loglayer.dev/transports/zerolog/v3
go get go.loglayer.dev/plugins/redact/v3
```
## Quick Start
```go
package main
import (
"go.loglayer.dev/v3"
"go.loglayer.dev/transports/structured/v3"
)
func main() {
log := loglayer.New(loglayer.Config{
Transport: structured.New(structured.Config{}),
})
log.Info("hello world")
}
```
## Log Levels
Seven levels, in priority order:
```go
log.Trace("detailed debugging")
log.Debug("debug information")
log.Info("informational message")
log.Warn("warning message")
log.Error("error occurred")
log.Fatal("critical failure") // dispatches then calls os.Exit(1) unless DisableFatalExit
log.Panic("unrecoverable") // dispatches then panics with the joined message string
// Multiple values join with a space
log.Info("user", 123, "logged in")
```
## Metadata (per-message data)
Data attached to a single log entry only.
```go
// Map-style metadata nests under the "metadata" key (MetadataFieldName default)
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| logtide.dev | LogTide | interface Cybersecurity DevOps and observability +1 | — | 46 | ✓ | ✓ | |
| controltheory.com | ControlTheory | documentation DevOps and observability Developer tools | — | 46 | ✓ | ✓ | |
| datalust.co | Seq | interface DevOps and observability Developer tools | — | 50 | ✓ | ||
| fluentd.org | Fluentd | documentation DevOps and observability Open source projects | CA | 60 | ✓ | ||
| signoz.io | SigNoz | documentation DevOps and observability Open source projects | US | 55 | ✓ | ✓ | |
| last9.io | Last9 | documentation DevOps and observability Documentation and reference | US | 54 | ✓ | ✓ | |
| maple.dev | Maple | documentation DevOps and observability | US | 55 | ✓ | ✓ | |
| appsignal.com | AppSignal Documentation | documentation DevOps and observability Documentation and reference | — | 63 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=loglayer.dev · GET /v1/domain/loglayer.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage loglayer.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for loglayer.dev:
1. POST https://agentwebmap.com/v1/sites/loglayer.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://loglayer.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/loglayer.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/loglayer.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.