Oct 14, 2025 - v1.95.1

Self-hosted

Bindplane v1.95.1 is the first v1.95 release.

Features:

• Bindplane now supports Postgres 17

• Enhanced Eventbus NATs and Pub/Sub Healthchecks

• Support multiple loggers

• Support OTLP logging

• New Statsig Destination

• New Transform Processor

• New Redact Sensitive Data Processor

  • Deprecated the Mask Sensitive Data processor

• New Processor Recommendation for Parse Severity by HTTP Status code

• Four new Blueprints for Palo Alto and Splunk logs

• Updated Google PubSub source type to support configurable text encoding when using raw_text

• Updated Cloudwatch source to support fractional poll intervals

Enhanced Event Bus Healthchecks

When using NATS or Google Pub/Sub Eventbus, Bindplane nodes periodically publish healthcheck events containing a list of known Bindplane servers. This list of servers is useful when debugging Eventbus configuration issues. It can used to prove that a server is receiving events from all servers.

Enable debug logging with logging.level: debug configuration option or BINDPLANE_LOGGING_LEVEL=debug environment variable.

The log will have logger: eventbus-health-manager key value pair as well as a list of hosts.

{
  "level": "debug",
  "timestamp": "2025-10-14T18:33:59.064Z",
  "logger": "eventbus-health-manager",
  "message": "received heartbeat from host",
  "hostname": "bindplane-nats-1",
  "time": "2025-10-14T18:33:59.063Z",
  "count": 10,
  "hosts": [
    "bindplane-nats-0",
    "bindplane-nats-1",
    "bindplane-nats-2",
    "bindplane-85b7b97d44-bk7nb",
    "bindplane-85b7b97d44-hsd44",
    "bindplane-85b7b97d44-txwcv",
    "bindplane-85b7b97d44-n8hnd",
    "bindplane-6dfd5b7cd9-zv6gg",
    "bindplane-85b7b97d44-pk8b7",
    "bindplane-jobs-6bc664bdb-xzxfv"
  ]
}

Multiple Loggers

Bindplane v1.95 supports multiple loggers. Users with file logger will not see much benefit, however, users of the new otlp logger are encouraged to combine otlp with stdout .

logging:
  type: stdout,file

OTLP Logging

Bindplane v1.95 supports logging to an OTLP gRPC endpoint. It is recommended to combine this logger with the stdout logger for local debugging using journalctl (Linux) or kubectl logs (Kubernetes).

logging:
  type: otlp,stdout
  otlp:
    endpoint: localhost:4317
    insecure: true
    interval: 1s

.