splunk-observability-metrics-pipeline-setup

To plan Splunk Observability Cloud Metrics Pipeline Management workflows, you provide inputs like realm, metric, action, and dimensions to generate a plan, intent JSON, and a deep-native-workflow spec for rendering and validation.

Metrics cardinality control in Splunk Observability Cloud governs metric usage and routing by applying actions like aggregate, drop, route, or archive to manage high-cardinality data effectively within your pipeline.

To validate a Metrics Pipeline Management plan before deployment, you render the downstream deep-native-workflow specs and intent files generated by the planning process using companion skills to ensure accuracy.

Yes, you can use this to route and aggregate metrics by specific dimensions by defining your desired action types and dimension handling rules within the generated intent JSON and deep-native-workflow spec.

Generating a Metrics Pipeline Management intent requires inputs including your realm, target metric, desired action such as aggregate or drop, and the specific metric dimensions you need to govern.

Yes, Splunk Observability Metrics Pipeline setup supports archiving metrics by allowing you to specify archive as your action type within the intent generation to route metric data accordingly.