<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 05/20/2016 05:55 PM, Arash
      Kaffamanesh wrote:<br>
    </div>
    <blockquote
cite="mid:CA+LqMcHgHKqiAoYnht69K1KztmtYRENcMXcjb5Fd0mRb+OX5yw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>Great!</div>
        <div><br>
        </div>
        <div>I'm currently working on how to bring log- and application-
          performance monitoring under the same roof for cloud-native
          and highly distributed applications on top of OpenStack w/
          Cloud Foundry or OpenShift and Kubernetes add-ons and define
          some best practices (needs) to build a simple, though
          effective cloud native application monitoring solution for
          BizDevOps (yet another buzz :-)).<br>
          <br>
          My 10 BizDevOps needs are:</div>
        <div>
          <ol class="">
            <li class=""><span class=""></span><span class="">Bring log
                and performance monitoring under the same roof, by
                providing a seamless correlation between log and
                performance metrics.<br>
              </span></li>
            <li class=""><span class=""></span><span class="">Provide
                intuitive pre-built monitoring interfaces and dashboards
                for everybody and for different roles and organizations
                (BizDevOps) (note: people lack the time and sometimes
                the skills to configure a monitoring tool).</span></li>
            <li class=""><span class=""></span><span class="">Build
                dedicated dashboards for transaction and correlation
                analysis to figure out the usual suspects like, memory
                leaks, garbage collection, saturated thread pools and
                hundreds of unusual suspects which might be the root
                cause of problems.<br>
              </span></li>
            <li class=""><span class=""></span><span class="">Enhance
                the quality of logs (on paas and apps level) and define
                custom metrics which are specific to our cloud-native
                applications and visualize these metrics on custom
                dashboards for tenants w/ different roles.<br>
              </span></li>
            <li class=""><span class=""></span><span class="">Analyze
                long term-trends such as how big is my database and how
                fast is it growing? How quickly is my daily-active user
                count growing?</span></li>
            <li class=""><span class=""></span><span class="">Implement
                innovative ideas such as data mining, forecasting and
                advanced analytics support to provide added value to the
                monitoring solution.<br>
              </span></li>
            <li class=""><span class=""></span><span class="">Get alerts
                on issues before customers notice, use the monitoring
                tool as an early warning system, and analyze application
                performance before and after new code deployments.<br>
              </span></li>
            <li class=""><span class=""></span><span class="">If using
                remediation actions which are triggered through the
                monitoring solution, first require human approval before
                the script is executed (this provides a better
                understanding of the root cause of the problem and how
                to eliminate it in long term).<br>
              </span></li>
            <li class=""><span class=""></span><span class="">Implement
                a simple, though an effective alerting system with clear
                alerting escalation path and low noise (rules that
                generate alerts for developers or operators should be
                simple to understand and represent a clear failure).<br>
              </span></li>
            <li class=""><span class=""></span><span class="">Combine
                heavy use of white-box monitoring with modest but
                critical uses of black-box monitoring and learn from
                others like Google about how they are monitoring their
                highly distributed systems: </span><a
                moz-do-not-send="true"
                href="https://www.oreilly.com/ideas/monitoring-distributed-systems"><a class="moz-txt-link-freetext" href="https://www.oreilly.com/ideas/monitoring-distributed-systems">https://www.oreilly.com/ideas/monitoring-distributed-systems</a></a></li>
          </ol>
        </div>
      </div>
    </blockquote>
    <br>
    These are good.<br>
    <br>
    <blockquote
cite="mid:CA+LqMcHgHKqiAoYnht69K1KztmtYRENcMXcjb5Fd0mRb+OX5yw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">To achieve the above needs, I'm
          investigating the following tools to bring log and performance
          monitoring under the same roof for my current needs:</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">
          <ul>
            <li>ELK / EFK Stack<br>
            </li>
            <li>Hawkular:  <a moz-do-not-send="true"
                href="http://www.hawkular.org/">http://www.hawkular.org/</a><br>
            </li>
          </ul>
        </div>
      </div>
    </blockquote>
    <br>
    EFK is already being used by OpenShift and RDO, and Hawkular is
    already being used by OpenShift - these will be among our first
    packages to support.<br>
    <br>
    <blockquote
