Is there a built-in command to disable an integration, or turn off "fetches incidents"?

cancel
Showing results for 
Search instead for 
Did you mean: 

Is there a built-in command to disable an integration, or turn off "fetches incidents"?

L1 Bithead

I'm working on a failsafe automation to shut down an integration if it fetches more than a certain threshold of events in a time period. Is it possible to disable an integration, or turn off the "fetches incidents" parameter, with a command? Or through the API?

1 ACCEPTED SOLUTION

Accepted Solutions

L3 Networker

Hi @jtorvald

Which integration are you working on? Some integrations allow you to set a max fetch parameter.

You can check the API call being made while saving the instance configurations by opening Developer Tools on your browser and checking the Network Tab for request headers and methods.

For this use case it should be a PUT request to /settings/integration with the request headers containing {"isFetch":False}

 

Hope this helps.

View solution in original post

3 REPLIES 3

L3 Networker

Hi @jtorvald

Which integration are you working on? Some integrations allow you to set a max fetch parameter.

You can check the API call being made while saving the instance configurations by opening Developer Tools on your browser and checking the Network Tab for request headers and methods.

For this use case it should be a PUT request to /settings/integration with the request headers containing {"isFetch":False}

 

Hope this helps.

L1 Bithead

Hi @amore, thank you so much for the help. I have confirmed that your suggestions are correct. Unfortunately, I'm experiencing 2 more problems when sending the request, I hope you might be able to help me a little more.


Problem 1 - When I send the PUT request using the built in http method, if the integration name and/or brand have whitespaces in them, I receive a response with StatusCode:400, detail:"Could not update integration", and error:"No suitable module for name : <integration instance name> and brand : <integration brand>"
Do you know if there is a specific way to encode the arguments in the JSON body so that XSOAR can parse the whitespaces in the PUT request correctly?

 

Problem 2 - When I send the PUT request using an integration name and brand that do NOT contain whitespaces, I receive a response with StatusCode:400, detail:"Could not update integration", and error:"<integration instance name> already exists (33)."
It seems XSOAR will not update the integration instance because it already exists, and I cannot identify any way to signify to XSOAR in the request that I wish to update an already existing instance. Do you know how to manage this?

L3 Networker

Hi @jtorvald , glad to hear the suggestion helped you.

Problem 1: Try by replacing the whitespaces with an underscore _

Problem 2: Can you share your PUT request body with me? Please remove any api keys and related confidential information from it.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!