Navigate to"Client Secret"Tab and copy"Client ID"and"Client
Secret".
Provide"Client ID"and"Client Secret"in the integration
configuration.
Navigate to"Generate Code"Tab, provide the following scopes:
"Site24x7.Operations.Read,Site24x7.Admin.Read" and some custom "Scope
Description".
Press on the"Create"button and copy the authorization code.
Navigate to action"Generate Refresh Token", provide authorization code
and execute it.
From the JSON result copy"refresh_token"and put the value in the"Refresh Token"in the integration configuration.
Configure Site24x7 integration in Google Security Operations
For detailed instructions on how to configure an integration in
Google SecOps, seeConfigure
integrations.
Integration parameters
Use the following parameters to configure the integration:
Parameter Display Name
Type
Default Value
Is Mandatory
Description
API Root
String
https://www.site24x7.{region}
Yes
API root of the Site24x7 instance.
Client ID
String
N/A
Yes
Client ID of the Site24x7 instance.
Client Secret
Password
N/A
Yes
Client Secret of the Site24x7 instance.
Refresh Token
Password
N/A
Yes
Refresh Token of the Site24x7 instance.
Verify SSL
Checkbox
Checked
Yes
If enabled, verifies that the SSL certificate for the connection to the Site24x7 server is valid.
Actions
Ping
Description
Test connectivity to Site24x7 with parameters provided at the integration
configuration page in the Google Security Operations Marketplace tab.
Run On
This action doesn't run on entities.
Action Results
Script Result
Script Result Name
Value Options
is_success
is_success=False
is_success
is_success=True
Case Wall
Case
Success
Fail
Message
if successful
true
false
Successfully connected to the Site24x7 server with the provided connection parameters!
not successful
false
true
Failed to connect to the Site24x7 server! Error: {0}".format(exception.stacktrace)
Generate Refresh Token
Description
Generate a refresh token needed for Integration configuration.
Parameters
Parameter Display Name
Type
Default Value
Is Mandatory
Description
Authorization Code
Password
N/A
Yes
Specify the authorization code.
Run On
This action doesn't run on entities, nor has mandatory input parameters.
Action Results
Script Result
Script Result Name
Value Options
is_success
is_success=False
is_success
is_success=True
JSON Result
{
"refresh_token": "{refresh token}"
}
``` ##### Case Wall
<table>
<thead>
<tr>
<th>Result type</th>
<th>Value/Description</th>
<th>Type</th>
</tr>
</thead>
<tbody>
<tr>
<td>Output message*</td>
<td><p><strong>The action should not fail nor stop a playbook execution:</strong><br><strong>if successful and no "error" in the response:</strong> <em></em> "Successfully generated the refresh token. Copy that refresh token and put it in the Integration configuration."</p><p><em></em></p><p><strong>The action should fail and stop a playbook execution:</strong><br><strong>if not successful:</strong> "Error executing action "{}". Reason: " {0}".format(exception.stacktrace)<br><strong></strong></p><p><strong>If "error" in the response (fail):</strong> "Error executing action "{}". Reason: " {0}".format(errors)</p></td>
<td>General</td>
</tr>
</tbody>
</table>
## Connector
## Site24x7 - Alerts Log Connector
#### Description
Pull information about alert logs from Site24x7.
#### Known Limitations
1. If the monitor has a whitespace in it, the connector won't be able to
extract it. Example: "backup site".
1. If the monitor name is "Critical", "Down", "Up" or "Trouble", the connector
may return unexpected results.
#### Configure Site24x7 - Alerts Log Connector in Google SecOps
For detailed instructions on how to configure a connector in
Google SecOps, see [Configuring the
connector](/chronicle/docs/soar/ingest/connectors/ingest-your-data-connectors).
##### Connector parameters
Use the following parameters to configure the connector:
<table>
<thead>
<tr>
<th>Parameter Display Name</th>
<th>Type</th>
<th>Default Value</th>
<th>Is Mandatory</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>Product Field Name</td>
<td>String</td>
<td>Product Name</td>
<td>Yes</td>
<td>Enter the source field name in order to retrieve the Product Field name.</td>
</tr>
<tr>
<td>Event Field Name</td>
<td>String</td>
<td>eventType</td>
<td>Yes</td>
<td>Enter the source field name in order to retrieve the Event Field name.</td>
</tr>
<tr>
<td>Environment Field Name</td>
<td>String</td>
<td>""</td>
<td>No</td>
<td><p>Describes the name of the field where the environment name is stored.</p>
<p>If the environment field isn't found, the environment is the default environment.</p></td>
</tr>
<tr>
<td>Environment Regex Pattern</td>
<td>String</td>
<td>.*</td>
<td>No</td>
<td><p>A regex pattern to run on the value found in the "Environment Field Name" field.</p>
<p>Default is .* to catch all and return the value unchanged.</p>
<p>Used to allow the user to manipulate the environment field via regex logic.</p>
<p>If the regex pattern is null or empty, or the environment value is null, the final environment result is the default environment.</p></td>
</tr>
<tr>
<td>Script Timeout (Seconds)</td>
<td>Integer</td>
<td>180</td>
<td>Yes</td>
<td>Timeout limit for the python process running the current script.</td>
</tr>
<tr>
<td>API Root</td>
<td>String</td>
<td>https://www.site24x7.{region}</td>
<td>Yes</td>
<td><p>API root of the Site24x7 instance. Possible api roots:</p>
<p>United States<br>https://www.site24x7.com</p>
<p>Europe<br>https://www.site24x7.eu</p>
<p>China<br>https://www.site24x7.cn</p>
<p>India<br>https://www.site24x7.in</p>
<p>Australia<br>https://www.site24x7.net.au</p></td>
</tr>
<tr>
<td>Client ID</td>
<td>String</td>
<td>N/A</td>
<td>Yes</td>
<td>Client ID of the Site24x7 instance.</td>
</tr>
<tr>
<td>Client Secret</td>
<td>Password</td>
<td>N/A</td>
<td>Yes</td>
<td>Client Secret of the Site24x7 instance.</td>
</tr>
<tr>
<td>Refresh Token</td>
<td>String</td>
<td></td>
<td>Yes</td>
<td>Site24x7 Refresh token. You can generate this token using action "Get Refresh Token"</td>
</tr>
<tr>
<td>Max Days Backwards</td>
<td>Integer</td>
<td>1</td>
<td>No</td>
<td>Amount of days from where to fetch alert logs.</td>
</tr>
<tr>
<td>Max Alert Logs To Fetch</td>
<td>Integer</td>
<td>10</td>
<td>No</td>
<td>How many alert logs to process per one connector iteration. Default: 100.</td>
</tr>
<tr>
<td>Use whitelist as a blacklist</td>
<td>Checkbox</td>
<td>Checked</td>
<td>Yes</td>
<td>If enabled, whitelist will be used as a blacklist.</td>
</tr>
<tr>
<td>Disable Overflow</td>
<td>Checkbox</td>
<td></td>
<td>Yes</td>
<td>If enabled, the connector will ignore the overflow mechanism.</td>
</tr>
<tr>
<td>Verify SSL</td>
<td>Checkbox</td>
<td>Checked</td>
<td>Yes</td>
<td>If enabled, verify the SSL certificate for the connection to the Site24x7 server is valid.</td>
</tr>
<tr>
<td>Proxy Server Address</td>
<td>String</td>
<td>N/A</td>
<td>No</td>
<td>The address of the proxy server to use.</td>
</tr>
<tr>
<td>Proxy Username</td>
<td>String</td>
<td>N/A</td>
<td>No</td>
<td>The proxy username to authenticate with.</td>
</tr>
<tr>
<td>Proxy Password</td>
<td>Password</td>
<td>N/A</td>
<td>No</td>
<td>The proxy password to authenticate with.</td>
</tr>
</tbody>
</table>
#### Connector rules
##### Proxy support
The connector supports proxy.Need more help?Get answers from Community members and Google SecOps professionals.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eSite24x7 integration version 3.0 requires setting an API root, selecting from locations like the United States, Europe, China, India, and Australia.\u003c/p\u003e\n"],["\u003cp\u003eThe integration process involves obtaining a "Client ID" and "Client Secret" from the Zoho API console and a "Refresh Token" by generating an authorization code.\u003c/p\u003e\n"],["\u003cp\u003eThe "Ping" action in Site24x7 allows testing connectivity to the server, and results in either a successful connection or a failure message.\u003c/p\u003e\n"],["\u003cp\u003eThe "Generate Refresh Token" action creates a token necessary for integration, which requires an authorization code as input and returns the refresh token in a JSON format.\u003c/p\u003e\n"],["\u003cp\u003eThe Site24x7 Alerts Log Connector retrieves alert log data with limitations, including issues with monitor names containing whitespace or being named "Critical," "Down," "Up," or "Trouble," and the connector also supports proxy configurations.\u003c/p\u003e\n"]]],[],null,["# Site24x7\n========\n\nIntegration version: 3.0\n\nHow to configure integration\n----------------------------\n\n1. As an API root select one of the following values:\n\n - United States - https://www.site24x7.com/api\n - Europe - https://www.site24x7.eu\n - China - https://www.site24x7.cn\n - India - https://www.site24x7.in\n - Australia - https://www.site24x7.net.au/api\n2. Navigate to Zoho API console:\n\n - United States - [https://accounts.zoho.com](https://accounts.zoho.com/)\n - Europe -[https://accounts.zoho.eu](https://accounts.zoho.eu/)\n - China -[https://accounts.zoho.com.cn](https://accounts.zoho.com.cn/)\n - India -[https://accounts.zoho.in](https://accounts.zoho.in/)\n - Australia -[https://accounts.zoho.com.au](https://accounts.zoho.com.au/)\n3. Press on \"Add Client\".\n\n4. Create Self Client.\n\n5. Navigate to **\"Client Secret\"** Tab and copy **\"Client ID\"** and **\"Client\n Secret\"**.\n\n6. Provide **\"Client ID\"** and **\"Client Secret\"** in the integration\n configuration.\n\n7. Navigate to **\"Generate Code\"** Tab, provide the following scopes:\n \"Site24x7.Operations.Read,Site24x7.Admin.Read\" and some custom \"Scope\n Description\".\n\n8. Press on the **\"Create\"** button and copy the authorization code.\n\n9. Navigate to action **\"Generate Refresh Token\"**, provide authorization code\n and execute it.\n\n10. From the JSON result copy **\"refresh_token\"** and put the value in the\n **\"Refresh Token\"** in the integration configuration.\n\nConfigure Site24x7 integration in Google Security Operations\n------------------------------------------------------------\n\nFor detailed instructions on how to configure an integration in\nGoogle SecOps, see [Configure\nintegrations](/chronicle/docs/soar/respond/integrations-setup/configure-integrations).\n\n### Integration parameters\n\nUse the following parameters to configure the integration:\n\n| **Note:** You can make changes at a later stage if needed. Once configured, the Instances can be used in Playbooks. For detailed information on configuring and supporting multiple instances, please see [Supporting multiple instances](/chronicle/docs/soar/respond/integrations-setup/supporting-multiple-instances).\n\nActions\n-------\n\n### Ping\n\n#### Description\n\nTest connectivity to Site24x7 with parameters provided at the integration\nconfiguration page in the Google Security Operations Marketplace tab.\n\n#### Run On\n\nThis action doesn't run on entities.\n\n#### Action Results\n\n##### Script Result\n\n##### Case Wall\n\n### Generate Refresh Token\n\n#### Description\n\nGenerate a refresh token needed for Integration configuration.\n\n#### Parameters\n\n#### Run On\n\nThis action doesn't run on entities, nor has mandatory input parameters.\n\n#### Action Results\n\n##### Script Result\n\n##### JSON Result\n\n {\n \"refresh_token\": \"{refresh token}\"\n }\n ``` ##### Case Wall\n\n \u003ctable\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003cth\u003eResult type\u003c/th\u003e\n \u003cth\u003eValue/Description\u003c/th\u003e\n \u003cth\u003eType\u003c/th\u003e\n \u003c/tr\u003e\n \u003c/thead\u003e\n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003eOutput message*\u003c/td\u003e\n \u003ctd\u003e\u003cp\u003e\u003cstrong\u003eThe action should not fail nor stop a playbook execution:\u003c/strong\u003e\u003cbr\u003e\u003cstrong\u003eif successful and no \"error\" in the response:\u003c/strong\u003e \u003cem\u003e\u003c/em\u003e \"Successfully generated the refresh token. Copy that refresh token and put it in the Integration configuration.\"\u003c/p\u003e\u003cp\u003e\u003cem\u003e\u003c/em\u003e\u003c/p\u003e\u003cp\u003e\u003cstrong\u003eThe action should fail and stop a playbook execution:\u003c/strong\u003e\u003cbr\u003e\u003cstrong\u003eif not successful:\u003c/strong\u003e \"Error executing action \"{}\". Reason: \" {0}\".format(exception.stacktrace)\u003cbr\u003e\u003cstrong\u003e\u003c/strong\u003e\u003c/p\u003e\u003cp\u003e\u003cstrong\u003eIf \"error\" in the response (fail):\u003c/strong\u003e \"Error executing action \"{}\". Reason: \" {0}\".format(errors)\u003c/p\u003e\u003c/td\u003e\n \u003ctd\u003eGeneral\u003c/td\u003e\n \u003c/tr\u003e\n \u003c/tbody\u003e\n \u003c/table\u003e\n\n ## Connector\n\n ## Site24x7 - Alerts Log Connector\n\n #### Description\n\n Pull information about alert logs from Site24x7.\n\n #### Known Limitations\n\n 1. If the monitor has a whitespace in it, the connector won't be able to\n extract it. Example: \"backup site\".\n 1. If the monitor name is \"Critical\", \"Down\", \"Up\" or \"Trouble\", the connector\n may return unexpected results.\n\n #### Configure Site24x7 - Alerts Log Connector in Google SecOps\n\n For detailed instructions on how to configure a connector in\n Google SecOps, see [Configuring the\n connector](/chronicle/docs/soar/ingest/connectors/ingest-your-data-connectors).\n\n ##### Connector parameters\n\n Use the following parameters to configure the connector:\n\n \u003ctable\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003cth\u003eParameter Display Name\u003c/th\u003e\n \u003cth\u003eType\u003c/th\u003e\n \u003cth\u003eDefault Value\u003c/th\u003e\n \u003cth\u003eIs Mandatory\u003c/th\u003e\n \u003cth\u003eDescription\u003c/th\u003e\n \u003c/tr\u003e\n \u003c/thead\u003e\n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003eProduct Field Name\u003c/td\u003e\n \u003ctd\u003eString\u003c/td\u003e\n \u003ctd\u003eProduct Name\u003c/td\u003e\n \u003ctd\u003eYes\u003c/td\u003e\n \u003ctd\u003eEnter the source field name in order to retrieve the Product Field name.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eEvent Field Name\u003c/td\u003e\n \u003ctd\u003eString\u003c/td\u003e\n \u003ctd\u003eeventType\u003c/td\u003e\n \u003ctd\u003eYes\u003c/td\u003e\n \u003ctd\u003eEnter the source field name in order to retrieve the Event Field name.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eEnvironment Field Name\u003c/td\u003e\n \u003ctd\u003eString\u003c/td\u003e\n \u003ctd\u003e\"\"\u003c/td\u003e\n \u003ctd\u003eNo\u003c/td\u003e\n \u003ctd\u003e\u003cp\u003eDescribes the name of the field where the environment name is stored.\u003c/p\u003e\n \u003cp\u003eIf the environment field isn't found, the environment is the default environment.\u003c/p\u003e\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eEnvironment Regex Pattern\u003c/td\u003e\n \u003ctd\u003eString\u003c/td\u003e\n \u003ctd\u003e.*\u003c/td\u003e\n \u003ctd\u003eNo\u003c/td\u003e\n \u003ctd\u003e\u003cp\u003eA regex pattern to run on the value found in the \"Environment Field Name\" field.\u003c/p\u003e\n \u003cp\u003eDefault is .* to catch all and return the value unchanged.\u003c/p\u003e\n \u003cp\u003eUsed to allow the user to manipulate the environment field via regex logic.\u003c/p\u003e\n \u003cp\u003eIf the regex pattern is null or empty, or the environment value is null, the final environment result is the default environment.\u003c/p\u003e\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eScript Timeout (Seconds)\u003c/td\u003e\n \u003ctd\u003eInteger\u003c/td\u003e\n \u003ctd\u003e180\u003c/td\u003e\n \u003ctd\u003eYes\u003c/td\u003e\n \u003ctd\u003eTimeout limit for the python process running the current script.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eAPI Root\u003c/td\u003e\n \u003ctd\u003eString\u003c/td\u003e\n \u003ctd\u003ehttps://www.site24x7.{region}\u003c/td\u003e\n \u003ctd\u003eYes\u003c/td\u003e\n \u003ctd\u003e\u003cp\u003eAPI root of the Site24x7 instance. Possible api roots:\u003c/p\u003e\n \u003cp\u003eUnited States\u003cbr\u003ehttps://www.site24x7.com\u003c/p\u003e\n \u003cp\u003eEurope\u003cbr\u003ehttps://www.site24x7.eu\u003c/p\u003e\n \u003cp\u003eChina\u003cbr\u003ehttps://www.site24x7.cn\u003c/p\u003e\n \u003cp\u003eIndia\u003cbr\u003ehttps://www.site24x7.in\u003c/p\u003e\n \u003cp\u003eAustralia\u003cbr\u003ehttps://www.site24x7.net.au\u003c/p\u003e\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eClient ID\u003c/td\u003e\n \u003ctd\u003eString\u003c/td\u003e\n \u003ctd\u003eN/A\u003c/td\u003e\n \u003ctd\u003eYes\u003c/td\u003e\n \u003ctd\u003eClient ID of the Site24x7 instance.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eClient Secret\u003c/td\u003e\n \u003ctd\u003ePassword\u003c/td\u003e\n \u003ctd\u003eN/A\u003c/td\u003e\n \u003ctd\u003eYes\u003c/td\u003e\n \u003ctd\u003eClient Secret of the Site24x7 instance.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eRefresh Token\u003c/td\u003e\n \u003ctd\u003eString\u003c/td\u003e\n \u003ctd\u003e\u003c/td\u003e\n \u003ctd\u003eYes\u003c/td\u003e\n \u003ctd\u003eSite24x7 Refresh token. You can generate this token using action \"Get Refresh Token\"\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eMax Days Backwards\u003c/td\u003e\n \u003ctd\u003eInteger\u003c/td\u003e\n \u003ctd\u003e1\u003c/td\u003e\n \u003ctd\u003eNo\u003c/td\u003e\n \u003ctd\u003eAmount of days from where to fetch alert logs.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eMax Alert Logs To Fetch\u003c/td\u003e\n \u003ctd\u003eInteger\u003c/td\u003e\n \u003ctd\u003e10\u003c/td\u003e\n \u003ctd\u003eNo\u003c/td\u003e\n \u003ctd\u003eHow many alert logs to process per one connector iteration. Default: 100.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eUse whitelist as a blacklist\u003c/td\u003e\n \u003ctd\u003eCheckbox\u003c/td\u003e\n \u003ctd\u003eChecked\u003c/td\u003e\n \u003ctd\u003eYes\u003c/td\u003e\n \u003ctd\u003eIf enabled, whitelist will be used as a blacklist.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eDisable Overflow\u003c/td\u003e\n \u003ctd\u003eCheckbox\u003c/td\u003e\n \u003ctd\u003e\u003c/td\u003e\n \u003ctd\u003eYes\u003c/td\u003e\n \u003ctd\u003eIf enabled, the connector will ignore the overflow mechanism.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eVerify SSL\u003c/td\u003e\n \u003ctd\u003eCheckbox\u003c/td\u003e\n \u003ctd\u003eChecked\u003c/td\u003e\n \u003ctd\u003eYes\u003c/td\u003e\n \u003ctd\u003eIf enabled, verify the SSL certificate for the connection to the Site24x7 server is valid.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eProxy Server Address\u003c/td\u003e\n \u003ctd\u003eString\u003c/td\u003e\n \u003ctd\u003eN/A\u003c/td\u003e\n \u003ctd\u003eNo\u003c/td\u003e\n \u003ctd\u003eThe address of the proxy server to use.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eProxy Username\u003c/td\u003e\n \u003ctd\u003eString\u003c/td\u003e\n \u003ctd\u003eN/A\u003c/td\u003e\n \u003ctd\u003eNo\u003c/td\u003e\n \u003ctd\u003eThe proxy username to authenticate with.\u003c/td\u003e\n \u003c/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003eProxy Password\u003c/td\u003e\n \u003ctd\u003ePassword\u003c/td\u003e\n \u003ctd\u003eN/A\u003c/td\u003e\n \u003ctd\u003eNo\u003c/td\u003e\n \u003ctd\u003eThe proxy password to authenticate with.\u003c/td\u003e\n \u003c/tr\u003e\n \u003c/tbody\u003e\n \u003c/table\u003e\n\n #### Connector rules\n\n ##### Proxy support\n\n The connector supports proxy.\n\n Need more help? https://security.googlecloudcommunity.com/google-security-operations-2"]]
