BigFix Integration Data Inconsistency via Service Graph Connector

[jssee]

We would like to seek your assistance regarding issues encountered with our BigFix integration to ServiceNow using the Service Graph Connector. Although the integration is partially working, we are observing data inconsistencies and incomplete ingestion that require further validation.

Observed Issues:

• Significant discrepancy in record count:
  • BigFix Console reports approximately 12,600+ computers, while only about 10,500+ records are ingested into ServiceNow.
• Some expected data attributes are not consistently populated, such as:
  • IP address
  • Assigned user
• We observed that some configuration items are updated successfully, but others appear to be missing or skipped, raising concern that:
  • The integration execution may be completing only partially, or
  • Certain records may be excluded due to identifier or transform logic
• We would also like to confirm whether any records are being rejected during ingestion and where these can be identified in logs or execution results.

Environment Details:

• Integration: Service Graph Connector for BigFix
• Role: ITOM Admin
• Attachment size configuration has already been reviewed and adjusted where applicable

Requests for Assistance:

1. Confirmation on whether the integration jobs are fully completing versus partially ingesting data
2. Guidance on identifying skipped or rejected records during ingestion
3. Validation of identifier rules and transform maps used by the BigFix connector
4. Best practices to ensure record parity between BigFix and ServiceNow
5. Recommended steps to verify ingestion completeness and data accuracy

[Cotulo]

test