Skip to main content
Version: 11.7.x

Guidelines for logs

The objective of these guidelines is to guarantee uniformity between the logs from all services that run in a single project, regardless of whether they are custom or core.

Log Parsers

Every microservice from the Marketplace comes with an annotation called this annotation allows log collection and processing from your Kubernetes cluster to the ELK Stack.

Mia-Platform Console provides a series of log parsers that can be used as annotations and at runtime provides information to the loggin stack to parse and process fields of your service logs.

This information are available in the Microservice configuration card and will change accordingly the aforementioned annotation.

Log Parsers

Possible parsers are:

  • mia-json: parse log lines as JSON data structures, including nested fields.


    A possible log that can be parsed is:

    {"level":30,"time":1531171074631,"msg":"hello world","pid":657,"hostname":""}

    This log will be parsed into the following fields:

    • level: 30
    • time: 1531171074631
    • msg: hello world
    • pid: 657
    • hostname:

  • mia-nginx: parse log lines from our API Gateway based on NGINX having the following format:

    <remoteAddress> <remoteHostname> [<time>] "<requestMethod> <requestURL> HTTP/<requestHTTPVersion>" <statusCode> <responseSize> "<HTTPReferer>" "<userAgent>" - <responseTime> - <reqId>

    where time is in the format %Y-%m-%dT%H:%M:%S%z.


    A possible log that can be accepted by the parser is: [2023-10-30T15:47:07+00:00] "GET / HTTP/1.1" 404 323 "-" "Some browser" - 0.002 - my_unique_request_id

    This log will be parsed into the following fields:

    • remoteAddress:
    • remoteHostname:
    • time: 2023-10-30T15:47:07+00:00
    • requestMethod: GET
    • requestURL: /
    • requestHTTPVersion: 1.1
    • statusCode: 404
    • responseSize: 323
    • HTTPReferer: -
    • userAgent: Some browser
    • responseTime: 0.002
    • reqId: my_unique_request_id

  • mia-plain: does not parse any information contained in log lines.


Any log produced by the application that is not following this format will be stored but NOT indexed into logging fields.

To not collect logs from a micro-service, you can specify Not Collected as log parser.

JSON Logging format

When a service uses the label with value mia-json, all of its key/values are collected and stored in Elastic. However, if you want to perform queries on the logs using Kibana, you'll need to create indexes.

A set of preconfigured indexes come with each Console project. These indexes run on a specific set of keys. The following document provides a list of available log keys (following the Elastic Common Schema specifications) that can be used. Some of these log keys are indexed.


Each project has a set of preconfigured indexes. If you need custom indexes, please refer to your Mia-Platform representative.

Here you can find some guidelines, drawn from guidelines and best practices suggested by Elastic, which should be followed when application logs are generated:

  • Field names must be in camelCase;
  • Field names must not contain special characters;
  • Field names should be singular or plural according to the content of the field;
  • Whenever it makes sense, prefer nesting your fields in structured objects;
  • Avoid using abbreviations in field names.

When creating a new server, consider offload the setup of the logging facilities to Mia-Platform service libraries:

Use the appropriate logging level

It is important to always use the correct log level. Each level has a value expressed in tenths: the higher is the number, the higher the severity of the log. To choose which is the appropriate level, you should rely on the following criteria:

trace10Trace the operations flow of the application (do not use in production).
debug20Report information that may be useful in troubleshooting (do not use in production).
info30In cases where the service has to give information about the branch of code in execution.
warning40In cases of recoverable error, the service can continue to process the request.
error50In cases of not recoverable error and error for which the processing of the request (but not the service) must be interrupted.
fatal60In cases of unexpected and not recoverable error, and as a result of which the service must stop its execution.

It is important to put in logs the right information that can be used to track operations, highlight problems, and allow troubleshooting.


Avoid, under any circumstance, to insert any private or sensitive value that can lead to privacy-related issues or incidents.

Best Practices

In each log, the following fields should always be present:

msgStringIndexedThe text message specific for each log.
reqIdStringIndexedTraces the flow of each request. It is taken from the platform headers
timeNumberIndexedMarks in Unix timestamp the moment when the log was generated.
levelNumberIndexedIdentifies the severity level of the log.

