How to fetch plant integration (connector) logs?
Log in on the connector (plant integration) server.
Open the folder 'c:/inetpub/<myconnector>/logs'
Select all .log files and compress them into a .zip file.
Open the browser and browse to https://files.trendminer.com
Log in using your TrendMiner file server credentials. If you don't know these or your credentials are not working, please contact your TrendMiner Customer Success Manager or send a support request to support@trendminer.com
Click on upload.php
Select your file and enter your company or plant name and click 'Send File'.
Plant integration logs
Logging
Changes should be performed in NLog.config inside Plant Integrations website folder.
Logging archives rotation/size
By default logs are rotated at when they reach 10Mb and a maximum of 4 files are kept.
This values can be changed by editing the NLog.config file
Attributes that can be changed
archiveAboveSize | Specifies the size in bytes that the log file will be rotated Default: 10000000 |
maxArchiveFiles | Specifies the number of archive files Default: 3 |
Log Level
Changing the log level can be done using the API at /api/log or by changing directly the configuration files.
Open the NLog.config and change the rule for logger "*" with one of the following settings:
Level | Description |
|---|---|
Error | Only show error messages |
Warn | Show Error and Warning messages. Default setting |
Info | Show Info, Warning and Error messages. Shows all requests to Plant Integration and how long they took |
Debug | Show Debug, Info, Warning and Error messages. Can be very verbose. It has important information for debugging purposes |
Trace | Show all log messages. Can be very extremely verbose. Logged information can have points data. |
e.g.:
<rules>
<logger name="*" minlevel="Info" writeTo="logfile" />
</rules>Trace Tag
Specific tag can be traced to analyse process of getting data using processed points output and easier to reproduce steps using logged request and queries. This is designed to log all information with minimum debug level output to ensure that trace information would be logged even after IIS pool is reset and logging level is sufficient for tracing. It is required for long term tracing and minimising useless logged information when problem is not consistent and occurs for specific tags.
Parameter | Description |
|---|---|
ParameterDescriptiontrace.tags | Defines comma separated tag names for which detailed information would be traced. e.g. BA:LEVEL.1,BA:CONC.1 NoteCurrently logs all requests for traced tag and outputs type definition, data query and points for OsiSoft PI OLEDB provider. |