Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upmarathon unsupported protocol scheme or panic: runtime error: index out of range #1511
Comments
brian-brazil
added
the
bug
label
Mar 31, 2016
This comment has been minimized.
This comment has been minimized.
|
The code indicates that prepending the scheme was correct. What seems to be a problem is that the JSON returned from your marathon API doesn't specify any port for a task. Thus it panics. The access to the port should be checked to not throw a panic of course. |
fabxc
added this to the v1.0.0 milestone
Apr 25, 2016
fabxc
added
kind/bug
and removed
bug
labels
Apr 28, 2016
This comment has been minimized.
This comment has been minimized.
fretboarder
commented
Jun 3, 2016
|
I'm having the same problem with a Marathon instance that is accessible via https. A quick fix would be highly appreciated! |
brian-brazil
added
the
component/service discovery
label
Jun 15, 2016
This comment has been minimized.
This comment has been minimized.
|
The panic on missing port was fixed #1722 and is already in the latest release. |
fabxc
closed this
Jun 23, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
samek commentedMar 29, 2016
Hi,
since we've have a large amount of tasks in marathon first thing I wanted to try with prometheus was getting data out of marathon.
our marathon version is 0.15.2.
config
output
I've tried adding http in-front of each host where marathon runs
but the output is now
I've read that marathon is in beta for prometheus, which version is supposed to work ?
Thanks.