-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Endpoint metrics are not displayed #6712
Comments
Hi @Infusible! Thanks for reporting this... I've been especially on the look out for Windows issues recently! It looks like your configuration is correct; the |
@tgross I use |
For example my job, this work is different from the one shown in the screenshot, but the result is the same - there are no metrics. My job definition, I use the simplest setting of the job
|
@tgross any update? |
@Infusible we'll let you know when we've had a chance to investigate. In the meantime, linking to #6349 which may be related. |
thank you) |
Hey @Infusible just a heads up that I've verified that #6349 is working (on the soon-to-be-released 0.10.2). Here's my test outputs: Test jobRunning Docker containers on Windows 2016 is pretty painful b/c there's no support for Linux containers and most of the various public images MSFT publishes are for 2019. job "winsleep" {
datacenters = ["dc1"]
type = "service"
group "sleepy_win" {
count = 1
restart {
attempts = 10
interval = "5m"
delay = "25s"
mode = "delay"
}
constraint {
attribute = "${attr.kernel.name}"
operator = "="
value = "windows"
}
task "sleepy" {
driver = "docker"
config {
image = "mcr.microsoft.com/windows/servercore:ltsc2016"
command = "powershell"
args = ["-command", "Start-Sleep", "-s", "600"]
}
resources {
cpu = 500
memory = 256
}
}
}
} Client metrics
Allocation metrics
|
hi @tgross |
Oh, good catch! Just checked that and we're looking good for the raw_exec test jobjob "infusible" {
datacenters = ["dc1"]
type = "service"
group "infusible" {
count = 1
constraint {
attribute = "${attr.kernel.name}"
operator = "="
value = "windows"
}
task "infusible" {
driver = "raw_exec"
config {
command = "powershell"
args = ["-command", "Start-Sleep", "-s", "600"]
}
}
}
} Allocation metrics
|
and you job used null - memory=0 it is impossible |
i will check on version 0.10.2 |
Bah, that's my fault... I wasn't paying close enough attention. But that's a slightly different problem than I thought we were facing -- Nomad is exposing the metrics it has but not collecting them properly. |
Yeah, I think that was just a bad test; the whole point of "sleep" is that it doesn't use any resources. I ran a quick golang application that does CPU-intensive prime numbers searching instead and got good results:
|
golang app runned on driver = raw_exec? |
Yup! |
i will check on version 0.10.2 and comment on this issue |
I'm going to close this as part of tracking our 0.10.2 completion. We expect to cut the release very soon. Feel free to re-open this if you find that 0.10.2 doesn't solve the problem. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
nomad version: 0.9.3
Operating system and Environment details
server: ubuntu 16
client: windows server 16
Issue
telemetry settings for windows apps
Reproduction steps
run my job and it ran, but not metrics
config my client
https://www.nomadproject.io/docs/telemetry/metrics.html
and my metrics = ZERO
what should you do to get these metrics to appear?
The text was updated successfully, but these errors were encountered: