You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After custom CO-RE BPF rollout it would be hard to get visibility into its
adoption with the current data we have. Investigate if we could use Amplitude
integration to get better understanding how collection methods are used. There
are following questions to cover:
What would be the easiest implementation? Proposed options to evaluate are
integrating Collector directly with Amplitude, or pass the necessary
information via Sensor and let it report everything.
What data should be exposed? Proposed bits if information regarding
collection method are:
Effective collection method (in case if it was changed by collector at
runtime and differs from what was configured).
Kernel version Collector is running on.
Cases where a collection method has failed.
The last one is the trickiest one, as it brings the most valuable information,
but at the same time we would like to get only a single error pair (collection
method, kernel version), which is hard as Collector will be in a crash loop.
After custom CO-RE BPF rollout it would be hard to get visibility into its
adoption with the current data we have. Investigate if we could use Amplitude
integration to get better understanding how collection methods are used. There
are following questions to cover:
What would be the easiest implementation? Proposed options to evaluate are
integrating Collector directly with Amplitude, or pass the necessary
information via Sensor and let it report everything.
What data should be exposed? Proposed bits if information regarding
collection method are:
runtime and differs from what was configured).
The last one is the trickiest one, as it brings the most valuable information,
but at the same time we would like to get only a single error pair (collection
method, kernel version), which is hard as Collector will be in a crash loop.
Part of #1426
The text was updated successfully, but these errors were encountered: