Skip to content

Easily grab task/container stdout/err logs from Mesos regardless of the slave it's running on

License

Notifications You must be signed in to change notification settings

ContainX/go-mesoslog

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

21 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Go-Mesoslog

Build Status

Overview

Go-Mesoslog makes it easy to grab StdOut and StdErr logs from any task. It allows you to find logs using the name of the task without the UUID portion. Go-Mesoslog locates the logs via the master and then downloads the desired log from the allocated slave.

Usage

go-mesoslog [global_flags] [action] <action_flags>
Actions
  list                      - List current application id's and task count (instances running)
  print [appId]             - Outputs the log for the given [appId] to StdOut.  Each running instance log will be outputed
  tail [appId]              - Tails the log from the given [appId] to StdOut.  All instances are part of the tail
  file [appId] [targetDir]  - Outputs the log for the given [appId] to a files in the [targetDir] prefixed with the instance TaskID
  help                      - Help about any cmmand

Global Flags
  -m, --master :            - Mesos Master host:port (eg. 192.168.2.1:5050)

Binary Installation

Binaries are available through GitHub releases. You can download the appropriate binary, package and version from the Releases page

Build and Install the Binaries from Source

Add Go-Mesoslog and its package dependencies to your go src directory

go get -v github.com/ContainX/go-mesoslog

Once the get has completed, you should find your new go-mesoslog (or go-mesoslog.exe) executable sitting inside the $GOPATH/bin/

To update Go-Mesoslog's dependencies, use go get with the -u option.

go get -u -v github.com/ContainX/go-mesoslog

Why Go-Mesoslog

Ideally in your larger clusters you should be log forwarding via Syslog, GELF, FluentD, etc but for smaller deployments where this isn't setup such as DEV or TEST environments this offers a quick view without exposing all of your cluster characteristics to the teams.

I wrote this quickly in one night to solve a few use cases. Feel free to fork and contribute!

Looking for Mesos/Marathon, Kubernetes or ECS deployment in one tool?

Checkout depcon

License

This software is licensed under the Apache 2 license, quoted below.

Copyright 2016 ContainX / Jeremy Unruh

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

About

Easily grab task/container stdout/err logs from Mesos regardless of the slave it's running on

Resources

License

Stars

Watchers

Forks

Packages

No packages published