Cloud API Migration for AWS and Azure using Service Graph Connectors
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2024 09:22 AM
We are doing a cloud API migration for AWS and azure using service graph connectors.
Steps taken so far:
Performed the guided setup for both AWS and AZURE.
Ran all scripts and scheduled jobs.
Created Service account to pull data.
Authentication Success.
Customer was still using probes so migrated them to patterns for SGC to work.
Updated required plugins.
Checked all discovery patterns to be active for pulling cloud data.
Issue:Still unable to pull all required data from AZURE and AWS.We are still getting old historical data.For some strange resons our service graph connectors are not working as expected.
Could anyone please tell me how can we mitigate this issue?
Error logs attached for reference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-26-2024 01:33 AM
I'm sorry, but as a text-based AI, I'm unable to view or analyze attached files such as error logs. However, I can provide some general troubleshooting steps for issues with Service Graph Connectors (SGC) in ServiceNow:
1. **Check the Service Account Permissions**: Ensure that the service account used to pull data from AWS and Azure has the necessary permissions. It should have read access to all the resources you want to discover.
2. **Check the Discovery Schedule**: Make sure that the discovery schedule is set up correctly and is running as expected.
3. **Check the Discovery Logs**: Review the discovery logs for any errors or warnings. This can provide clues about what's going wrong.
4. **Check the MID Server**: Ensure that the MID Server used for discovery is up and running. Also, check if it has the necessary capabilities to discover AWS and Azure resources.
5. **Check the Patterns**: Make sure that the patterns used for discovery are correct and active.
6. **Clear Old Data**: If old historical data is causing issues, you might need to clear it. However, be careful with this step as it can lead to data loss.
7. **Contact ServiceNow Support**: If you're still facing issues, it might be best to contact ServiceNow Support. They can help you troubleshoot the issue and provide specific guidance.
Remember, these are general steps and might not apply to your specific situation. It's always best to carefully analyze the issue and take steps accordingly.
For ServiceNow Live Classes, Books, Sample Resumes, Interview Questions, CSA Quizzes.
And getting better services's on ServiceNow you can visits our website.
Please visit : https://nowkb.com/home
Our Website :https://nowkb.com/home
nowKB.com