Dear Community User! We are updating our platform to a new system.
Read more: Important information on the platform change.

cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

Get all data from Diagnosis/Logbook

Get all data from Diagnosis/Logbook

Elleshar
Established Member

Dear Community,

is there any possiblility/interface to get the whole data from the Logbook?
Not only one node. All.
When yes? Where? How to find this peace of documentation?
Are there anywhere more documentation?

Sincerely 
Elleshar 

3 REPLIES 3

CodeShepherd
Community Moderator
Community Moderator

See this post for information how to read all pending diagnostics via PLC in the actual version. For the next release 1.18 there are function blocks available for easier access.

See also this post how to get plain text out of the error codes.

Or do you like to really read the log file with all past messages?

I want to read the log file with all past messages.
I prefer a Rest-Api to filter. (Something like in CtrlX-Ui)
I don't want all syslogs.
I want all logs, which occurs to my "App".

Thanks for your help! 

nickH
Community Moderator
Community Moderator

Hi, 

in general: everything what you can do via the web-ui, you can also access via a rest api. 

So, if you would like to read logbook messages you can do a get query with a rest client to https://<ip of ctrlX CORE>/logbook/api/v2/entries. And with a additional parameter at your query (?unit=<your-snap-name>) you can filter for the unit you like. 

I tried this out with the help of the RESTED rest client, which is a add-on for the firefox browser. (There are also similar tools for other browsers as well). And just read out all the messages of the helloworld snap of the SDK. 

nickH_0-1670589910354.png

This is the response I got: 

nickH_1-1670589967585.png

 

Some additional information:

  • Please remember that you always have to authorize your query with a Bearer Token. Find out more about how to do that and how to use the Rest Api here
  • You can set the logbook to persistant for troubleshooting in the logbook settings. But persistent logging should be set only temporarily for troubleshooting and should be deactivated again immediately afterwards, as activating persistent logging causes the logs to be saved on a storage medium shortening the lifetime of the storage medium in case of a permanently high number of log entries! 
  • To store logs persistently over a longer period, you can use 'Remote Logging'.  Additional information about "Remote Logging" to a external server, can be found here

 

Best regards, 

Nick

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist