kamon.io/about.html at master · kamon-io/kamon.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
---
layout: default
title: 'Kamon.io - Simple and Effortless Microservices Monitoring Tool'
description: 'We are developers helping other developers easily find and fix errors and performance issues. Start monitoring microservices in 3 minutes.'
---

<div class="background-top-gray"></div>
<main class="default-content-container">
  <section class="row hero no-gutters">
    <div class="col-12 text-center">
      <h1>
        Here is our story
      </h1>

      <h4 class="my-3">
        We are a group of folks focused on making it easier for people<br>
        to instrument, monitor and debug distributed systems.
      </h4>
    </div>
  </section>


  <section class="w-100 background-gray skew-top-right">
    <div class="container">
      <div class="row pt-2 pb-5">
        <div class="col-sm-12 col-lg-7 pr-lg-5">
          <h1 class="font-weight-normal mt-3">
            The Beginning
          </h1>
          <p class="about-us-section mt-4">
            It all started back in 2014. We were super happy writing our very first services with Akka and Scala,
            doing concurrency like never before (literally) until the D day came: we were ready to deploy to production
            and only then we discovered that there was no simple, performant and reliable way to get metrics out of the
            services we just wrote. We searched, we asked around and we found nothing, so we decided to build something
            that could <strong>help</strong> solve this problem.
          </p>

          <p class="about-us-section mt-4">
            During this process we noticed that we were not alone on this; there were several teams around the world
            facing the very same problems we had so there was only one natural thing to do, <strong>share</strong> what
            we built, an so Kamon was born!
          </p>
        </div>

        <div class="col-sm-12 col-lg-5 mt-5 pt-lg-4 text-left">
          <img class="img-fluid" src="/assets/img/about-us-logos-history.png" alt="Kamon logos history">
        </div>
      </div>
    </div>
  </section>


  <section class="w-100">
    <div class="container mt-6">
      <div class="row justify-content-center">
        <div class="col-12 col-lg-4 pt-5 align-self-center">
          <img class="img-fluid" src="/assets/img/kamon-apm-logo.svg" alt="Kamon APM Logo">
        </div>
        <div class="col-12 col-lg-8 pl-lg-5 text-left">
          <h1 class="font-weight-normal mt-3">
            And then, APM
          </h1>

          <p class="about-us-section mt-4">
            As time passed and we grew more fond of monitoring, we started to notice how all our effort on the
            instrumentation side was usually being transformed into a few statistical summaries on a dashboard that said
            very little about the true behavior of an application. Our frustration with this lead us to build a platform
            that at it's very core could store an application's behavior in the same level of detail as Kamon can gather
            it, so Kamon APM was born.
          </p>
          <p class="about-us-section mt-4">
            Fast forward to today, Kamon APM is no longer just about metrics! We are enabling teams around the world to
            to see the true behavior of their services with both metrics and distributed tracing, get alerts when things
            go wrong and discover issues across microservices. And we are just getting started!
          </p>
        </div>
      </div>
    </div>
  </section>


  <section id="contact-us-section" class="w-100">
    <div class="container mt-8">
      <div class="row text-center">
        <div class="col-12 col-md-5">
          <h1 class="font-weight-normal mt-3">
            Visit us in Zagreb
          </h1>

          <p class="about-us-section mt-4">
            If you come to Zagreb do not hesitate to <strong><a href="mailto:hello@kamon.io">contact us</a></strong> and
            let's grab a beer or coffee together! You will leave the city well fed and full of Kamon stickers :)
          </p>
        </div>


        <div class="col-12 col-md-5 offset-md-2">
          <h1 class="font-weight-normal mt-3">
            Share your experience
          </h1>

          <p class="about-us-section mt-4">
            Don't be shy, reach out on Twitter and give us a Star on Github if Kamon is helping you!
          </p>

          <a href="https://twitter.com/kamonteam?ref_src=twsrc%5Etfw" class="twitter-follow-button" data-size="large" data-show-count="false">Follow @kamonteam</a><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
          <a class="github-button" href="https://github.com/kamon-io/kamon" data-size="large" data-show-count="true" aria-label="Star kamon-io/kamon on GitHub">Star</a>
        </div>
      </div>
    </div>
  </section>


  <section class="w-100 background-gray skew-top-left">
    <div class="container mt-8 pb-4">
      <div class="row">
        <div class="col-12 text-right">
          <h3 class="font-weight-normal">
            Trivia: is "Kamon" a mythical creature or something like that?
          </h3>
          <p class="mt-4 about-us-section pl-lg-5">
            LOL. No. You know that situation where it takes forever to start your next project because you need to
            choose an awesome name? We skipped that and went for Ak<strong>ka Mon</strong>itoring. It caught up and here
            we are!
          </p>
        </div>
      </div>
    </div>
  </section>
</main>

<script async defer src="https://buttons.github.io/buttons.js"></script>