LogoLogo
Contact Uscybus.io
Connectware 1.9.0
Connectware 1.9.0
  • Getting Started
    • Introduction
    • Installing Connectware
      • System Requirements
      • Acquiring your License Key
      • Installing Connectware on Docker
      • Installing Connectware on Kubernetes
    • Connectware Admin UI
    • Basic Components of Connectware
    • Connecting your First Machine
      • Your First Service Commissioning File
  • Documentation
    • Services
      • Service Commissioning Files
        • Structure of Service Commissioning Files
          • description
          • metadata
          • parameters
          • definitions
          • resources
            • Cybus::Connection
            • Cybus::Endpoint
            • Cybus:Mapping
            • Cybus::Container
              • Docker problem with network changes
            • Cybus::Link
            • Cybus::IngressRoute
            • Cybus::User
            • Cybus::Role
            • Cybus::Volume
            • Cybus::File
            • Cybus::Server
            • Cybus::Node
        • Sample Service Commissioning Files
          • Modbus
            • “Bearbeitungszentrum BAZ” - Single File
            • “Bearbeitungszentrum BAZ” - Multiple Files
            • “Bearbeitungszentrum BAZ” - Single File and Custom Topics
            • “Bearbeitungszentrum BAZ” - Agent Mode
          • Machine Condition Monitoring : OPC UA + InfluxDB + Grafana Dashboard
            • “Machine Condition Monitoring Example” - Single File
          • Machine Utilization Example (Multi file service composition) : Modbus TCP + InfluxDB + Grafana + MSS
            • “Machine Utilization Example” - Machine Connectivity
            • “Machine Utilization Example” - Dashboards with role based access permission
            • “Machine Utilization Example” - Push data to MSSQL Database
      • Services View
      • Setting Up and Configuring Services
        • Installing Services
        • Enabling Services
        • Updating Services
        • Disabling Services
        • Deleting Services
      • Service Details View
      • FlowSync
        • Example 1 - Node with Transaction Mode (HTTP)
        • Example 2 - Node Responds (HTTP)
        • Example 3 - Node with Error (HTTP)
        • Example 4 - Node with Timeout Error Code and Error Message (HTTP)
        • Example 5 - Full Transactional Data Flow (HTTP)
        • Example 6 - Full Transactional Data Flow (OPC UA)
      • ServiceID
      • Inter-Service Referencing
      • Deviation
      • Service Logs
        • Logs of Individual Services
        • Logs of All Services
      • Rule Engine
        • Data Processing Rules
        • Rule Sandbox
      • Shared Subscriptions
        • Setting Up Shared Subscriptions
      • API Definition
    • Resources
      • Servers
      • Containers
      • Volumes
      • Connections
      • Endpoints
      • Mappings
      • Nodes
      • API Definition
    • User Management
      • Users and Roles View
      • Users
      • Roles
      • Permissions
      • Password Policy Rules
      • Default Admin User
      • MQTT Users
      • Adding a MQTT Publish Prefix for Users
      • Multi-Factor Authentication
      • Long lived JSON Web Tokens
      • Access Permissions for Admin-UI
        • UI Access
        • Minimum Access Role Pages
      • API Definition
    • Client Registry
      • Implicit Flow
      • Explicit Flow
      • Granting Access
      • API Definition
    • Certificates
    • Monitoring
      • Data Explorer
      • Live Data
    • Workbench
      • Flows in Git Repositories
    • System Status
      • Info
      • Metrics
      • Status
      • Retrieving More System Information
      • System Health
      • API Definition
    • Backup and Restore
      • Volumes
      • User Database
    • Configuration
      • Environment Variables
      • LDAP Configuration
      • MFA Configuration
    • Agents
      • Agents View
      • Installing Agents
        • Installing Agents via Docker
        • Installing Agents via Docker Compose
        • Installing Agents via Kubernetes
        • Using Mutual TLS for Agents
      • Registering Agents in Connectware
      • Using Agents
      • Monitoring Agents
      • Troubleshooting Agents
    • Industry Protocol Details
      • ADS
        • AdsConnection
        • AdsEndpoint
      • BACnet
        • BacnetConnection
        • BacnetEndpoint
      • EtherNet/IP
        • EthernetIpConnection
        • EthernetIpEndpoint
      • Focas
        • FocasConnection
        • FocasEndpoint
      • Generic VRPC
        • GenericVrpcConnection
        • GenericVrpcEndpoint
      • Hottinger Baldwin Messtechnik (HBM)
        • HbmdaqConnection
        • HbmdaqEndpoint
      • Heidenhain DNC
        • HeidenhainConnection
        • HeidenhainEndpoint
      • HTTP/REST
        • HttpConnection
        • HttpEndpoint
      • HTTP Server
        • HttpServer
        • HttpNode
      • InfluxDB
        • InfluxdbConnection
        • InfluxdbEndpoint
      • Kafka
        • KafkaConnection
        • KafkaEndpoint
      • Modbus/TCP
        • ModbusConnection
        • ModbusEndpoint
      • MQTT
        • MqttConnection
        • MqttEndpoint
      • MSSQL
        • MssqlConnection
        • MssqlEndpoint
      • OPC DA
        • OpcdaConnection
        • OpcdaEndpoint
      • OPC UA
        • OPC UA Client
          • OpcuaConnection
          • OpcuaEndpoint
        • OPC UA Server
          • OpcuaServer
          • OpcuaNode
        • OPC UA Object Types
        • OPC UA Server References
          • OpcuaReferenceNode
          • OpcuaObjectNode
      • Siemens SIMATIC S7
        • S7Connection
        • S7Endpoint
      • Shdr
        • ShdrConnection
        • ShdrEndpoint
      • Sinumerik
        • SinumerikConnection
        • SinumerikEndpoint
      • Sopas
        • SopasConnection
        • SopasEndpoint
      • SQL
        • SqlConnection
        • SqlEndpoint
      • Werma WIN Ethernet
        • WermaConnection
        • WermaEndpoint
      • Systemstate
        • SystemstateConnection
        • SystemstateEndpoint
      • API Definition
    • Connectware Licensing
    • Changelog
      • General changes from 0.x to 1.0
        • Upgrading from 0.x to 1.0
    • Upgrade Guide
      • Upgrading from 1.x to 1.7.0
      • Upgrading from 1.x to 1.5.0
Powered by GitBook
LogoLogo

Cybus

  • Terms and Condition
  • Imprint
  • Data Privacy

© Copyright 2025, Cybus GmbH

On this page
  • Overview
  • Name
  • State
  • Uptime
  • Controls
  • Container Details View
  • Configuration
  • Environment Variables
  • Container Logs
  • Controls

Was this helpful?

  1. Documentation
  2. System Status

Status

PreviousMetricsNextRetrieving More System Information

Last updated 5 months ago

Was this helpful?

  1. On the navigation panel, click System.

2. This opens the status view which contains information about all running Connectware containers.

Overview

The status view contains the following information

Name

The name of the container.

State

Connectware containers can enter one of the following states:

  • running -> The container is working as expected.

  • starting -> The container is currently in the process of starting.

  • stopping -> The container is currently stopping.

  • restarting -> The container has triggered the restarting procedure.

  • exited -> The container was shut down and won’t restart automatically.

  • created -> The container was created but not yet started.

Uptime

The time the container is already running.

Controls

To restart Connectware containers, select one or more instances (1.) and click Restart (2.) on the toolbar.

Container Details View

The Container Details view contains more information about a single container. To open this view, select one of the containers displayed in the status view.

A window similar to the picture below will open.

To unfold the individual resources just click on the appropriate tab.

Configuration

The Configuration tab shows information about container settings including

  • capAdd -> Added capabilities.

  • exposedPorts -> Ports exposed by the container.

  • image -> The docker image used by the container.

  • privileged -> Shows if the container is running in privileged mode.

  • workingDir -> The working directory inside the container.

Environment Variables

The Environment Variables tab shows all environment variables available to the processes inside the container at runtime.

Container Logs

The Container Logs tab shows the logging message of the selected container. In the toolbar at the top right of this section, there are the following buttons:

  • Search for log entries containing the entered keyword. This also filters the current table.

  • Download CSV to download the displayed rows of the log file as a CSV (Comma-Separated-Value) text file (Note: Log lines outside of the window are not downloaded, and the complete download is limited to the most recent 500 lines; use Download raw log for a complete log download)

  • View columns to select the columns to be shown

  • Filter table to select filter criteria to have only a subset of rows shown

  • Download raw logs to download the full log file in order to pass on this file to Cybus Support for in-depth issue resolution. See below for an explanation of the file format.

  • and Refresh to refresh (reload) the currently shown log messages.

Controls

The details view offers capabilities to

  • Stop -> Stop the selected container.

  • Restart -> Restart the selected container.

  • Delete -> Delete the selected container (the container has to be stopped first).

  • Expand all Resources -> Unfold all of the tabs described above.

In addition to these global controls, each details tab provides individual controls to filter, organize, or search the data provided.

Search

Search for entries containing the entered keywords. This also filters the current table.

Show Columns

Select the columns to be shown.

Filter

(Not in Logs section.) Select from available options to filter the rows to be shown.

Refresh

Only available in the Container Logs section. This option reloads the displayed logs.

The “Download raw logs” button returns the stream output of “docker logs” directly, whereby each log line is prepended by some control characters. The exact stream format is described in the Docker API documentation of the “Attach” endpoint, see e.g. . Basically, each line is prepended by an eight byte header and another two byte marker. For text file processing, the first 10 bytes of each line should hence be ignored. A suitable Linux command line tool for that would be cut -b11- < inputfile.log where the output lines are printed from the 11th byte onwards each.

https://docs.docker.com/engine/api/v1.41/#operation/ContainerAttach
../_images/search.png
../_images/columns.png
../_images/filter.png
../_images/refresh.png