Logs

The PaaS Logs section in the Cockpit displays logs for pods, domains, ingresses, and more. Each section has dedicated filtering by their relevant components as well as by a date range.

There are several different types of logs which are covered on this page. See the subsections below more for more details.

Select desired cluster

Select your desired cluster from the dropdown menu at the top of the Cockpit.

select cluster id

Magnolia Backend

Magnolia Backend displays log information from Kubernetes Pods associated with the Magnolia backend. You can access the pods logs by going to your Cockpit and navigating to the Logs section.

You can select up to the last 7 days for this filter.
How long do you keep the logs?

Generally, we keep logs for 30 days. However, for your deployment, you may configure a different duration.

From Logs > Magnolia Backend:

View from the Cockpit

pod logs backend

  1. Select your desired Release from the dropdown list.

  2. Select your desired App or Database pod from the dropdown list.

  3. Select your desired Container from the dropdown list.

  4. Select your desired Date Range.

  5. Input any filter terms under Term. This filters the results by the term you’ve entered.

  6. Click Apply filters.

Log format

Log fields

Field Description Example

date

string

The log date.

"[14/Mar/2022:16:01:50 +0000]"

log level

string

The severity of the log such as INFO or WARN.

INFO

log message

string

The log message.

info.magnolia.module.scheduler.SchedulerModule : Job configScan added [0 0 0 * * ?]. Will fire for the first time on Thu Mar 31 at 00:00:00 CEST 2024

Example

See sample file

2022-03-31 07:02:00,1982022-03-31 09:01:59,968 INFO info.magnolia.multisite.registry.MultiSiteRegistry: Following sites are registered: [sportstation, travel].
2022-03-31 10:00:00,0852022-03-31 12:00:00,002 INFO info.magnolia.module.scheduler.CommandJob : Starting job [cleanTempFiles]...
2022-03-31 10:00:00,0852022-03-31 12:00:00,003 INFO info.magnolia.module.scheduler.CommandJob : Job executed successfully [cleanTempFiles]

Magnolia Frontend

Magnolia Frontend displays log information from Kubernetes Pods associated with the Magnolia frontend. You can access the pods logs by going to your Cockpit and navigating to the Logs section.

You can select up to the last 7 days for this filter.
How long do you keep the logs?

Generally, we keep logs for 30 days. However, for your deployment, you may configure a different duration.

From Logs > Magnolia Frontend:

  1. Select your desired Release from the dropdown list.

  2. Select your desired Frontend pod from the dropdown list.

  3. Select your desired Frontend component from the dropdown list.

    This is typically the public or author instance.

  4. Select your desired Date Range.

  5. Input any filter terms under Term. This filters the results by the term you’ve entered.

  6. Click Apply filters.

Log format

Log fields

Field Description Example

date

string

The log date.

"[14/Mar/2022:16:01:50 +0000]"

log level

string

The severity of the log such as INFO or WARN.

INFO

log message

string

The log message.

info.magnolia.module.scheduler.SchedulerModule : Job configScan added [0 0 0 * * ?]. Will fire for the first time on Thu Mar 31 at 00:00:00 CEST 2024

Example

See sample file

2022-03-31 07:02:00,1982022-03-31 09:01:59,968 INFO info.magnolia.multisite.registry.MultiSiteRegistry: Following sites are registered: [sportstation, travel].
2022-03-31 10:00:00,0852022-03-31 12:00:00,002 INFO info.magnolia.module.scheduler.CommandJob : Starting job [cleanTempFiles]...
2022-03-31 10:00:00,0852022-03-31 12:00:00,003 INFO info.magnolia.module.scheduler.CommandJob : Job executed successfully [cleanTempFiles]

Fastly domain logs

PaaS stores Fastly cache logs. The default setup and deployment stores customer IPs for a configurable amount of time. However, if you do not want customer IPs included in the logs at all, this is also something that can be configured.

You can select up to the last 7 days for this filter.
How long do you keep the logs?

Generally, we keep logs for 30 days. However, for your deployment, you may configure a different duration.

From Logs > Domains:

View from the Cockpit

domain logs

  1. Select your desired Domain name.

  2. Select your desired Date range.

  3. If desired, enter a term to filter on.

  4. Click Apply filters.

Log format

Each cache log is broken down by host and tenant. Hosts are the host website and tenants are the individual tenant within the PaaS deployment.

Example

host = www.magnolia-cms.com and tenant = magnolia

Log fields

Field Description Example

response length

integer

The size of response in bytes, excluding HTTP headers.

86601

cache_status

string

The cache status.

possible values

  • PASS

  • MISS

  • HIT

  • UNKNOWN

"PASS"

cluster_name

string

The name of the Kubernetes cluster.

"magnolia-production"

date

string

The log date.

"[14/Mar/2022:16:01:50 +0000]"

host

string

The host URL.

"www.magnolia-cms.com"

ip

string

The IP of the tenant.

"217.243.XXX.XX"

method

string

The method used.

"GET"

path

string

The URL path.

"/path/ch"

protocol

string

The HTTP protocol used.

"HTTP/1.1"

request_time

integer

The request time in milliseconds.

22

round_trip

integer

The total round trip time in milliseconds.

5574

wr_decision

The waiting room decision.

possible values

  • anon: The initial state. This is an anonymous user who needs a cookie set to enter the waiting room.

  • wait: The user must wait. This is a user that already has a cookie with an expiry time set.

  • re-wait: The user has already waited for the initial expiry duration. However, the system decided to force the user to wait again with a new cookie expiry time.

  • allow: This is the final state. The user has waited the full duration of the cookie expiry time. The system has now allowed the user to enter the waiting room.

  • deny: The system has denied access to the user or an error has occurred with the system.

anon

wr_expires

The time left until the next waiting room decision (in milliseconds).

1706345190

status

integer

The HTTP status code.

200

ts

date:time

The timestamp in ISO 8601 format.

2022-03-14T16:01:51.596Z

tsNs

integer

The timestamp in nanoseconds.

1647273711596698629

zone

string

Which CDN data center this request hit.

"HHN"

WAF logs

WAF logs displays log information from your Web Application Firewall rules. You can access the WAF logs by going to your Cockpit and navigating to the Logs section.

You can select up to the last 7 days for this filter.
How long do you keep the logs?

Generally, we keep logs for 30 days. However, for your deployment, you may configure a different duration.

From Logs > WAF:

View from the Cockpit

waf logs

  1. Select your desired Domain name from the dropdown list.

  2. Select your desired Date range.

  1. If desired, enter a term to filter on.

  2. Click Apply filters.

Log format

Log fields

Field Description Example

Start Time

string

The start time for the request.

"2022-06-14 12:59:42,971"

Blocked

boolean

Boolean stating if the request was blocked.

  • 0 - not blocked

  • 1 - blocked

See waf.blocked for more details.

1

Datacenter

string

The Datacenter through which the request passed.

LGB

Client IP

string

The client IP address.

205.XXX.31.23

Request Method

string

The request method.

GET

URI

string

The relative path of your site the request was attempting to access.

/

Status

integer

The HTTP status code of the request.

308

Kubernetes ingress logs

Kubernetes ingress logs displays log information from Kubernetes ingresses. You can access the Ingress logs by going to your Cockpit and navigating to the Logs section.

You can select up to the last 7 days for this filter.
How long do you keep the logs?

Generally, we keep logs for 30 days. However, for your deployment, you may configure a different duration.

From Logs > Ingresses:

  1. Select your desired Service from the dropdown list.

  2. Select your desired Date range.

  1. If desired, enter a term to filter on.

  2. Click Apply filters.

Log format

Example log entry
6/6/2024, 4:18:46 PM	157.52.67.55 - - [10/Jun/2024:15:18:46 +0000] "GET /.rest/cockpit/v1/cluster/statistics?clusterId=c-r5veq&serviceName=GET_RANCHER_CLUSTER_PROVIDER&timeBased=false HTTP/1.1" 200 34 "https://cockpit.customer.magnolia-platform.com/cockpit/v1/cluster/statistics?clusterId=c-r5veq&" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36" 3720 0.041 [prod-prod-magnolia-helm-public-svc-http] [] 10.41.3.131:8080 34 0.041 200 9c3rf24w1od91491313735979dc22bj9
Description Sample value

1

Log entry timestamp

6/6/2024, 1:17:39 PM

2

Client IP address

192.168.1.1

3

Client identity and authenticated user (unused)

- -

4

Request timestamp

[16/Jun/2023:19:33:51 +0000]

5

HTTP request method, URL, and version

"GET /api/v1/resource?id=123 HTTP/1.1"

6

HTTP status code

200

7

Response size in bytes

512

8

Referrer URL

"https://example.com/referrer"

9

User-agent string

"Mozilla/5.0 (Windows NT 10.0; Win64; x64) …​ Safari/537.36"

10

Total request time in milliseconds

3570

11

Backend connection time in seconds

0.112

12

Backend service name

[service-name]

13

Additional info/annotations (empty)

[]

14

Backend server IP address and port

10.42.1.224:8080

15

Response size in bytes (repeated)

512

16

Backend processing time in seconds (repeated)

0.112

17

HTTP status code (repeated)

200

18

Unique request identifier

abcdef1234567890abcdef1234567890

Enterprise search logs

PaaS stores Enterprise search logs. You can access the logs by going to your Cockpit and navigating to the Logs section. Enterprise search logs store a range of information from application errors to slow queries.

You can select up to the last 7 days for this filter.
How long do you keep the logs?

Generally, we keep logs for 30 days. However, for your deployment, you may configure a different duration.

From Logs > Enterprise search:

  1. Select your desired Release from the dropdown list.

  2. Select your desired Date range.

  1. Click Apply filters.

For more information on what you can see in these particular logs, see Solr logging.

Audit logs

PaaS stores audit logs. Audit logs show different actions triggered by your team while they navigate and use the Cockpit. These actions range from logins to those performing backup operations.

You can select up to the last 7 days for this filter.
How long do you keep the logs?

Generally, we keep logs for 30 days. However, for your deployment, you may configure a different duration.

From Logs > Audit:

View from the Cockpit

audit logs

  1. Select your desired API from the dropdown.

  2. If desired, enter a username to filter on.

  3. Select your desired Date range.

  4. If desired, enter a term to filter on.

  5. Click Apply filters.

Log format

Each audit log provides a timestamp along with other pertinent information. See the Log fields below for more details.

Log fields

Field Description Example

username

string

The username of the person or entity that performed the action.

person@example.com

action

string

The action performed. This is typically an API operation.

example values

  • getUsers

  • getFeatures

  • getClusters

  • getAuditLogs

getUsers

message

object

An object containing information about the action.

 
{
  "username": "person@magnolia-cms.com",
  "resource": "NotificationResource",
  "action": "getNotifications",
  "type": "audit",
  "parameters": {
    "displayOnLogin": "true",
    "archived": "false",
    "read": "false",
    "size": "10",
    "countOnly": "false",
    "term": "null",
    "from": "null",
    "to": "null",
    "page": "0",
    "sort": "null",
    "tenant": "cockpit"
  },
  "ip": "142.248.74.130"
}

timestamp

date

The log timestamp. This is the date and time on which the action occurred.

"2024-01-18T04:01:32.139Z"
Feedback

PaaS

×

Location

This widget lets you know where you are on the docs site.

You are currently perusing through the Magnolia PaaS docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules