minor changes
parent
1339aa41e3
commit
bf9d9ee96b
|
|
@ -1,54 +0,0 @@
|
||||||
### Provider Breakdown Configuration
|
|
||||||
|
|
||||||
- Dynatrace automatically recognizes more than 1,000 3rd-party content providers, including Google, Amazon, Twitter, and LinkedIn.
|
|
||||||
Typical 3rd-party content includes Facebook and Twitter widgets, gravatars, and similar resources.
|
|
||||||
It's worth monitoring this type of content to know exactly how it affects your applications and to understand if such content is the root cause of any page slow-downs.
|
|
||||||
- This extesions allows you to set up rules that define how your applications' downloaded content resources (images, CSS, 3rd party widgets, and more) are displayed
|
|
||||||
and categorized for analysis.
|
|
||||||
- This extension allows you to keep the configuration consistent accross all tenants
|
|
||||||
|
|
||||||
#### Download configuration
|
|
||||||
|
|
||||||
1. Configure *config.ini* file:
|
|
||||||
```
|
|
||||||
downloadConfig = 1
|
|
||||||
updateConfig = 0
|
|
||||||
```
|
|
||||||
2. Run the script:
|
|
||||||
```
|
|
||||||
python providerBreakdown.py
|
|
||||||
```
|
|
||||||
3. The configuration will appear under */data/<tenant>/contentResources/contentResources.json*
|
|
||||||
|
|
||||||
|
|
||||||
#### Create configuration
|
|
||||||
|
|
||||||
*Use case: A team wants to create a new provider breakdown rule*
|
|
||||||
|
|
||||||
1. Configure *config.ini* file:
|
|
||||||
```
|
|
||||||
downloadConfig = 0
|
|
||||||
updateConfig = 1
|
|
||||||
```
|
|
||||||
2. Edit the file */data/<tenant>/contentResources/contentResources.json* adding the desired rule. For example:
|
|
||||||
```
|
|
||||||
{
|
|
||||||
"resourceName": "OneLogin (Prod)",
|
|
||||||
"resourceType": "FIRST_PARTY_RESOURCES",
|
|
||||||
"brandIconUrl": "https://empty",
|
|
||||||
"domainNamePatterns": [
|
|
||||||
"customer.bmwgroup.com"
|
|
||||||
]
|
|
||||||
}
|
|
||||||
```
|
|
||||||
3. Run the script:
|
|
||||||
```
|
|
||||||
python providerBreakdown.py
|
|
||||||
```
|
|
||||||
|
|
||||||
#### Delete configuration
|
|
||||||
|
|
||||||
1. Same process as before:
|
|
||||||
- access the JSON
|
|
||||||
- delete the target rule
|
|
||||||
- run the update
|
|
||||||
Loading…
Reference in New Issue