Integration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 03:30 AM
ServiceNow performance engagement team identified a slow integration transactions triggered by user SVCAXONIUS.INTEGRATION. /api/now/table/cmdb_rel_ci
Action items identified :
Action items identified : • Review usage of the '/api/now/table/cmdb_rel_ci' transaction by 'SVCAXONIUS.INTEGRATION' UserID • Review the purpose of reading entire 'cmdb_rel_ci' table. If this is not required, please add necessary filters to read only the required data
Can someone share how to resolve this issue step by step as a ITOM BAU Team member??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 04:46 AM
What did you already do and where are you stuck? It is literally saying what you need to do. Your integration is checking on the entire cmdb_rel_ci table, which is a huge one. Depending on the purpose of your integration (which is your first step: you need to know what the integration is for) you need to check why it is reading the entire table and not just on a (sub)set, based on conditions.
Example: if you need to update relations through that integration and you have a CI that needs to be checked, it should be sufficient to only read all records where that CI is parent/child and if it exists, check if it is correct and if it doesn't exist, create it.
You haven't shared anything about the integration, but in the worst case, it is running through the entire table for every CI, which is just very bad practice.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 09:00 AM
Thanks for sharing this suggetions
@Mark Manders wrote:What did you already do and where are you stuck? It is literally saying what you need to do. Your integration is checking on the entire cmdb_rel_ci table, which is a huge one. Depending on the purpose of your integration (which is your first step: you need to know what the integration is for) you need to check why it is reading the entire table and not just on a (sub)set, based on conditions.
Example: if you need to update relations through that integration and you have a CI that needs to be checked, it should be sufficient to only read all records where that CI is parent/child and if it exists, check if it is correct and if it doesn't exist, create it.
You haven't shared anything about the integration, but in the worst case, it is running through the entire table for every CI, which is just very bad practice.
but in order to check the Transaction Log i did not find any records that is being created by "SVCAXONIUS.INTEGRATION" user , how i can find the logs then further
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2025 04:46 AM
I am not able to find any transaction for 'SVCAXONIUS.INTEGRATION' this user .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2025 04:45 AM
I am not able to find any transaction for 'SVCAXONIUS.INTEGRATION' this user can someone suggest.