vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Hosts accessed from pipelines 

You can access hosts from the following types of pipelines: pull request, continuous integration, promotion, continuous deployment, and continuous compliance.



 Pull request pipelines 

The following table lists and describes each of the hosts that are accessed from pull request pipelines.



Table 1. Pull request pipeline hosts

 Host Description 

 https://hooks.slack.com/services When the Slack integration is configured, notifications are sent when pipelines start and finish. 
 https://otc-github-consolidated-broker.<region>.devops.cloud.ibm.com/github/token?git_id=integrated The OTC broker URL to fetch a Git token if one was not provided. 
 https://<region>.git.cloud.ibm.com Clones repos, and sets and checks the pull request status. 
 https://detect-secrets-client-version.s3.us-south Detects secrets checks for newer versions. 
 https://otcbroker.devopsinsights.cloud.ibm.com Checks the toolchain for Code Risk Analyzer support. 
 https://iam.cloud.ibm.com/identity/token Gets the IAM token. 
 https://gitsecure.us-south.devopsinsights.cloud.ibm.com The Code Risk Analyzer API. 
 https://vcurator.us-south.devopsinsights.cloud.ibm.com Code Risk Analyzer. 







 Continuous integration pipelines 

The following table lists and describes each of the hosts that are accessed from continuous integration pipelines.



Table 2. Continuous integration pipeline hosts

 Host Description 

 https://hooks.slack.com/services When the Slack integration is configured, notifications are sent when pipelines start and finish. 
 https://otc-github-consolidated-broker.<region>.devops.cloud.ibm.com/github/token?git_id=integrated The OTC broker URL to fetch a Git token if one was not provided.
Omission results in the default HTML error page. This field is valid only when mode is simulate or ban.

<-- <ul> -->

* content_type: The content-type of the body, which must be one of the following: text/plain, text/xml, application/json.
* body: The body to return. The content here must conform to the content_type. Max length is 10240.

<-- </ul> -->

<-- </ul> -->

<-- </ul> -->

* The optional fields are disabled, description, correlate and bypass:

<-- <ul> -->

* disabled: Whether this rate limiting rule is currently disabled.
* description: A note that you can use to describe the reason for a rate limiting rule.
* correlate: Whether to enable NAT based rate limiting.

<-- <ul> -->

* by: Valid values: nat.

<-- </ul> -->

* bypass: Criteria that allows the rate limit to be bypassed. For example, to express that you shouldn’t apply a rate limit to a given set of URLs.

<-- <ul> -->

* name: Valid values is url.
* value: The url to bypass.

<-- </ul> -->

<-- </ul> -->

<-- </ul> -->

Sample JSON data: {
"disabled": false,
"description": "Prevent multiple login failures to mitigate brute force attacks",
"bypass":
{
"name": "url",
"value": "api.example.com/"
}
],
"threshold": 60,
"period": 900,
"correlate": {
"by": "nat"
},
"action":
{
"mode": "simulate",
"timeout": 86400,
"response": {
Instead, Ansible securely connects to compute hosts over the public network by using SSH keys. To bring a resource to the required state, Ansible pushes modules to the managed host that run the tasks in your Ansible playbook. After the tasks are executed, the result is returned to the Ansible server and the module is removed from the managed host. Ansible modules are idempotent such that executing the same playbook or operation multiple times returns the same result as resources are changed only if required. For more information about Ansible, check out this [video](https://www.youtube.com/watch?v=fHO1X93e4WA).

Zoom

![Configuration Management with Actions and Ansible](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics//images/new/sc-actions.svg)

Configuration Management with Actions and Ansible

Using your supplied playbooks, Schematics runs the Ansible engine to execute your playbook. Ansible, tasks, roles and playbooks can perform provisioning tasks via the IBM Cloud APIs via HTTPS, or configuration of compute instances (virtual servers) using SSH. Server configuration is performed via SSH over the public network. To maintain security for your environment, use of a bastion host to provide a secure gateway to your compute infrastructure is strongly encouraged.

It is your responsibility as a user to ensure suitable network policies and bastion host configuration are in place for their cloud environment to allow Schematics to connect via SSH to your environment. See [Schematics firewall, allowed IPs](https://cloud.ibm.com/docs/schematics?topic=schematics-allowed-ipaddresses) for details of the IP addresses Schematics uses and must be allowed access. When using a bastion host, SSH forwarding is used to connect to the target VSIs. To validate access the command ssh -J bastion-ip vsi-ip. Actions has only been tested with IBM Cloud VPC VSIs.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) 
 Configure and remove notifications channels ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) 
 Configure and remove agents ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) 
 Create, delete, and edit content in the UI ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) 
 Manage runtime policies ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/checkmark-icon.svg) !
* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cm-8.1control-requirements)
* [IBM Cloud for Financial Services profile](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cm-8.1scc-fs-cloud-profile)



