[sr-dev] [kamailio/kamailio] JSON CEE structured logging (#2797)

Daniel Pocock notifications at github.com
Sat Jul 10 17:13:44 CEST 2021


<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for feature requests.

If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:

  * http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:

  * http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.

If you submit a feature request (or enhancement) add the description of what you would like to be added.

If there is no content to be filled in a section, the entire section can be removed.

You can delete the comments from the template sections when filling.

You can delete next line and everything above before submitting (it is a comment).
-->

### Description

Kamailio recently added JSON logging support, described on these two pages:
https://www.kamailio.org/w/2020/04/structured-json-logging/
https://www.kamailio.org/wiki/cookbooks/devel/core#log_engine_cli_parameter

Structured logging is particularly useful when:

1. there are multiple applications involved in a call (e.g. Kamailio, Kurento, coTurn, Apache)
2. all the applications create JSON logs using identical field names

I recently made contributions to reSIProcate, GStreamer and Kurento to support the JSON CEE field names.  It would be very easy to replicate in Kamailio.
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/847
https://github.com/Kurento/kurento-media-server/pull/17
https://github.com/resiprocate/resiprocate/commit/d1df9aeb956be79253560fe3628b3f37a4ef94f2

Notice that ```rsyslog``` can receive legacy Syslog events from VoIP hardware, Cisco and Polycom phones and it can convert them to JSON CEE and push them into the document store where they will meet the records from Kamailio.  This is another case where it is really useful if all the JSON from different applications is using CEE.

Here are the JSON CEE field names:

https://cee.mitre.org/language/1.0-beta1/core-profile.html

### Expected behavior

Extend the config setting so that people can request CEE on the command line.

#### Actual observed behavior

#### Debugging Data

```
(paste your debugging data here)
```

#### Log Messages

<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->

```
(paste your log messages here)
```

#### SIP Traffic

<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->

```
(paste your sip traffic here)
```

### Possible Solutions

<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a improvement.
-->

### Additional Information

  * **Kamailio Version** - output of `kamailio -v`

```
(paste your output here)
```

* **Operating System**:

<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->

```
(paste your output here)
```


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2797
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20210710/2a68407a/attachment.htm>


More information about the sr-dev mailing list