<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/08/2015 11:29 AM, Christian
Stimming wrote:<br>
</div>
<blockquote
cite="mid:OFE9FA9F0C.B336B9A6-ONC1257E5E.00341394-C1257E5E.003422B6@sick.de"
type="cite"><font face="sans-serif" size="2">Dear community,</font>
<br>
<br>
<font face="sans-serif" size="2">in the default configuration, the
"journal"
part of the kallithea web page notes all the various actions per
day. The
actions include "user xy pushed into A/B", and "xy started
following A/B", and "xy pulled from A/B".</font>
<br>
<br>
<font face="sans-serif" size="2">Is there any possibility to
filter out
some of the actions here? In particular, the "pulled from..."
action IMHO starts to make this page a rather bad overview of
what's going
on. I'm thinking of repositories with tens or hundreds of
developers, each
pulling several times per day. The actual pushs will be almost
invisible
on that default journal page because it will list the hundreds
of pulls.</font>
<br>
<br>
<font face="sans-serif" size="2">Also, depending on the social
context
it might actually be not desired to notify each other whether a
pull has
happened or has not happened. (I'm thinking of workplace
regulations in
some contries, e.g. Germany, "Leistungs- und
Verhaltenskontrolle",
where there might be information privacy regulations to
publically list
only the pushs but not the pulls.)</font>
<br>
<br>
<font face="sans-serif" size="2">Is there any configuration option
to
have such actions be removed from the journal? I didn't find
anything in
the documentation and neither in the issue tracker. I also tried
browsing
through the python code in model/journal.py but didn't find any
hints there
as well.</font>
<br>
<br>
<font face="sans-serif" size="2">Thank you very much for any
pointers
for further discussion!</font>
<br>
</blockquote>
<br>
Logging of pulls is arguably better done in the web server access
log. You can disable logging of pulls on /_admin/settings . <br>
<br>
The Journal is in my opinion currently not very useful. The whole
concept should probably be rethought. One alternative could be to
send all logging data to some logging service (such as
<a class="moz-txt-link-freetext" href="http://www.freedesktop.org/software/systemd/man/journalctl.html">http://www.freedesktop.org/software/systemd/man/journalctl.html</a> )
message bus (such as <a class="moz-txt-link-freetext" href="http://www.fedmsg.com/en/latest/overview/">http://www.fedmsg.com/en/latest/overview/</a> ) or
"data warehouse". We should also review whether we are logging
exactly what is important and relevant.<br>
<br>
/Mads<br>
</body>
</html>