Accountable Cloud Solutions

Support & FAQs

Quick answers to common questions about setup, data collection, and publishing.

You can setup publishing by adding REG_SZ settings under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\lmmahafalaedbemifckcmhdbpdplbnil\policy.

Typically, rather than editing the settings in the registry directly, customers use a Mobile Device Management (MDM) solution like MIcrosoft Intune to push extension configurations out to multiple workstations.

The settings that can be set are as follows:

  • settings_publish_url (required, this is the URL that the http POST to publish metrics will be sent to)
  • settings_license (required, you request a license here, then simply paste the contents of the license file into this setting)
  • settings_publish_format (optional, set to SPLUNK if using splunk)
  • settings_publish_stream_name (optional, set to your stream if using splunk)
  • settings_splunk_hec_token (optional, set to your HEC token if using splunk)
  • settings_publish_http_headers (optional, set to JSON array of headers you want to add)
  • settings_tenant_id (optional, if you have concept of a tenants in your org, set this to a tenant name)
  • settings_client_id (optional, if you want to identify the device by a particular name, add a value for this setting)

You can setup publishing by adding REG_SZ settings under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdParty\extensions\kdpaicmgckdkaemgalalcmijdacanoad\policy.

Typically, rather than editing the settings in the registry directly, customers use a Mobile Device Management (MDM) solution like MIcrosoft Intune to push extension configurations out to multiple workstations.

The settings that can be set are as follows:

  • settings_publish_url (required, this is the URL that the http POST to publish metrics will be sent to)
  • settings_license (required, you request a license here, then simply paste the contents of the license file into this setting)
  • settings_publish_format (optional, set to SPLUNK if using splunk)
  • settings_publish_stream_name (optional, set to your stream if using splunk)
  • settings_splunk_hec_token (optional, set to your HEC token if using splunk)
  • settings_publish_http_headers (optional, set to JSON array of headers you want to add)
  • settings_tenant_id (optional, if you have concept of a tenants in your org, set this to a tenant name)
  • settings_client_id (optional, if you want to identify the device by a particular name, add a value for this setting)
That’s the beauty of the extension — it only publishes a small payload of metrics once a day. The payload is intentionally small because, in the real world, daily granularity is plenty to know if performance is getting worse.

Settings for the extension is stored under the ~/Library/Application Support/Google/Chrome/Default/Local Extension Settings/lmmahafalaedbemifckcmhdbpdplbnil folder.

Typically, rather than editing the settings directly, customers use a Mobile Device Management (MDM) solution like MIcrosoft Intune to push extension configurations out to multiple workstations.

The settings that can be set are as follows:

  • settings_publish_url (required, this is the URL that the http POST to publish metrics will be sent to)
  • settings_license (required, you request a license here, then simply paste the contents of the license file into this setting)
  • settings_publish_format (optional, set to SPLUNK if using splunk)
  • settings_publish_stream_name (optional, set to your stream if using splunk)
  • settings_splunk_hec_token (optional, set to your HEC token if using splunk)
  • settings_publish_http_headers (optional, set to JSON array of headers you want to add)
  • settings_tenant_id (optional, if you have concept of a tenants in your org, set this to a tenant name)
  • settings_client_id (optional, if you want to identify the device by a particular name, add a value for this setting)
Yes! Simply set up a Splunk HTTP Event Collector (HEC) and configure:
  • settings_publish_format to SPLUNK
  • settings_publish_url to your HEC endpoint
  • settings_splunk_hec_token to the token generated by Splunk
You can do all of this using an Edge/Chrome managed policy for the extension and the data will start flowing to Splunk daily! If you need to set the index name from the extension, set the settings_publish_stream_name setting in that same policy.
As long as your metric collection system can accept HTTP POSTs, the answer is yes! If you need specific headers included with each request, set settings_publish_http_headers to JSON containing the headers to include.
{
  "X-Api-Key": "YOUR_KEY",
  "X-Org": "YourCompany"
}
Give it some time! The extension quietly works in the background to collect web application response times and there really isn’t much to show initially.
Remember! The real power of analytics is understanding what performance used to be and what it is now!