Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to connect Meraki API connector #8777

Closed
philfy20 opened this issue Aug 14, 2023 · 14 comments
Closed

Unable to connect Meraki API connector #8777

philfy20 opened this issue Aug 14, 2023 · 14 comments
Assignees
Labels
Connector Connector specialty review needed

Comments

@philfy20
Copy link

philfy20 commented Aug 14, 2023

Describe the bug
I am unable to connect to the Meraki REST API data connector is looks like the Meraki API is not providing the expected data (schema) and is failing

To Reproduce
Steps to reproduce the behavior:

  1. Install solution https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/CiscoMeraki/Data%20Connectors/CiscoMerakiNativePollerConnector
  2. Connector to connector providing organisation ID and AP KEY
  3. Click connect
  4. Then get error message
    Failed to create Connector resource of kind Log Analytics Table, error: User provided schema is invalid, due to - HttpClient: Response status code does not indicate success - 400 (Bad Request), for request - cms/apiv2/workspaces/............................/tables/CiscoMerakiNativePoller_CL/validate?intent=PUT, due to reason - [Table validation failed with following 5 errors: MSG 1015: Invalid value provided for data type: Double, in column DstGeoLatitude
    ;MSG 1015: Invalid value provided for data type: Double, in column DstGeoLongitude
    ;MSG 1015: Invalid value provided for data type: Double, in column SrcGeoLatitude
    ;MSG 1015: Invalid value provided for data type: Double, in column SrcGeoLongitude
    ;MSG 1041: Additional Fields Column Type should be of dynamic Data Type]. Operation Id: '654bb77f82c0b4dd69ab715013b9c00a'
    Expected behavior
    Connector should connect and ingest alerts from meraki

Additional context
Hitting the API directly the API does not provide details on latitude and longitude as per examples from Meraki - https://developer.cisco.com/meraki/api-latest/get-organization-appliance-security-events/

@github-actions
Copy link
Contributor

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

1 similar comment
@github-actions
Copy link
Contributor

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

@github-actions
Copy link
Contributor

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

@v-amolpatil v-amolpatil added the Connector Connector specialty review needed label Aug 14, 2023
@github-actions
Copy link
Contributor

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

1 similar comment
@github-actions
Copy link
Contributor

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

@v-sudkharat
Copy link
Contributor

Hi @philfy20, thanks for flagging this, we will soon get back to you on this. Thanks!

@v-sudkharat
Copy link
Contributor

Hi @philfy20, we are looking into this issue, and we will provide next update on 22-08-2023. Thanks!

@v-sudkharat
Copy link
Contributor

Hello @philfy20, we are connecting with our concerned team for this issue, once we get any information on this, we will update you. Thanks!

@v-sudkharat
Copy link
Contributor

v-sudkharat commented Aug 24, 2023

Hi @philfy20, we have made modification in data connector file. Please find attached zip and perform a custom deployment from Azure portal at your end. Let us know if it works for you so that once we receive a confirmation we will raise a PR with this file change.
Thanks!
azuredeploy_Cisco_Meraki_native_poller_connector.zip

@philfy20
Copy link
Author

@v-sudkharat connector can now connect which is good. Just waiting on a Meraki device to create a new alert to confirm end to end connector is working. Will update once this is done. Thanks

@v-sudkharat
Copy link
Contributor

Hi @philfy20, please let us know once you done. Thanks!

@philfy20
Copy link
Author

@v-sudkharat can confirm this has fixed the issue. Data connector can connect and ingest the alerts. Thanks

@v-sudkharat
Copy link
Contributor

Hi @philfy20, thanks for confirmation we will raise a PR with modification in data connector file. Closing this issue. If you still need support for this issue, feel free to re-open it any time. Thank you for your co-operation.

@v-sudkharat
Copy link
Contributor

Hi @philfy20, we are going to upgrade the solution with the changes; it is now in private preview. Please monitor the channel for further updates. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connector Connector specialty review needed
Projects
None yet
Development

No branches or pull requests

4 participants