-
Instead, we could add an optional `level` field to the global log function:
```js
log("Hello", level: std.LogLevel.VERBOSE)
```
-
I am trying to use formatting for log messages as suggested in https://github.com/open-telemetry/opentelemetry-cpp/blob/e86ceba79dc5999c7b3655fd006847a360b351a0/api/include/opentelemetry/logs/logger.h…
-
-
Hi,
Our use case read the full unified logs but does not bother about all the logs.
Could be great if we could skip the message formating while reading, but be able and turn the `message` field…
-
Add Angular component to display featured messages of interest
-
Create component that will be responsible for showing messages
success message - green bar with tick icon
warning message - orange bar with exclamation in triangle
error message - red bar with cros…
-
Noticed that log messages for core plugins, e.g. Pyroscope, are not formatted correctly as can be seen below.
```
{"@level":"debug","@message":"Processing queries","@timestamp":"2024-09-06T12:08:43.3…
-
It would be nice if in the filtering of the message box it becomes possible to only see one instance of a message like a depreciated operator warning.
Optionally with a count on how often it occure…
-
### Describe the bug
Our Quarkus application logs some strange messages with `NULL` content (since we left the 3.2 to 3.4 and after):
```
// Our JSON log:
{
level: SEVERE
loggerName: io.ve…
-
OS: WIndows 11
TeraTerm version: 5.3 x86 (Git 5b83fb6f7)
Steps to re-produce:
. configure TeraTerm to start with Auto start logging enabled, or just enable logging.
. start TeraTerm
. connect to …