Configure your application to log to console (stdout/stderr), it will be scraped by FluentD running inside the cluster and sent to Elasticsearch and made available via Kibana. Visit our Kibana at logs.adeo.no.
If you want more information than just the log message (loglevel, MDC, etc), you should log in JSON format; the fields you provide will then be indexed.
Working with Kibana¶
When you open Kibana you are prompted to select a workspace, select "Nav Logs" to start viewing your application logs.
Once the page loads you will see an empty page with a search bar. This is the query bar, and it is used to search for logs. You can use the query bar to search for logs by message, by field, or by a combination of both.
The query language is called Kibana Query Language (KQL). KQL is a simplified version of Lucene query syntax. You can use KQL to search for logs by message, by field, or by a combination of both.
There is also a time picker in the upper right corner of the page. You can use the time picker to select a time range to search for logs. The default time range is the last 15 minutes. If no logs shows up, try to increase the time range.
The following fields are common to all logs and can be used in the query bar:
@timestamp- The timestamp of the log event.
application- The application the log event originated from.
cluster- The cluster the log event originated from.
container- The container the log event originated from.
host- The host the log event originated from.
level- The log level of the log event.
message- The log message itself.
namespace- The namespace the log event originated from.
pod- The pod the log event originated from.
team- The team who owns the application the log event originated from.
||Search for logs with the message "my message"|
||Search for logs with the message "my message" and the level "ERROR"|
||Search for logs with the message "my message" or the level "ERROR"|
||Search for logs with the message "my message" and not the level "ERROR"|
||Search for logs with the message "my message" and the level "ERROR" and not the level "WARN"|
||Search for logs with the message "my message" and the level "ERROR" or the level "WARN"|
Gain access to logs.adeo.no¶
In order to get access to logs.adeo.no you need to have the correct access rights added to your AD account. This can be requested through your Personnal Manager.
These permissions will give you access:
If you're unsure if you already have these permission, or some of them, you can check what permission you currently have at igruppe.adeo.no
Some applications have logs with information that should not be stored with the normal application logs. To support this a directory for these logs can be mounted in the application, and the content of logs written here will be transferred to separate indices in Elasticsearch.
Enabling secure logs¶
Secure logs can be enabled by setting the
secureLogs.enabled flag in the application resource. See the nais manifest specification.
With secure logs enabled a directory
/secure-logs/ will be mounted in the application container. Every
*.log file in this directory will be monitored and the content transferred to Elasticsearch. Make sure that these files are readable for the log shipper (the process runs as uid/gid 1065).
/secure-logs/ directory has a size limit of 128Mb, and it's the application responsibility to ensure that this limit is not exceeded. If the limit is exceeded the application pod will be evicted and restarted. Use log rotation on file size to avoid this.
Log files should be in JSON format as the normal application logs. Here is an example configuration of JSON logging with a size based rolling file appender in Logback:
<appender name="secureLog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/secure-logs/secure.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>/secure-logs/secure.log.%i</fileNamePattern> <minIndex>1</minIndex> <maxIndex>1</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>50MB</maxFileSize> </triggeringPolicy> <encoder class="net.logstash.logback.encoder.LogstashEncoder" /> </appender>
See logging examples for more information on log configuration.
If the logging framework used doesn't support JSON logging, it is also possible to use multiline logs in this format:
Files on this format must be named
Sending logs with HTTP¶
If you do not want to have these logs as files in the pod, it is also possible to use HTTP to write logs. POST your log entry as JSON to
Most applications where a user processes data related to another user need to log audit statements, detailing which user did what action on which subject. These logs need to follow a specific format and be accessible by ArcSight. See naudit for how to set up the logging, and details on the log format.
Gaining access in kibana¶
Once everything is configured, your secure logs will be sent to the
tjenestekall-* index in kibana. To gain access to these logs, you need to do the following:
1 Create an AD-group¶
To make sure you gain access to the proper logs, you need an AD-group connected to the nais-team. So the first thing you do is create this group.
Go to Porten (service desk) and click
Melde sak til IT. The follow the template below.
For IT to be able to correctly add the group to Remedy you need to specify the four digit department code for those who can be able to ask for permission to the group. E.g 2990 is the four digit code for the department IT-AVDELINGEN. If you are creating secure logs for your team and are unsure about which department your colleagues belong to then you can use Delve to search for their profile. In their profile their department code will also be visible.
You can paste the template below into Jira:
Ønsker å få opprettet en AD-gruppe for å få tilgang til sikker logg i Kibana for applikasjoner knyttet til <your project here>. Gruppenavn: 0000-GA-SECURE_LOG_<SOMETHING> Beskrivelse: Tilgang til secureLog for Team <team name> i Kibana. Kryss i identrutinen: Ja Den må inn i Remedy. Enheter i Nav som skal ha tilgang: <four digit department code>. E.g (2990 - IT-AVDELINGEN)
2 Connect the AD group to your team in Kibana¶
The logs your apps produces are linked with your nais-team. Administrators of Kibana will create a role for your team with read rights to those logs. Whoever is in the AD-group (created in step 1) will get the Kibana role, and can thus read all logs produced by apps belonging to the nais-team.
Ask in the #atom Slack channel to connect the AD-group (created in step 1) to your nais-team.
3 Put people into the AD-group¶
This must be done by "identansvarlig". For NAV-IT employees, this is
firstname.lastname@example.org. Send them an email and ask for access with a CC to whoever is your superior.
For everyone else, the team lead or who ever is their superior should know.
What can go wrong?¶
Basically, the one thing that can go wrong here is that the AD-group is not registered in "identrutinen". If this happens, the group cannot be found by "identansvarlig". If this happens, make a new JIRA-ticket to the same people and tell them to transfer the group. Sadly this can take a few days.