cite="mid:CA+LqMcHgHKqiAoYnht69K1KztmtYRENcMXcjb5Fd0mRb+OX5yw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <ul>
            <li>Stagemonitor <a moz-do-not-send="true"
                href="http://www.stagemonitor.org/">http://www.stagemonitor.org/</a><br>
            </li>
            <li>cAdvisor <a moz-do-not-send="true"
                href="https://github.com/google/cadvisor">https://github.com/google/cadvisor</a><br>
            </li>
          </ul>
        </div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">and I think these BizDevOps-Tools might
          be the right choice to start with and I'd be happy to be of
          help.</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Cheers,</div>
        <div class="gmail_extra">Arash</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">On Fri, May 20, 2016 at 9:08 PM,
          Matthias Runge <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:mrunge@redhat.com" target="_blank">mrunge@redhat.com</a>></span>
          wrote:<br>
        </div>
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
              <div class="">
                <div class="h5">On 20/05/16 16:12, Rich Megginson wrote:<br>
                  > We are trying to start up a CentOS OpsTools SIG<br>
                  > <a moz-do-not-send="true"
                    href="https://wiki.centos.org/SpecialInterestGroup"
                    rel="noreferrer" target="_blank">https://wiki.centos.org/SpecialInterestGroup</a>
                  for logging, monitoring, etc.<br>
                  ><br>
                  > The intention is that this would be the upstream
                  for development and<br>
                  > packaging of tools related to logging (EFK stack,
                  etc.), monitoring, and<br>
                  > other opstools, as a single place where packages
                  can be consumed by RDO,<br>
                  > OpenShift Origin, and other upstream projects -
                  pool our resources,<br>
                  > share the lessons learned, and enable cross
                  project log aggregation and<br>
                  > correlation (e.g. running OpenShift on top of
                  OpenStack on top of<br>
                  > Ceph/Gluster - do my OpenShift application errors
                  correlate with Nova<br>
                  > errors?  file system errors?).  This would also
                  be a place for<br>
                  > installers (puppet manifests, ansible playbooks),
                  and possibly<br>
                  > testing/CI and containers.<br>
                  ><br>
                  > If you are interested, please chime in in the
                  email thread:<br>
                  > <a moz-do-not-send="true"
href="https://lists.centos.org/pipermail/centos-devel/2016-May/014777.html"
                    rel="noreferrer" target="_blank">https://lists.centos.org/pipermail/centos-devel/2016-May/014777.html</a><br>
                  ><br>
                </div>
              </div>
              Thank you for the reminder, Rich.<br>
              <br>
              We already have quite a few interested persons. The
              reason, why I didn't<br>
              mention this here was, that it has a broader focus than
              just RDO.<br>
              <br>
              On the other side, it clearly will be usable with RDO, and
              it will help<br>
              RDO operators to get to the root of occurring issues.<br>
              <br>
              If any of you is interested or can help, please join us on
              centos-devel<br>
              mailing list and express your interest there. It will help
              us to speed<br>
              things up.<br>
              --<br>
              Matthias Runge <<a moz-do-not-send="true"
                href="mailto:mrunge@redhat.com">mrunge@redhat.com</a>><br>
              <br>
              Red Hat GmbH, <a moz-do-not-send="true"
                href="http://www.de.redhat.com/" rel="noreferrer"
                target="_blank">http://www.de.redhat.com/</a>,
              Registered seat: Grasbrunn,<br>
              Commercial register: Amtsgericht Muenchen, HRB 153243,<br>
              Managing Directors: Paul Argiry, Charles Cachera, Michael
              Cunningham,<br>
                                  Michael O'Neill<br>
              <br>
              _______________________________________________<br>
              rdo-list mailing list<br>
              <a moz-do-not-send="true"
                href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a><br>
              <a moz-do-not-send="true"
                href="https://www.redhat.com/mailman/listinfo/rdo-list"
                rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
              <br>
              To unsubscribe: <a moz-do-not-send="true"
                href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a><br>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
rdo-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rdo-list@redhat.com">rdo-list@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/rdo-list">https://www.redhat.com/mailman/listinfo/rdo-list</a>

To unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:rdo-list-unsubscribe@redhat.com">rdo-list-unsubscribe@redhat.com</a></pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>