dcos/dcos-signal

Name: dcos-signal

Owner: DC/OS

Description: The signal service is a passive data forwarding service for telemetry and analytics gathering. The signal service acts as a middleware which runs GET requests to 3DT, Mesos, and Cosmos on masters on a systemd timer.

Created: 2016-04-13 20:04:35.0

Updated: 2018-05-16 15:37:32.0

Pushed: 2018-01-19 18:55:07.0

Homepage:

Size: 219

Language: Go

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

DCOS Signal Service

The signal service is a passive data forwarding service for telemetry and analytics gathering. The signal service acts as a middleware which runs GET requests to 3DT, Mesos, and Cosmos on masters on a systemd timer.

SegmentIO Library Used

SegmentIO

Build

 build

Run

You can run an example with the `run` script:

-signal

This will query a running 3DT environment and post the results to segmentIO.

Test

Unittest:

 test

Integration test locally:

at -lk 4444 &
un dcos_signal.go -v -test-url http://localhost:4444

Integration test in an actually integrated scenario:

myuser@mymaster.com
at -lk 4444 &
os_signal -v -test-url http://localhost:4444

CLI Arguments

Usage:
  -c                string | Path to dcos-signal-service.conf. (default "/opt/mesosphere/etc/dcos-signal-config.json")

  -cluster-id-path  string | Override path to DCOS anonymous ID. (default "/var/lib/dcos/cluster-id")

  -segment-key      string | Key for segmentIO.

  -test-url         string | URL to send would-be SegmentIO data to as JSON blob.

  -v                  bool | Verbose logging mode.

  -version            bool | Print version and exit.