---
title: "Set Node Log Level of All Control Plane Nodes"
url: "https://nov18-dev.movespot.fyi/apis/konnect-runtime-groups-configuration-0/versions/af18902c-58f1-49d7-8ec2-9987b4e0d1bd/operations/put-debug-cluster-control-planes-nodes-log-level-log_level"
---

> Full API specification: https://nov18-dev.movespot.fyi/apis/konnect-runtime-groups-configuration-0/versions/af18902c-58f1-49d7-8ec2-9987b4e0d1bd.md

# Set Node Log Level of All Control Plane Nodes

`PUT` `/runtime-groups/{runtimeGroupId}/core-entities/debug/cluster/control-planes-nodes/log-level/{log_level}`

Operation ID: `put-debug-cluster-control-planes-nodes-log-level-log_level`

Change the log level of all Control Plane nodes deployed in Hybrid (CP/DP) cluster. See the [NGINX docs](http://nginx.org/en/docs/ngx_core_module.html#error_log) for a list of accepted values. Care must be taken when changing the log level of a node to `debug` in a production environment because the disk could fill up quickly. As soon as the debug logging finishes, revert back to a higher level such as notice. It’s currently not possible to change the log level of DP and DB-less nodes.

## Path parameters

- `log_level` (string, required) - Log levels are set in Kong’s configuration. Log levels increase in order of their severity
- `runtimeGroupId` (string, required)

## Responses

- `200` - OK

## OpenAPI definition

```yaml
openapi: 3.0.0
info:
  title: Konnect Runtime Groups Configuration
  version: 0.0.1
servers:
  - url: https://us.api.konghq.com/v2
    description: United-States Production region
  - url: https://eu.api.konghq.com/v2
    description: Europe Production region
  - url: https://au.api.konghq.com/v2
    description: Australia Production region
  - url: https://me.api.konghq.com/v2
    description: Middle-East Production region
  - url: https://in.api.konghq.com/v2
    description: India Production region
  - url: https://sg.api.konghq.com/v2
    description: Singapore Production region
paths:
  /runtime-groups/{runtimeGroupId}/core-entities/debug/cluster/control-planes-nodes/log-level/{log_level}:
    parameters:
      - name: log_level
        in: path
        description: Log levels are set in Kong’s configuration. Log levels increase in
          order of their severity
        required: true
        schema:
          type: string
          example: warn
          enum:
            - info
            - notice
            - warn
            - error
            - crit
      - name: runtimeGroupId
        in: path
        required: true
        schema:
          type: string
    put:
      operationId: put-debug-cluster-control-planes-nodes-log-level-log_level
      summary: Set Node Log Level of All Control Plane Nodes
      description: >
        Change the log level of all Control Plane nodes deployed in Hybrid
        (CP/DP) cluster.


        See the [NGINX
        docs](http://nginx.org/en/docs/ngx_core_module.html#error_log) for a
        list of accepted values.


        Care must be taken when changing the log level of a node to `debug` in a
        production environment because the disk could fill up quickly. As soon
        as the debug logging finishes, revert back to a higher level such as
        notice.


        It’s currently not possible to change the log level of DP and DB-less
        nodes.
      responses:
        "200":
          description: OK
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    description: Response message
                    type: string
                    example: log level changed
                x-examples:
                  Example 1:
                    message: log level changed
              examples:
                log level changed:
                  value:
                    message: log level changed
      tags:
        - Debug
security:
  - konnectAccessToken: []
  - personalAccessToken: []
components:
  securitySchemes:
    konnectAccessToken:
      type: http
      scheme: bearer
      description: >-
        The Konnect access token is meant to be used by the Konnect dashboard
        and the decK CLI to

        authenticate with.
    personalAccessToken:
      type: http
      scheme: bearer
      description: The personal access token is meant to be used as an alternative to
        basic-auth when accessing Konnect via APIs. You can generate a Personal
        Access Token (PAT) from the personal access token page in the Konnect
        dashboard.
```
