This article applies to:
• Data Ingestion
• Product edition: All
• Feature Category: Integrations, Kubernetes
Overview:
When ingesting Kubernetes data through your Kubernetes Integration configuration, AWS information is not automatically included. You can add tags in the Aria Operations for Application Custom Resource configuration from our Kubernetes Operator to provide key value pair tags that can be added to all the metrics emitted.
Common Properties:
Prefix, Tags, and Filters All sources and sinks support the Common Properties:
Here is an example of a wavefront.yaml config that sets custom AWS Account Name, Account ID and Region tags: (awsAccountName, awsAccountId, awsRegion)
# Need to change YOUR_CLUSTER_NAME and YOUR_WAVEFRONT_URL accordingly
apiVersion: wavefront.com/v1alpha1
kind: Wavefront
metadata:
name: wavefront
namespace: observability-system
spec:
clusterName: YOUR_CLUSTER_NAME
wavefrontUrl: YOUR_WAVEFRONT_URL
dataCollection:
metrics:
enable: true
# Can be any key value pair that users can add to all metrics emitted.
tags:
userDefinedTag: userDefinedValue
# aws example scenario
awsRegion: us-west-2
awsAccountName: AWS_ACCOUNT_NAME
awsAccountId: AWS_ACCOUNT_ID
dataExport:
wavefrontProxy:
enable: true
Note: VMware does not provide, update, or maintain scripts, and as such no support is provided for such purposes, even if said script was received and or provided by VMware. VMware does not recommend nor suggest running any untested script in production and always recommends testing of any scripts or automation in test environments before using on production environments.
See also:
Aria Operations for Application Custom Resource
Common Properties
Comments