- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2023 07:14 PM
Hi,
Our service graph connector integration for JAMF is not working since we upgraded to Tokyo.
I see 2 distinct errors in the logs and not sure why these are logged.
1) 5500+ log entries with this message.
2) Error message even when CI's are loaded and created in snow.
Did anyone come across this ?? if so, what is the root cause or work around to avoid these ?
Appreciate your response!!
Thanks
Sindhuja
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2023 06:57 PM
Per Servicenow HI ticket , #1 is a bug and the workaround is to create a system property to filter those logs.
Property name:
glide.log_filter.terminal_context
Type:
String
Value : Ignoring message=(.*?) because context is already terminal
for #2 - was told to ignore these as the data was being loaded and transformed successfully. It due to the JAMF timeout (default - 30 mins), post which the Token is re-generated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2023 06:57 PM
Per Servicenow HI ticket , #1 is a bug and the workaround is to create a system property to filter those logs.
Property name:
glide.log_filter.terminal_context
Type:
String
Value : Ignoring message=(.*?) because context is already terminal
for #2 - was told to ignore these as the data was being loaded and transformed successfully. It due to the JAMF timeout (default - 30 mins), post which the Token is re-generated.