...
| Panel |
|---|
| borderColor | white |
|---|
| borderWidth | 50 |
|---|
| borderStyle | none |
|---|
|
| Code Block |
|---|
| aaf_username: dcae@dcae.onap.org
aaf_password: <dcae_password> |
|
...
By default, the PM-Mapper will only allow inbound queries over HTTPS, however its possible to configure it to enable HTTP also. This configuration can look like:
| Panel |
|---|
| borderColor | white |
|---|
| borderWidth | 50 |
|---|
| borderStyle | none100 |
|---|
|
| Code Block |
|---|
| enable_http: true |
|
...
By default the latest Docker Images will be used when deploying the PM-Mapper, however, this attribute can also be configured like:
| Panel |
|---|
| borderColor | white |
|---|
| borderWidth | 50 |
|---|
| borderStyle | none100 |
|---|
|
| Code Block |
|---|
| tag_version: nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pm-mapper:<version> |
|
...
The default behavior of the PM-Mapper is to map all measType in the received PM XML files, however, it's possible to provide filtering configuration which will reduce the VES event to the counters that the designer has expressed interest in. An example of this configuration:
| Panel |
|---|
| borderColor | white |
|---|
| borderWidth | 50 |
|---|
| borderStyle | 100none |
|---|
|
| Code Block |
|---|
| pm-mapper-filter: {"filters":[{"pmDefVsn":"targetVersion","nfType":"targetNodeType","vendor":"targetVendor","measTypes":["targetMeasType"]}]} |
|
...