[CM-8 (2) - Automated Maintenance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cm-8.2cm-8.2)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cm-8.2control-requirements)
* [IBM Cloud for Financial Services profile](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cm-8.2scc-fs-cloud-profile)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cm-8.2nist-supplemental-guidance)



[CM-8 (3) - Automated Unauthorized Component Detection](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cm-8.3cm-8.3)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cm-8.3control-requirements)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cm-8.3nist-supplemental-guidance)
Custom model training data 

When you train a custom model, the training data that you use to create the model is stored to provide you with the custom model. Custom models and training data are encrypted in flight and at rest. The encrypted training data persists in storage until the model is deleted with the Delete model method.

Custom models can only be deleted at the model level. Component data used to create a custom model cannot be deleted. If you use personal data when creating a custom model, a separate custom model must be created for each customer and the model name labeled to identify the customer so it can be deleted if requested.
If this happens, the solution is to delete the job, after which the upgrade proceeds normally. Perform the following steps to resolve the problem.



1. To determine whether the MinIO backup job remains undeleted, issue the following command:

oc get job --namespace {${PROJECT_CPD_INSTANCE} | grep speech-cr-ibm-minio-backup

The MinIO job that is not deleted is identified by an entry of the following form:

speech-cr-ibm-minio-backup 1/1 3m25s 1d
2. To delete the MinIO backup job, issue the following command:

oc delete job speech-cr-ibm-minio-backup --namespace ${PROJECT_CPD_INSTANCE}



Once the backup job is deleted, upgrade continues and completes.

Defect fix: Update French Canadian next-generation telephony model (upgrade required)
: Defect fix: The French Canadian next-generation telephony model, fr-CA_Telephony, was updated to address an internal inconsistency that could cause an error during speech recognition. You need to upgrade any custom models that are based on the fr-CA_Telephony model. For more information about upgrading custom models, see



* [Upgrading custom models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-custom-upgrade)
* [Using upgraded custom models for speech recognition](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-custom-upgrade-use)



Defect fix: The next-generation Brazilian Portuguese multimedia model is now available
: Defect fix: The next-generation Brazilian Portuguese multimedia model is now available for Speech to Text for IBM Cloud Pak for Data. Previously, the model was unavailable.

Adding words directly to custom models that are based on next-generation models increases the training time
: Adding custom words directly to a custom model that is based on a next-generation model causes training of a model to take a few minutes longer than it otherwise would.
echo 'cp.icr.io,cp/watson-speech/en-gb-multimedia,2022-01-05-405models,sha256:167f9a76258530a56a6abdd1c311f2ea05d6820ee0e802fbf2f96f08fb8a7646,IMAGE,linux,x86_64,"",0,CASE,"",""' >> $CASE_PATH/ibm-watson-speech-4.0.5-images.csv



License Server is now automatically installed
: The Speech services operator now automatically installs the required License Server when it installs the Speech services. You no longer need to install the License Server from the IBM Cloud Pak for Data foundational services, and you no longer need to use additional YAML content to create an OperandRequest with the necessary bindings.

Removal of steps specific to PostgreSQL EnterpriseDB server
: The previous version of the documentation included steps for the PostgreSQL EnterpriseDB server that were specific to the Speech services. These steps were documented in the topics Upgrading Watson Speech to Text (Version 4.0) and Uninstalling Watson Speech to Text. These additional steps are no longer necessary and have been removed from the documentation.

RabbitMQ datastore is now used only by the sttAsync component
: The RabbitMQ datastore was previously used by components of both Speech services, Speech to Text and Text to Speech. It now handles non-persistent message queuing for the Speech to Text asynchronous HTTP component (sttAsync) only. It is used only if the sttAsync component is installed and enabled.

New next-generation models
: The service now supports the following next-generation models with Speech to Text for IBM Cloud Pak for Data:



* Chinese (Mandarin) telephony model (zh-CN_Telephony). The new model supports low latency.
* English (Australian) multimedia model (en-AU_Multimedia). The new model does not support low latency.
* English (UK) multimedia model (en-GB_Multimedia).
You again need the {environment_id} and {configuration_id} IDs you collected at the start of this procedure.

curl -X PUT -u "apikey":"{apikey_value}" -H "Content-Type: application/json" -d @my_config.json "{url}/v1/environments/{environment_id}/configurations/{configuration_id}?version=2019-04-30"

If you are creating a configuration or modifying the default configuration, create another custom configuration instead of updating an existing configuration. Before you create the configuration, remove the "configuration_id": field from your my_config.json file, and then run the following command:

curl -X POST -u "apikey":"{apikey_value}" -H "Content-Type: application/json" -d @my_config.json "{url}/v1/environments/{environment_id}/configurations?version=2019-04-30"

Both commands return the contents of the updated configuration file.

Replace {apikey} and {url} with your API key and URL.





 Integrating multiple custom models 

You can apply more than one custom model to identical fields using the API. Follow the steps in [Integrating your custom model with the API](https://cloud.ibm.com/docs/discovery?topic=discovery-integrating-with-wksintegrate-customAPI) and use the example here as a guide.

You cannot apply multiple custom models using the Discovery tooling. Only the entity and relations enrichments can be customized.

You must specify a different destination_field for each identical source_field. In addition, each source_field must be enriched by a unique model. For example, if you want to apply multiple custom models to the source_field of text and you apply the model{watson_knowledge_studio_model_ID} to the entities enrichment, you must not use that model again for the entities enrichment.

"enrichments": [
{
"source_field": "text",
"destination_field": "enriched_text",
echo 'cp.icr.io,cp/watson-speech/es-la-telephony,2022-01-05-405models,sha256:58e8c04abe9659472e89bf0778b7dc66e0ddceb4ea18d9d3e048a08c72125ea2,IMAGE,linux,x86_64,"",0,CASE,"",""' >> $CASE_PATH/ibm-watson-speech-4.0.5-images.csv
* For the Australian English multimedia model (en-AU_Multimedia):

echo 'cp.icr.io,cp/watson-speech/en-au-multimedia,2022-01-05-405models,sha256:167f9a76258530a56a6abdd1c311f2ea05d6820ee0e802fbf2f96f08fb8a7646,IMAGE,linux,x86_64,"",0,CASE,"",""' >> $CASE_PATH/ibm-watson-speech-4.0.5-images.csv
* For the UK English multimedia model (en-GB_Multimedia):

echo 'cp.icr.io,cp/watson-speech/en-gb-multimedia,2022-01-05-405models,sha256:167f9a76258530a56a6abdd1c311f2ea05d6820ee0e802fbf2f96f08fb8a7646,IMAGE,linux,x86_64,"",0,CASE,"",""' >> $CASE_PATH/ibm-watson-speech-4.0.5-images.csv



License Server is now automatically installed
: The Speech services operator now automatically installs the required License Server when it installs the Speech services. You no longer need to install the License Server from the IBM Cloud Pak for Data foundational services, and you no longer need to use additional YAML content to create an OperandRequest with the necessary bindings.
As with the initial deprecation notice, the Arabic and Japanese previous-generation models are not deprecated. For complete list of all deprecated models, see the [15 March 2022 (Version 4.0.6) service update](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-release-notes-dataspeech-to-text-data-15march2022).

On 3 March 2023, the deprecated models will be removed from the service and the documentation. If you use any of the deprecated models, you must migrate to the equivalent next-generation model by the 3 March 2023.



* For more information about the next-generation models to which you can migrate from each of the deprecated models, see [Previous-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models)
* For more information about the next-generation models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng)
* For more information about migrating from previous-generation to next-generation models, see [Migrating to next-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-migrate).



Note: When the previous-generation en-US_BroadbandModel is removed from service, the next-generation en-US_Multimedia model will become the default model for speech recognition requests.





 3 August 2022 (Version 4.5.1) 

Version 4.5.1 is now available
: Speech to Text for IBM Cloud Pak for Data version 4.5.1 is now available. This version supports IBM Cloud Pak for Data version 4.5.x and Red Hat OpenShift versions 4.6, 4.8, and 4.10.
speech-to-text.custom-language-model-grammar-list.read Read a grammar list of a custom language model (GET /v1/customizations/{customization_id}/grammars). 
 speech-to-text.custom-language-model-grammar.read Read a grammar of a custom language model (GET /v1/customizations/{customization_id}/grammars/{grammar_name}). 







 Delete events 



Table 3. Language model customization .delete actions that generate events

 Action Description 

 speech-to-text.custom-language-model.delete Delete a custom language model (DELETE /v1/customizations/{customization_id}). 
 speech-to-text.custom-language-model-word.delete Delete a word from a custom language model (DELETE /v1/customizations/{customization_id}/words/{word_name}). 
 speech-to-text.custom-language-model-corpus.delete Delete a corpus from a custom language model (DELETE /v1/customizations/{customization_id}/corpora/{corpus_name}). 
 speech-to-text.custom-language-model-grammar.delete Delete a grammar from a custom language model (DELETE /v1/customizations/{customization_id}/grammars/{grammar_name}). 







 Train event 



Table 4. Language model customization .train action that generates an event

 Action Description 

 speech-to-text.custom-language-model.train Train a custom language model (POST /v1/customizations/{customization_id}/train). 







 Reset event 



Table 5. Language model customization .reset action that generates an event

 Action Description 

 speech-to-text.custom-language-model.reset Reset a custom language model (POST /v1/customizations/{customization_id}/reset). 







 Upgrade event 



Table 6. Language model customization .upgrade action that generates an event

 Action Description
Verify the token authentication function.

First, access the contents without the token.

curl -i "http://www.cdn-domain.com/private/test.txt"
HTTP/1.1 403 Forbidden
...

<HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD><BODY>
<H1>Access Denied</H1>

You don't have permission to access "http://www.cdn-domain.com/private/test.txt" on this server.
Reference 18.ef3ce17.1598346101.6c7c336e
</BODY>
</HTML>

Without the token, the Edge server returns a 403 response code that indicates the user has no permission to access the content.

Next, pass the token in a cookie and make the request again.

curl -i "http://www.cdn-domain.com/private/test.txt" --cookie "__token__=exp=1598348288acl=/private/hmac=73cbcba0137b4875b10a3264d4c24189a91825e51f2764af0891a854d015dd08"
HTTP/1.1 200 OK
...

200 response code is returned and the content is successfully returned by the CDN Edge server.
FJInGKFJpEcwRTELMAkGA1UEBhMCQVUxEzARBgNVBAgTClNvbWUtU3RhdGUxITAfBgNVnBAoTGEludGVybmV0IFdpZGdpdHMgUHR5IEx0ZIIJAMHAwfXZ5/PWMAwGA1UdEwQFnMAMBAf8wDQYJKoZIhvcNAQELBQADggEBAHHFwl0tH0quUYZYO0dZYt4R7SJ0pCm2n2satiyzHl4OnXcHDpekAo7/a09c6Lz6AU83cKy/+x3/djYHXWba7HpEu0dR3ugQPnMlr4zrhd9xKZ0KZKiYmtJH+ak4OM4L3FbT0owUZPyjLSlhMtJVcoRp5CJsjAMBUGnSvD8RX+T01wzox/Qb+lnnNnOlaWpqu8eoOenybxKp1a9ULzIVvN/LAcc+14vioFqn2swRWtmocBAs8QR9n4uvbpiYvS8eYueDCWMM4fvFfBhaDZ3N9IbtySh3SpFdQDhwnYbjM2rxXiyLGxB4Bol7QTv4zHif7Zt89FReT/NBy4rzaskDJY5L6xmY=n-----END CERTIFICATE-----n", "private_key": "-----BEGIN RSA PRIVATE KEY-----nMIIEowIBAAKCAQEAwQHoetcl9+5ikGzV6cMzWtWPJHqXT3wpbEkRU9Yz7lgvddmGndtcGbg/1CGZu0jJGkMoppoUo4c3dts3iwqRYmBikUP77wwY2QGmDZw2FvkJCJlKnnabIRuGvBKwzESIXgKk2016aTP6/dAjEHyo6SeoK8lkIySUvK0fyOVlsiEsCmOpidntnKX/a+50GjB79CJH4ER2lLVZnhePFR/zUOyPxZQQ4naHf7yu
5BRb6FJInGKFJpEcwRTELMAkGA1UEBhMCQVUxEzARBgNVBAgTClNvbWUtU3RhdGUxITAfBgNVnBAoTGEludGVybmV0IFdpZGdpdHMgUHR5IEx0ZIIJAMHAwfXZ5/PWMAwGA1UdEwQFnMAMBAf8wDQYJKoZIhvcNAQELBQADggEBAHHFwl0tH0quUYZYO0dZYt4R7SJ0pCm2n2satiyzHl4OnXcHDpekAo7/a09c6Lz6AU83cKy/+x3/djYHXWba7HpEu0dR3ugQPnMlr4zrhd9xKZ0KZKiYmtJH+ak4OM4L3FbT0owUZPyjLSlhMtJVcoRp5CJsjAMBUGnSvD8RX+T01wzox/Qb+lnnNnOlaWpqu8eoOenybxKp1a9ULzIVvN/LAcc+14vioFqn2swRWtmocBAs8QR9n4uvbpiYvS8eYueDCWMM4fvFfBhaDZ3N9IbtySh3SpFdQDhwnYbjM2rxXiyLGxB4Bol7QTv4zHif7Zt89FReT/NBy4rzaskDJY5L6xmY=n-----END CERTIFICATE-----n", "private_key": "-----BEGIN RSA PRIVATE KEY-----nMIIEowIBAAKCAQEAwQHoetcl9+5ikGzV6cMzWtWPJHqXT3wpbEkRU9Yz7lgvddmGndtcGbg/1CGZu0jJGkMoppoUo4c3dts3iwqRYmBikUP77wwY2QGmDZw2FvkJCJlKnnabIRuGvBKwzESIXgKk2016aTP6/dAjEHyo6SeoK8lkIySUvK0fyOVlsiEsCmOpidntnKX/a+50GjB79CJH4ER2lLVZnhePFR/zUOyPxZQQ4naHf7yu/b5
IEx0ZIIJAMHAwfXZ5/PWMAwGA1UdEwQFnMAMBAf8wDQYJKoZIhvcNAQELBQADggEBAHHFwl0tH0quUYZYO0dZYt4R7SJ0pCm2n2satiyzHl4OnXcHDpekAo7/a09c6Lz6AU83cKy/+x3/djYHXWba7HpEu0dR3ugQPnMlr4zrhd9xKZ0KZKiYmtJH+ak4OM4L3FbT0owUZPyjLSlhMtJVcoRp5CJsjAMBUGnSvD8RX+T01wzox/Qb+lnnNnOlaWpqu8eoOenybxKp1a9ULzIVvN/LAcc+14vioFqn2swRWtmocBAs8QR9n4uvbpiYvS8eYueDCWMM4fvFfBhaDZ3N9IbtySh3SpFdQDhwnYbjM2rxXiyLGxB4Bol7QTv4zHif7Zt89FReT/NBy4rzaskDJY5L6xmY=n-----END CERTIFICATE-----n", "private_key": "-----BEGIN RSA PRIVATE KEY-----nMIIEowIBAAKCAQEAwQHoetcl9+5ikGzV6cMzWtWPJHqXT3wpbEkRU9Yz7lgvddmGndtcGbg/1CGZu0jJGkMoppoUo4c3dts3iwqRYmBikUP77wwY2QGmDZw2FvkJCJlKnnabIRuGvBKwzESIXgKk2016aTP6/dAjEHyo6SeoK8lkIySUvK0fyOVlsiEsCmOpidntnKX/a+50GjB79CJH4ER2lLVZnhePFR/zUOyPxZQQ4naHf7yu/b5jhO0f8fwt+pynFxIXjbEIdZliWRkRMtzrHOJIhrmJ
* Recommend to enable the SSH Host key checking or specify the StrictHostKeyChecking = yes in the ssh_config file for additional security to allow only verified known hosts to connect to the instance.







 App Orchestration 

IBM's responsibilities:



* None.



Your responsibilities:



* Use the tools and features that are provided to:



* Configure and deploy setup permissions.
* Integrate with other services.
* Externally serve, monitor the health, save, back up, and restore data.
* Manage your highly available and resilient workloads.



* Design and deploy your workload in a way that achieves high availability by using multiple data centers.







 Connecting clients 

IBM's responsibilities:



* None.



Your responsibilities:



* Make sure that the clients, which can connect to the virtual server instances are maintained and securely configured. Also, don't share private keys to authenticate to any virtual server.









 Abuse of IBM Cloud® Virtual Private Cloud 

Clients must not misuse IBM Cloud® Infrastructure.

Misuse includes:



* Any illegal activity
* Distribution or execution of malware
* Harming IBM Cloud Infrastructure or interfering with the use of IBM Cloud Infrastructure
* Harming or interfering with the use of any other service or system
* Unauthorized access to any service or system
* Unauthorized modification of any service or system
* Violation of the personal rights of others



See [Cloud Services terms](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms) for overall terms of use.
"WAFAction":"unknown",
"WAFFlags":"0",
"WAFMatchedVar":"",
"WAFProfile":"unknown",
"WAFRuleID":"",
"WAFRuleMessage":"",
"WorkerCPUTime":0,
"WorkerStatus":"unknown",
"WorkerSubrequest":false,
"WorkerSubrequestCount":0,
"ZoneID":
}
Show more
* Request matched a WAF rule (SQLj attack)

{
"CacheCacheStatus":"unknown",
"CacheResponseBytes":0,
"CacheResponseStatus":0,
"CacheTieredFill":false,
"ClientASN":56046,
"ClientCountry":"cn",
"ClientDeviceType":"desktop",
"ClientIP":"1.1.1.1",
"ClientIPClass":"noRecord",
"ClientRequestBytes":501,
"ClientRequestHost":"foo.com",
"ClientRequestMethod":"GET",
"ClientRequestPath":"/login.php",
"ClientRequestProtocol":"HTTP/1.1",
"ClientRequestReferer":"",
"ClientRequestURI":"/login.php?username=asdf&password=asdf",
"ClientRequestUserAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Firefox/60.0",
"ClientSSLCipher":"NONE",
"ClientSSLProtocol":"none",
"ClientSrcPort":48718,
"EdgeColoID":134,