-
Notifications
You must be signed in to change notification settings - Fork 179
add Prometheus to remaining sidecar types #752
Conversation
d17e243
to
107ff09
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I recognize the prom metrics are basically in parity with the statsd metrics, I think we should be aiming for the proper metrics, rather than replacement metrics. Additionally, these need spec changes (even though the same sidecar are used for go and python), and we should ensure any clients used in the sidecars are the baseplate clients so we get that instrumentation for free
8a10860
to
0491f16
Compare
self.session.headers[ | ||
"User-Agent" | ||
] = f"baseplate.py-{self.__class__.__name__}/{baseplate_version}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I'm missing something, but it seems like this was getting overwritten below anyway (and same in the other file)
f6f0830
to
0959931
Compare
0959931
to
fe851d5
Compare
0356258
to
75bb1e3
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job! Do you have some example metrics from testing?
Not good ones 😅 My plan now is to ask a team who actually uses these sidecars in a not-very-critical service if I can do better tests using their service |
Okey doke, finally tested it:
Example metrics from the trace_publisher test (forgot to record ones from the other test, but it was pretty similar)
|
This reverts commit eb7d24b.
💸 TL;DR
Reproducing #742. This makes all sidecar types expose Prometheus metrics.
📜 Details
JIRA
🧪 Testing Steps / Validation
and only then update infrared to use these by default
✅ Checks