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.
Log records are aggregated by resource and log attributes, body and severity text. The instrumentation scope is ignored and does not form part of the exported logs payload.
Describe the solution you'd like
It should also be possible to aggregated logs per scope, using the scopes attributes, name and version. The scope should also be part of the exported logs payload.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
**Description:**
Adds a scope aggregator to separate log records by different scopes.
Also includes some refactor work:
- Extend pdatautil.hash with configurable options of values to hash,
includes ability of returning uint64
- Add consistent hash functions for resource, scope and log records that
use new hash functions
- Update aggregators to keep a copy of the original resource, scope and
log record instead of just it's attributes
- Simplifies ConsumeLogs & Export functions
- Update newLogCounter to set lastObservedTime
- Update existing and add more tests
**Link to tracking Issue:**
- Closesopen-telemetry#34606 34606
**Testing:**
Updated existing and added more unit tests to verify behaviour.
Component(s)
processor/logdedup
Is your feature request related to a problem? Please describe.
Log records are aggregated by resource and log attributes, body and severity text. The instrumentation scope is ignored and does not form part of the exported logs payload.
Describe the solution you'd like
It should also be possible to aggregated logs per scope, using the scopes attributes, name and version. The scope should also be part of the exported logs payload.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: