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.
Many systems, especially legacy ones, report metrics through logs. Analyzing metric data directly from logs is inefficient and complex, which highlights the need to extract it from the logs during collection and store it as a separate signal. This capability already exists on the receiving end of many monitoring platforms (1, 2, 3) - having it in OTel would greatly enhance it.
The signaltometrics connector is a huge step toward this, but it does not produce the gauge metric type currently. This is a request to add gauge to the list of supported produced metrics.
Component(s)
connector/signaltometrics
Is your feature request related to a problem? Please describe.
Many systems, especially legacy ones, report metrics through logs. Analyzing metric data directly from logs is inefficient and complex, which highlights the need to extract it from the logs during collection and store it as a separate signal. This capability already exists on the receiving end of many monitoring platforms (1, 2, 3) - having it in OTel would greatly enhance it.
The signaltometrics connector is a huge step toward this, but it does not produce the gauge metric type currently. This is a request to add gauge to the list of supported produced metrics.
Describe the solution you'd like
Example configuration:
Log:
2025-01-08 16:28:00 Memory usage: 600MB
Result:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: