Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Events to CONNECT

Logging

  • Last UpdatedAug 20, 2024
  • 2 minute read

AVEVA agents write daily log messages for the AVEVA Events to CONNECT, the system, and OMF egress to flat text files in the following location:

%ProgramData%\OSIsoft\Adapters\EventsToCONNECT\Logs

Each message in the log displays the message severity level, timestamp, and the message itself.

Configure logging using Curl commands

Complete the following steps to configure logging. Use the PUT method in conjunction with the http:// localhost:5590/api/v1/configuration/<ComponentId>/Logging REST endpoint to initialize the configuration.

  1. Using a text editor, create an empty text file.

  2. Copy and paste an example configuration for logging into the file. For sample JSON, see Logging examples.

  3. Update the example JSON parameters for your environment. For a table of all available parameters, see Logging parameters.

  4. Save the file. For example, as ConfigureLogging.json.

  5. Open a command line session. Change directory to the location of ConfigureLogging.json.

  6. Enter the following cURL command (which uses the PUT method) to initialize the logging configuration.

    curl.exe --ntlm --negotiate -u <UserName> -d "@ConfigureLogging.json" -H "Content-Type: application/json" -X PUT "http://localhost:5590/api/v1/configuration/<ComponentId>/Logging"

    Notes:
    If you installed the agent to listen on a non-default port, update 5590 to the port number in use.
    For a list of other REST operations you can perform, like updating or retrieving a logging configuration, see Logging REST URLs.
    Any parameter not specified in the updated configuration file reverts to the default schema value

On successful execution, the log-level change takes effect immediately during runtime. The other configurations (log file size and file count) are updated after the agent is restarted.

Configure logging using the Configurator plugin

Default values for logging for system, data ingress, and data egress tabs are populated when Configurator is launched.

Update the system logging configuration

The post-install configurator displaying the Events to CONNECT Logging settings.

To update system logging parameters:

  1. In the General tab, edit the default logging parameters.

    For more information on the input fields, see the Logging parameters.

  2. Select Configure.

    Update the data ingress logging parameters

    The post-install configurator displaying the Events to CONNECT Data Ingress Logging settings.

    To update data ingress logging parameters:

    1. In the Data Ingress Logging tab, edit the default logging parameters.

      For more information on the input fields, see the Logging parameters.

    2. Select Configure.

      Update the data egress logging parameters

      The post-install configurator displaying the Events to CONNECT Data Egress Logging settings.

      To update data egress logging parameters:

      1. In the Data Egress tab, edit the default logging parameters.

        For more information on the input fields, see the Logging parameters.

      2. Select Configure.

        TitleResults for “How to create a CRG?”Also Available in