title: Setting log priority for Nodejs app running as systemd service
body: <p>I have an application which is running as a systemd service.</p>
  <p>Logs can be accessed using journalctl which is what I want, however despite the fact that node logs console.error &gt; stderr, it does not seem possible to identify console.error from console.log entries using the -p(riority) filter.</p>
  <p>It seems that all logs are sent without a priority:</p>
  <pre><code>journalctl -fu my-app.* -p 3
  </code></pre>
  <p>Attempting to show error logs ( p=3) results in no logs, despite the fact that there are error logs.</p>
  <p>How can I go about configuring nodejs to output it's logs with a priority level so that I can filter error and normal log files using journalctl ?</p>