Setting severity / status based on log content#
On occasion, you will need to adjust the severity of the log based on the actual log line content.
For example, a log line that reads: Please investigate - something is broken is mistakenly sent as an INFO level event when it really should be an ERROR.
scenario5.yaml shows the OpenTelemetry collector configuration to achieve this.
Stop Previous Collector#
If you haven't done so already, stop the previous collector process by pressing Ctrl + C.
Start Collector#
Run the following command to start the collector:
/workspaces/$RepositoryName/dynatrace-otel-collector --config=/workspaces/$RepositoryName/scenario5.yaml
Generate Log Data#
Open file.log file and add this line then save the file.
My fifth dummy log line. Please investigate - something is broken.
Verify Debug Data in Collector Output#
View the collector terminal window and verify that the SeverityText and SeverityNumber fields are now correctly set.
...
SeverityText: ERROR
SeverityNumber: Error(17)
Body: Str(My fifth dummy log line. Please investigate - something is broken.)
...
View Data in Dynatrace#
Tip
Right click and "open image in new tab" to see large image
Click the Run button again on the DQL tile. You should see the new data.
Reminder, the DQL statement is:
fetch logs
| filter contains(content, "dummy log line")
Congratulations! The log lines now have the most appropriate log level.