Srikanth Chekuri

Spec discussion https://github.com/open-telemetry/opentelemetry-specification/issues/3136

>Implement a query history feature for log retrieval to improve user experience. https://github.com/SigNoz/signoz/issues/5144 >Introduce a global mapping function that allows users to map their custom log fields to the required...

https://github.com/open-telemetry/semantic-conventions

Where did you get the json reference? SigNoz accepts data using OTLP protocol, and format for otlp json is this https://github.com/open-telemetry/opentelemetry-proto/blob/main/examples/logs.json

>Is it only camel case? Can't it be snake case? It should be exactly as mentioned in the json example. >If I use Zap to log to a file without...

I hope your question is answered. We do not consider the option of mapping. The data should come from the source in the required format following OTeL semantics.

While at it, please check all the Service details tab panels once again to see if there are any such gaps (in Overview, DB, and external tabs).

This `signoz.collector.id` can be ignored.

For those customers with a different TTL than default, it will be updated. Edit: TTL has been updated. This feature is enabled by default for everyone. Will disable it for...

> AFAIU the logic, users won't be able to see such spikes for data older data. @shivanshuraj1333 we maintain mix, max, and count other than average. They can choose to...