<p>A third party app metrics tools is great if it already covers all (or most of) the parameters you want to monitor and it presents the information in a convenient enough manner for your use case - you just need to (find it first and then) learn how to install/use/maintain it and then do that.</p>

<p>Advantages:</p>

<ul>
<li>avoids the software development and maintenance costs, which can be quite high depending on the capabilities</li>
<li>can be immediately used, a custom tool needs to be developed first</li>
<li>technical support (not always great, tho)</li>
<li>standardisation: if the tool is a popular one - expertise on it can be requested on a job description instead of having to train every user on it</li>
</ul>

<p>However there are many cases in which custom development is needed, some already mentioned by Michael: reliability, security/confidentiality, lack of integrations for your custom applications.</p>

<p>Depending on each particular case, custom development can go from tiny scripts extending the coverage of a third party tool to complex wrappers assembling multiple such tools to achieve the necessary monitoring capabilities</p>

<p>Such development is not always lightweight:</p>

<ul>
<li>it may require in-depth tool knowledge and/or language expertise outside of your team</li>
<li>it may need management for heavy/complex or even conflicting dependencies</li>
<li>the adaptation layers for the tool's actual usage environment may be very heavy</li>
</ul>

<p>Sometimes the cost of such development is higher overall than that of developing a custom system.</p>

<p>Othertimes the functionality actually needed from the third party tools is a relatively small percent of its capability set and the overhead for learning/installing/operating the tool is simply not worthy.</p>

<p>You guessed it - I wrote my own monitoring tool :)</p>

CC BY-SA 3.0
2017-09-18T15:56:10.390Z
2017-09-18T15:56:10.390Z
Dan Cornilescu
<p>With tools like Riemann, New Relic, etc., is there any benefit to building custom app metrics tools for monitoring application health?</p>

CC BY-SA 3.0
2017-09-18T16:00:52.697Z
"is there any benefit to building custom app metrics tools..." as opposed to? Doing nothing? Using only what is pre-built? Using a divining rod?
James Shewey
CC BY-SA 3.0
2017-03-02T10:33:51.767Z
How is this primarily opinion-based? Logs give crucial informations about an infrastructure. Can you guarantee your monitoring provider is reliable? Can you guarantee strategic information about your business will not leak to some opponents? How easy it is to prepare custom analysis on the provider's system? All these questions lead to trade-offs decision that can be rationally discussed!
Michaël Le Barbier
<monitoring><metrics>
What are benefits of using third party app metrics tools versus custom build tools?
soundslikeodd
# What are benefits of using third party app metrics tools versus custom build tools?

(Asked by: username_0 on 2017-02-28)

With tools like Riemann, New Relic, etc., is there any benefit to building custom app metrics tools for monitoring application health?

**Tags:** monitoring, metrics

> **Comments:**
> **username_2**: How is this primarily opinion-based? Logs give crucial informations about an infrastructure. Can you guarantee your monitoring provider is reliable? Can you guarantee strategic information about your business will not leak to some opponents? How easy it is to prepare custom analysis on the provider's system? All these questions lead to trade-offs decision that can be rationally discussed!  
> **username_1**: "is there any benefit to building custom app metrics tools..." as opposed to? Doing nothing? Using only what is pre-built? Using a divining rod?  

---

## 1 answers

### Answer by username_3 on 2017-09-18. Score: 3

A third party app metrics tools is great if it already covers all (or most of) the parameters you want to monitor and it presents the information in a convenient enough manner for your use case - you just need to (find it first and then) learn how to install/use/maintain it and then do that.

Advantages:

* avoids the software development and maintenance costs, which can be quite high depending on the capabilities
* can be immediately used, a custom tool needs to be developed first
* technical support (not always great, tho)
* standardisation: if the tool is a popular one - expertise on it can be requested on a job description instead of having to train every user on it

However there are many cases in which custom development is needed, some already mentioned by Michael: reliability, security/confidentiality, lack of integrations for your custom applications.

Depending on each particular case, custom development can go from tiny scripts extending the coverage of a third party tool to complex wrappers assembling multiple such tools to achieve the necessary monitoring capabilities

Such development is not always lightweight:

* it may require in-depth tool knowledge and/or language expertise outside of your team
* it may need management for heavy/complex or even conflicting dependencies
* the adaptation layers for the tool's actual usage environment may be very heavy

Sometimes the cost of such development is higher overall than that of developing a custom system.

Othertimes the functionality actually needed from the third party tools is a relatively small percent of its capability set and the overhead for learning/installing/operating the tool is simply not worthy.

You guessed it - I wrote my own monitoring tool :)


---

