[jira] [Updated] (MESOS-7361) Command checks via agent pollute agent logs.
[ https://issues.apache.org/jira/browse/MESOS-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-7361: -- Sprint: Mesosphere Sprint 68, Mesosphere Sprint 69, Mesosphere Sprint 70 (was: Mesosphere Sprint 68, Mesosphere Sprint 69) > Command checks via agent pollute agent logs. > > > Key: MESOS-7361 > URL: https://issues.apache.org/jira/browse/MESOS-7361 > Project: Mesos > Issue Type: Improvement > Components: agent >Reporter: Alexander Rukletsov >Assignee: Armand Grillet > Labels: check, health-check, mesosphere > > Command checks via agent leverage debug container API of the agent to start > checks. Each such invocation triggers a bunch of logs on the agent, because > the API was not originally designed with periodic invocations in mind. We > should find a way to avoid excessive logging on the agent. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MESOS-7361) Command checks via agent pollute agent logs.
[ https://issues.apache.org/jira/browse/MESOS-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-7361: -- Shepherd: Alexander Rukletsov > Command checks via agent pollute agent logs. > > > Key: MESOS-7361 > URL: https://issues.apache.org/jira/browse/MESOS-7361 > Project: Mesos > Issue Type: Improvement > Components: agent >Reporter: Alexander Rukletsov >Assignee: Armand Grillet > Labels: check, health-check, mesosphere > > Command checks via agent leverage debug container API of the agent to start > checks. Each such invocation triggers a bunch of logs on the agent, because > the API was not originally designed with periodic invocations in mind. We > should find a way to avoid excessive logging on the agent. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MESOS-7361) Command checks via agent pollute agent logs.
[ https://issues.apache.org/jira/browse/MESOS-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet updated MESOS-7361: -- Story Points: 3 > Command checks via agent pollute agent logs. > > > Key: MESOS-7361 > URL: https://issues.apache.org/jira/browse/MESOS-7361 > Project: Mesos > Issue Type: Improvement > Components: agent >Reporter: Alexander Rukletsov >Assignee: Armand Grillet > Labels: check, health-check, mesosphere > > Command checks via agent leverage debug container API of the agent to start > checks. Each such invocation triggers a bunch of logs on the agent, because > the API was not originally designed with periodic invocations in mind. We > should find a way to avoid excessive logging on the agent. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MESOS-7361) Command checks via agent pollute agent logs.
[ https://issues.apache.org/jira/browse/MESOS-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-7361: -- Sprint: Mesosphere Sprint 68, Mesosphere Sprint 69 (was: Mesosphere Sprint 68) > Command checks via agent pollute agent logs. > > > Key: MESOS-7361 > URL: https://issues.apache.org/jira/browse/MESOS-7361 > Project: Mesos > Issue Type: Improvement > Components: agent >Reporter: Alexander Rukletsov >Assignee: Armand Grillet > Labels: check, health-check, mesosphere > > Command checks via agent leverage debug container API of the agent to start > checks. Each such invocation triggers a bunch of logs on the agent, because > the API was not originally designed with periodic invocations in mind. We > should find a way to avoid excessive logging on the agent. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MESOS-7361) Command checks via agent pollute agent logs.
[ https://issues.apache.org/jira/browse/MESOS-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-7361: -- Sprint: Mesosphere Sprint 68 > Command checks via agent pollute agent logs. > > > Key: MESOS-7361 > URL: https://issues.apache.org/jira/browse/MESOS-7361 > Project: Mesos > Issue Type: Improvement > Components: agent >Reporter: Alexander Rukletsov >Assignee: Armand Grillet > Labels: check, health-check, mesosphere > > Command checks via agent leverage debug container API of the agent to start > checks. Each such invocation triggers a bunch of logs on the agent, because > the API was not originally designed with periodic invocations in mind. We > should find a way to avoid excessive logging on the agent. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
