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
One of the challenges I have heard several times is that it is difficult for users to determine the appropriate amount of storage space to allocate for the sending queue.
The answer will of course depend on the choice of storage extension, but we could provide metrics which are quite helpful in establishing a reasonable estimate.
We already have exporter_queue_size which reports the number of batches in the queue. However, without also knowing the size of these batches it is not possible to calculate the raw size of this data.
Would it make sense to add an optional histogram metric which records the size in bytes of each batch added to the queue?
The text was updated successfully, but these errors were encountered:
Component(s)
exporter/exporterhelper
Describe the issue you're reporting
One of the challenges I have heard several times is that it is difficult for users to determine the appropriate amount of storage space to allocate for the sending queue.
The answer will of course depend on the choice of storage extension, but we could provide metrics which are quite helpful in establishing a reasonable estimate.
We already have exporter_queue_size which reports the number of batches in the queue. However, without also knowing the size of these batches it is not possible to calculate the raw size of this data.
Would it make sense to add an optional histogram metric which records the size in bytes of each batch added to the queue?
The text was updated successfully, but these errors were encountered: