Getting started

Where to send your logs

Every instance gets a stable, per-tenant ingestion endpoint behind the managed gateway. Use it as your Seq server URL — it speaks native Seq ingestion over HTTPS (port 443), so no client library changes are needed.

API keys are managed natively in Seq (filters, level overrides, quotas all work). Replace the example host with your instance’s endpoint from the portal.

Serilog

Install the Seq sink, then write to your endpoint with an API key.

# Package
dotnet add package Serilog.Sinks.Seq

using Serilog;

Log.Logger = new LoggerConfiguration()
    .WriteTo.Seq(
        serverUrl: "https://acme-prod.in.us1.seqhost.net",
        apiKey: "<your-api-key>")
    .CreateLogger();

Log.Information("Hello from {App} on SEQHost", "my-service");

Dynamic level control works as if self-hosted — Serilog reads MinimumLevelAccepted back from the gateway’s ingest responses.

NLog

Add the Seq target package and configure a target in nlog.config.

<!-- nlog.config -->
<extensions>
  <add assembly="NLog.Targets.Seq" />
</extensions>

<targets>
  <target name="seq" xsi:type="Seq"
          serverUrl="https://acme-prod.in.us1.seqhost.net"
          apiKey="<your-api-key>" />
</targets>

<rules>
  <logger name="*" minlevel="Info" writeTo="seq" />
</rules>

OpenTelemetry (OTLP)

Seq ingests OTLP logs directly. Point your OTLP exporter at the endpoint’s /ingest/otlp/v1/logs path and pass the API key as a header.

# Environment variables (any OTLP SDK)
OTEL_EXPORTER_OTLP_LOGS_ENDPOINT=https://acme-prod.in.us1.seqhost.net/ingest/otlp/v1/logs
OTEL_EXPORTER_OTLP_LOGS_HEADERS=X-Seq-ApiKey=<your-api-key>
OTEL_EXPORTER_OTLP_LOGS_PROTOCOL=http/protobuf

Traces and metrics export is on the roadmap — log signals first.

seqcli

Datalust’s CLI works unchanged — handy for shipping a quick log or scripting against your instance.

# Send a one-off event
echo 'Deploy {Version} finished' | seqcli ingest \
  --server=https://acme-prod.in.us1.seqhost.net \
  --apikey=<your-api-key> \
  --property=Version=1.4.0