Implement check metadata payloads#2554
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2554 +/- ##
==========================================
- Coverage 57.03% 56.52% -0.52%
==========================================
Files 350 380 +30
Lines 19489 24119 +4630
==========================================
+ Hits 11116 13633 +2517
- Misses 7541 9571 +2030
- Partials 832 915 +83
|
7c3da93 to
c688b10
Compare
a4b2f8f to
061fed3
Compare
gzussa
left a comment
There was a problem hiding this comment.
Let's try to get this feature in but instead of sending infos to DD, let's add them to the flare cmd.
Also, let's get rid of the metadata name everywhere. What about using infos or details?
|
just realized this PR existed, so adding a note here: we have an OKR in Q2 about sending some more Agent telemetry, this could part of the effort (we have a stretch key result about sending more info about running agent integrations: version of integration, version of software that's monitored). We should have a discussion/RFC in Q2 about what the payload should look like before reviewing this PR (having in mind the current backend contraints, and long-term goals) |
|
Just some info for those coming here:
|
What does this PR do?
Implements a way for checks to send their own metadata. The backend will learn to work with this in upcoming PRs to respective repos.
Motivation
So we can track things like versions of applications monitored (MySQL, Redis, ...), configuration options used, etc.