<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><span class="vcard"><a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> <span class="fn">Zbigniew Jedrzejewski-Szmek</span></a>
</span> changed
              <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - RFE: support extra fields in systemd-journal-upload"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=89102">bug 89102</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Summary</td>
           <td>RFE: Extra systemd-journal-upload options to export
           </td>
           <td>RFE: support extra fields in systemd-journal-upload
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - RFE: support extra fields in systemd-journal-upload"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=89102#c1">Comment # 1</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - RFE: support extra fields in systemd-journal-upload"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=89102">bug 89102</a>
              from <span class="vcard"><a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> <span class="fn">Zbigniew Jedrzejewski-Szmek</span></a>
</span></b>
        <pre>Your request should be split into two or ever three parts.

First, adding custom fields to the log event stream. This has been requested
before, and should be done.

Second, we might consider adding fields from /usr/lib/os-release automatically,
things like description of the OS like CPE_NAME, BUILD_ID, and stuff from
/etc/machine-info, DEPLOYMENT, LOCATION, CHASSIS. I can see how this would be
useful, but I'm not sure if it is worth the overhead.

Third, JSON format. I'm not sure why you would s-j-upload specifically to
support JSON. journalctl -o json/json-pretty gives you JSON already. s-j-upload
is really a tool to communicate with s-j-remote, and the binary and HTTP
protocols it already has should be enough.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>