turbo

##################
#    Services    #
##################

services:
  # Service:        Telegraf
  # Purpose:        Data collection agent
  # Documentation:  https://docs.influxdata.com/telegraf
  telegraf:
    image: telegraf

turbo

##################
#   Extensions   #
##################

x-influxlog: &influxlog
  logging:
    driver: syslog
    options:
      syslog-address: "udp://localhost:514"
      tag: "{{.ImageName}}"

turbo

##################
#    Networks    #
##################

networks:
  traefik-net:
    external: true
  tick-net:
    driver: overlay

turbo

#################
#    Configs    #
#################

configs:
  telegraf-config:
    external: true
  kapacitor-config:
    external: true

turbo

##################
#    Networks    #
##################

networks:
  traefik-net:
    external: true
  tick-net:
    driver: overlay

turbo

#################
#    Volumes    #
#################

volumes:
  influxdb:
    external: true
  chronograf:
    external: true
  kapacitor:

turbo

# Read metrics about CPU usage
[[inputs.cpu]]
  percpu = false
  totalcpu = true
  fieldpass = [ "usage*" ]
  name_suffix = "_vm"

# Read metrics about disk usagee
[[inputs.disk]]
  fielddrop = [ "inodes*" ]

turbo

hostname = "kapacitor"
data_dir = "/var/lib/kapacitor"

[http]
  # HTTP API Server for Kapacitor
  # This server is always on,
  # it serves both as a write endpoint
  # and as the API endpoint for all other
  # Kapacitor calls.
  bind-address = ":9092"

turbo

Packages

• protobuf-net 2.3.17
• Jil 2.16.0
• JetBrains.Annotations 2018.2.1

Code

using System;

turbo

/*
 * In ESP 12 modules, spec. D1 Mini mounted, GPIO9 and GPIO10 can sort of be freed up.
 * GPIO9 is connected to flash HOLD
 * GPIO10 is connected to flash WP
 * 
 * In DIO mode, these pins should be free, but remain connected to the flash chip.
 * Using GPIO9 will crash the module sooner or later, GPIO10 is relatively safe, but
 * don't fuzz it. Might be good enough for SPI CS or similar, no data rates pl0x.
*/