The reqId field is extremely useful to trace operations following a single request, and is considered mandatory since usually services expose APIs.
However, if the concept of request tracing is not applicable, you can ignore it.

Track Requests

Each service exposing APIs must necessarily generate the logs shown in the table below, specifying the following fields in addition to the mandatory field specified above.

Incoming requesttraceIndexedhost, url
Request completedinfoIndexedhost, http, responseTime, url

If the service is not REST but takes its inputs from another source, the same criteria have to be applied.
Use a trace log when the event processing starts, and a info log when the event ends. The final log should contain as much useful information as possible.

ECS Field Definition

The following are examples taken from ECS documentation. None of the fields are mandatory, however it is important to use standard keys, whenever applicable.


If you want to create error logs, we recommend the following structure. When an error log has been generated, the passed object must necessarily have the key error, whose value has to be an object of the form specified by ECS for the Error Fields, which are shown in the table below:

error.codekeywordCoreIndexedError code describing the error.
error.idkeywordCoreIndexedUnique identifier for the error.
error.messagetextCoreIndexedError message.
error.stackTracekeywordExtendedIndexedThe stack trace of the error in plain text.
error.stackTrace.texttextExtendedIndexedMulti-fields stack trace of the error in plain text.
error.typekeywordExtendedIndexedThe type of the error, for example the class name of the exception. Example: java.lang.NullPointerException


host.hostnamekeywordCoreIndexedHostname of the host. It normally contains what the hostname command returns on the host machine.
host.namekeywordCoreIndexedName of the host. It can contain what hostname returns on Unix systems, the fully qualified domain name, or a name specified by the user. The sender decides which value to use.
host.uptimelongExtendedIndexedSeconds the host has been up. Example: 1325


http.request.body.byteslongExtendedIndexedSize in bytes of the request body. Example: 887
http.request.byteslongExtendedIndexedTotal size in bytes of the request (body and headers). Example: 1437
http.request.methodkeywordExtendedIndexedHTTP request method. The field value must be normalized to lowercase for querying. See the documentation section "Implementing ECS". Example: get, post, put
http.request.referrerkeywordExtendedIndexedReferrer for this HTTP request. Example:
http.request.userAgent.device.namekeywordExtendedNot indexedName of the device. Example: iPhone
http.request.userAgent.namekeywordExtendedNot indexedName of the user agent. Example: Safari
http.request.userAgent.originalkeywordExtendedIndexedUnparsed user_agent string. example: Mozilla/5.0 (iPhone; CPU iPhone OS 12_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0 Mobile/15E148 Safari/604.1
http.request.userAgent.original.texttextExtendedIndexedMulti-fields unparsed user_agent string.
http.request.userAgent.versionkeywordExtendedNot indexedVersion of the user agent. example: 12.0.
http.response.body.byteslongExtendedIndexedSize in bytes of the response body. example: 887
http.response.byteslongExtendedIndexedTotal size in bytes of the response (body and headers). example: 1437
http.response.status_codelongExtendedIndexedHTTP response status code. example: 404
http.versionkeywordExtendedNot indexedHTTP version. example: 1


url.domainkeywordExtendedIndexedDomain of the URL, such as In some cases a URL may refer to an IP and/or port directly, without a domain name. In this case, the IP address would go to the domain field. Example:
url.fragmentkeywordExtendedIndexedPortion of the URL after the #, such as "top". The # is not part of the fragment.
url.fullkeywordExtendedIndexedIf full URLs are important to your use case, they should be stored in url.full, whether this field is reconstructed or present in the event source.
url.full.texttextExtendedIndexedMulti-fields. Example:
url.pathkeywordExtendedIndexedPath of the request, such as /search.
url.portlongExtendedIndexedPort of the request, such as 443. Example: 443
url.querykeywordExtendedIndexedThe query field describes the query string of the request, such as "q=elasticsearch". The ? is excluded from the query string. If a URL contains no ?, there is no query field. If there is a ? but no query, the query field exists with an empty string. The exists query can be used to differentiate between the two cases.
url.schemekeywordExtendedIndexedScheme of the request, such as "https". Note: The : is not part of the scheme. Example: https.