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
Is your feature request related to a problem? Please describe.
I'm experimenting with receivertest.CheckConsumeContract to test a receiver and it seems to have some limitations. The receiver looks for a test_id attribute in the pdata message and uses that identifier to check if the data was delivered properly. This field is currently hardcoded.
For the receiver I'm trying to test, we don't use attributes and everything is in the log message body. I would like to be able to specify exactly how this identifier should be fetched, this gives more flexibility when testing.
Describe the solution you'd like
The first solution I thought of is to use a user defined function to fetch the identifier, for example:
With this we would need a callback function for metrics and traces as well. If this callback is not defined then it defaults to the current behavior—looking up the receivertest.UniqueIDAttrName attribute.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm experimenting with
receivertest.CheckConsumeContract
to test a receiver and it seems to have some limitations. The receiver looks for atest_id
attribute in the pdata message and uses that identifier to check if the data was delivered properly. This field is currently hardcoded.For the receiver I'm trying to test, we don't use attributes and everything is in the log message body. I would like to be able to specify exactly how this identifier should be fetched, this gives more flexibility when testing.
Describe the solution you'd like
The first solution I thought of is to use a user defined function to fetch the identifier, for example:
With this we would need a callback function for metrics and traces as well. If this callback is not defined then it defaults to the current behavior—looking up the
receivertest.UniqueIDAttrName
attribute.The text was updated successfully, but these errors were encountered: