-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Description
Describe the bug
Our Quokka CCF Connector is not calling the API to poll data. We published this solution over a month ago and just recently discovering that it's not working. We've used debug logs on our side to see what's going on and the root cause is the CCF connector is not calling the API at all after the initial connection.
To Reproduce
Steps to reproduce the behavior:
- Go to Content Hubs
- Install Quokka Qscout QscoutAppEventsConnector
- Using an org id and org API key we provide to connect
- The deployment succeeds (connection is authenticated)
- Nothing happens. No new API polling calls. No error logs. Not from our side or Sentinel
- We placed a logger middleware in our API to record any incoming request and nothing was coming from Sentinel (except the initial connection)
Expected behavior
After the initial connection, it should keep polling data in the query timeframe we established. If there is any error that prevents the connector from continuing polling, it should be made aware.
Additional context
The connector we deployed manually during development was working. This involved creating the Custom Logs table, DCR, and DCE, and specifying them in the deployment template. However, when we use the CCF pattern using the createSolutionV3.ps1 tool, the resulting template produced the erroneous connector. We've tried editing the resources files in many ways but nothing made it work. Would really appreciate any help with our solution.
https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Quokka
We can provide a sample org id and api key as well