| Description | This article describes the Attribute key-value pairs, where attributes can be used and some example use cases. |
| Scope | FortiMonitor. |
| Solution |
Overview
Attributes are values associated with instances that can be leveraged to filter results when needed. While Attributes are similar to Tags there are some key differences. Tags are standalone values while Attributes consist of a key-value pair that provides additional context for the stored value. Each attribute key can also have multiple associated values. For example, a Tag value could be 'Windows' while an Attribute key-value pair must consist of the key and at least one paired value example a key of 'Operating System' and the value 'Windows' as well as the value 'Linux'. Thus allowing to filter for results where the Attribute key of 'Operating System' has a value of 'Windows'.
Use Cases
Attributes can be leveraged for the following tasks:
1) Monitoring Policy Framework automation. 2) Dashboard level scope filtering. 3) Filtering Instance Group instance results. 4) Filtering Incident Hub incident results.
Creation
Attributes can be created from the Instance Details page. Attributes can also be included as part of a manifest file during agent installation. The Monitoring Policy Framework can also be leveraged to assign and utilize Attributes. Lastly, Attributes can also be automatically created for AWS or Azure cloud integrations. The cloud integration setup has the option to import AWS or Azure tags as FortiMonitor tags storing only the value portion or the key-value pair as a single string or import them as a Attribute key-value pair.
Examples
Below are some example use cases for Attributes:
1) Environment. - Dev. - Stage. - Prod.
2) Operating System. - Windows Server 2019. - Windows Server 2022. - Ubuntu 22.04 LTS. - Ubuntu 20.04 LTS. - Ubuntu 18.04.6 LTS.
3) Location. - Indianapolis. - Chicago. - Columbus. - AWS. - Azure.
4) Status. - Primary. - Backup. - Standby. |
