Nexeed
    • Introduction
    • User manual
      • Condition monitoring and its tabs
        • Live
        • Counters
        • Measurements
        • Events
        • Rules
        • View configuration
        • Details
      • Rules management
        • Rule types and standard functions
        • Rule details
      • Function configuration
      • Condition Monitoring widgets
      • Access Management
        • Application Roles
        • Fine-Grained Access Control and Configuration
        • How to Configure Organization Roles
    • Operations manual
      • Overview
      • System architecture and interfaces
        • System components
      • System requirements
        • General notes
        • cm/condition-monitoring-core
        • cm/rule-service-app
        • cm/rule-function-executor
        • cm/rule-result-aggregator
        • cm/rule-value-aggregator
        • cm/rule-value-provider
        • cm/stateful-function-executor
      • Migration from previous versions
        • Migration to 2.1+
        • Migration from CPM 1.5.4 to CM and RM 3.0.x (Nexeed IAS 2023.02.00.xx)
          • CPM to CM relational database migration
          • CPM to RM relational database migration
          • CM Influx database migration
          • Deletion of an old CPM installation
        • Resources mapping from MES to IAS Condition Monitoring
        • Migration to 4.0.0+ (Nexeed IAS 2024.01.00.xx)
        • Migration to 4.3.x (Nexeed IAS 2024.02.01.x)
        • Migration to 4.5.x (Nexeed IAS 2025.01.00.x)
        • Migration to 4.6.x (Nexeed IAS 2025.01.01.x)
        • Migration to 4.8.x (Nexeed IAS 2025.02.00.x)
        • Migration to 4.9.x (Nexeed IAS 2025.02.01.x)
      • Setup and configuration
        • Manual MACMA configuration after setting up a new tenant
        • RabbitMQ
        • Influx configuration
        • Kafka topics
        • Condition Monitoring - Helm Configuration
        • Advanced configuration parameters
          • cm/condition-monitoring-core
            • Common shared variables
            • Portal shared variables
            • MDM shared variables
            • RabbitMQ shared variables
            • OTEL shared variables
          • cm/rule-service-app
            • Rules Management shared variables
            • KAFKA shared variables
          • cm/rule-function-executor
          • cm/rule-result-aggregator
          • cm/rule-value-aggregator
          • cm/rule-value-provider
          • cm/stateful-function-executor
      • Start and shutdown
      • Regular operations
      • Failure handling
        • Rule Management Light Helm installation failing when Kafka is disabled or Kafka is not configured at all
        • User manual injection into Rule Management
        • Infrastructure outages: health verification Endpoints
        • OPP/PPMP are not received in CM
        • Master data (Devices, Facilities, Measuring Points, DeviceTypes) is missing in CM
        • CM is not visible in the portal
        • How to verify if the broker is out of sync
      • Backup and Restore
      • Logging and monitoring
        • General logging characteristics
        • Required monitoring
        • General logging format
        • Request-based logging format
        • Security logging format
        • Lifecycle logging format
        • Module health Endpoints and K8s probes
      • Known limitations
    • API documentation
      • Condition Monitoring HTTP API
      • Rules Management HTTP API
    • Glossary
Condition Monitoring
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Direct Data Link
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Condition Monitoring
  • Operations manual
  • Logging and monitoring
  • General logging characteristics
preview 4.10.0

General logging characteristics

  1. Requests are not logged per default
    Request are not logged per default unless an error occurs.

  2. Request based logging on demand
    Request based logging can be activated by changing the log level via environment variables, see Condition Monitoring - Helm Configuration.

  3. Configurable LogLevel
    Log level can be configured via environment variables, see Condition Monitoring - Helm Configuration.

  4. Log analysis tool independent logging
    A technology independent log pattern is used to process logs from all IAS modules in one logging system.

  5. Single line messages
    Logs are written as single line formatted json.

  6. Log to stdout
    Logs are written to stdout, for the purpose of being collected from there.

  7. Log in english
    Log message which are not presented to the "end-user" are written in English.

Loglevel guidelines

Preliminary Remark:
Logging can be configured during setup and configuration phase, see Condition Monitoring - Helm Configuration.

TRACE - Anything at statement level like "start to calculate something", "query something", "loop x of y", etc…​ is logged at TRACE level.

DEBUG - Anything at method or request processing level e.g.

  • "method entered" or "return with …​." is logged at DEBUG level

  • "HTTP GET /someresource took 5 seconds status 200" but also 4xy statuses

INFO - In the following cases the information is logged at INFO level, e.g.

  • Process life cycle messages, like

    • application started

    • application ready

    • shutdown application

  • Administrative events, like

    • (re)load or flush caches

    • (re)load configuration

    • database migrations

WARN - Uncommon behaviour or situations, e.g.

  • unavailability of services

  • security related events (potentially malicious)

  • handled failures which prevent the application to work normally as long as the application is able to recover automatically

ERROR - Anything which potentially leads to unexpected behaviour or crashes, e.g.

  • unhandled failures

  • implementation failures

Examples

One Line Formatted LIFE-CYCLE Log Example

{"timestamp":"2017-08-01T07:48:09.916Z","environment":"AZURE","system":"PROD","product":"nexeed-cm","application":"condition-monitoring-core-service","version":"1.0.1","instance":"3ae26cd4-7014-11e9-a923-1681be663d3e","thread":"thread-1","logger":"LIFE-CYCLE","loglevel":"INFO","status":"INITIALIZATION","message":"initialize masterdata cache"}

Pretty Printed LIFE-CYCLE Log Example

{
    "timestamp":    "2017-08-01T07:48:09.916Z",
    "environment":  "AZURE",
    "system":       "PROD",
    "product":      "nexeed-cm",
    "application":  "condition-monitoring-core-service",
    "version":      "3.0.1",
    "instance":     "3ae26cd4-7014-11e9-a923-1681be663d3e",
    "thread":       "thread-1",
    "logger":       "LIFE-CYCLE",
    "loglevel":     "INFO",
    "status":       "INITIALIZATION",
    "message":      "initialize masterdata cache"
}

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses