Closed samek closed 8 years ago
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. Generally, why does your task not specify a port. Is this expected behavior in the Marathon API? What would be a proper default port to chose?
I'm having the same problem with a Marathon instance that is accessible via https. A quick fix would be highly appreciated!
The panic on missing port was fixed #1722 and is already in the latest release.
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.
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.