kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
104695 commits 1 branch 0 tags 899 MiB
Commit graph

9 commits

Author SHA1 Message Date
GitLab Bot
a17eb314cf Add latest changes from gitlab-org/gitlab@master 2020-09-24 15:09:51 +00:00
GitLab Bot
0115b63f64 Add latest changes from gitlab-org/gitlab@master 2020-09-18 06:09:31 +00:00
GitLab Bot
202268ad93 Add latest changes from gitlab-org/gitlab@master 2020-08-21 09:10:08 +00:00
GitLab Bot
0254867cf0 Add latest changes from gitlab-org/gitlab@master 2020-07-07 12:09:16 +00:00
GitLab Bot
fa7ac2663b Add latest changes from gitlab-org/gitlab@master 2020-06-24 06:09:01 +00:00
GitLab Bot
4f5c8572e9 Add latest changes from gitlab-org/gitlab@master 2020-06-16 18:09:01 +00:00
Oswaldo Ferreira
b332caa4eb Backport "Track repository pushes as audit events" 2019-09-04 10:19:33 -03:00
Stan Hu
e19499caf5 Format from and to fields in JSON audit log 
To make it possible to index the `from` and `to` fields with
Elasticsearch and other tools, we need the types to be the same.
Currently they are a mix of boolean and string values.

Part of https://gitlab.com/gitlab-org/gitlab-ee/issues/12599
 2019-07-11 13:46:51 -07:00
Stan Hu
143d0e2666 Add support for JSON logging for audit events 
This will add audit_json.log that writes one line per audit event. For
example:

{
       "severity":"INFO",
       "time":"2018-10-17T17:38:22.523Z",
       "author_id":3,
       "entity_id":2,
       "entity_type":"Project",
       "change":"visibility",
       "from":"Private",
       "to":"Public",
       "author_name":"John Doe4",
       "target_id":2,
       "target_type":"Project",
       "target_details":"namespace2/project2"
}
 2018-10-18 15:59:12 -07:00