Doing a little more digging...

When running on minikube, I'm seeing Prometheus restart every time a request is sent to the zipkin server:

level=warn ts=2018-05-24T19:07:07.26144441Z caller=main.go:374 msg="Received SIGTERM, exiting gracefully..."
level=info ts=2018-05-24T19:07:07.269457896Z caller=main.go:398 msg="Stopping scrape discovery manager..."
level=info ts=2018-05-24T19:07:08.900432011Z caller=main.go:411 msg="Stopping notify discovery manager..."
level=info ts=2018-05-24T19:07:08.900607557Z caller=main.go:432 msg="Stopping scrape manager..."
level=info ts=2018-05-24T19:07:10.843304564Z caller=main.go:394 msg="Scrape discovery manager stopped"
level=info ts=2018-05-24T19:07:10.88485881Z caller=main.go:407 msg="Notify discovery manager stopped"
level=info ts=2018-05-24T19:07:18.197290036Z caller=main.go:426 msg="Scrape manager stopped"
level=info ts=2018-05-24T19:07:18.232419965Z caller=manager.go:460 component="rule manager" msg="Stopping rule manager..."
level=info ts=2018-05-24T19:07:18.232757788Z caller=manager.go:466 component="rule manager" msg="Rule manager stopped"
level=info ts=2018-05-24T19:07:18.232820006Z caller=notifier.go:512 component=notifier msg="Stopping notification manager..."
level=info ts=2018-05-24T19:07:18.232992907Z caller=main.go:573 msg="Notifier manager stopped"
level=info ts=2018-05-24T19:07:18.234006831Z caller=main.go:584 msg="See you next time!"

No idea what could be causing this. The request is run from app t, which has no sidecar ... so nothing should be going to Prometheus, AFAIK.

ci/circleci: e2e-pilot is flaky #5323

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions