question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Provide capability to use multiple metric dimensions

See original GitHub issue

Proposal

Provide capability to use multiple metric dimensions instead of just one.

Our current metric declaration looks as following:

- name: azure_service_bus_active_messages
    description: "The number of active messages on a service bus queue."
    resourceType: ServiceBusNamespace
    labels:
      app: promitor
      tier: messaging
    scraping:
      # Every 2 minutes
      schedule: "0 */2 * ? * *"
    azureMetricConfiguration:
      metricName: ActiveMessages
      limit: 5
      dimension:
        name: <dimension-name>
      aggregation:
        type: Total
        interval: 00:15:00
    resources: # Optional, required when no resource discovery is configured
      - namespace: promitor-messaging
        queueName: orders

This will change to:

- name: azure_service_bus_active_messages
    description: "The number of active messages on a service bus queue."
    resourceType: ServiceBusNamespace
    labels:
      app: promitor
      tier: messaging
    scraping:
      # Every 2 minutes
      schedule: "0 */2 * ? * *"
    azureMetricConfiguration:
      metricName: ActiveMessages
      limit: 5
      dimension: # Deprecated, use dimensions instead
        name: <dimension-name>
+     dimensions:
+     - name: <dimension-name-1>
+     - name: <dimension-name-2>
      aggregation:
        type: Total
        interval: 00:15:00
    resources: # Optional, required when no resource discovery is configured
      - namespace: promitor-messaging
        queueName: orders

Relates to #809

Component

Scraper

Contact Details

No response

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:9 (7 by maintainers)

github_iconTop GitHub Comments

4reactions
tomkerkhovecommented, Oct 23, 2021

@locmai volunteered to contribute this, thank you! I have added the config spec above

0reactions
tomkerkhovecommented, Aug 6, 2022

Thanks a ton! I’m currently working to get OTEL closed first so appreciate the help!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Monitor multiple time series in a single metric alert rule
A single metric alert rule can be used to monitor one or many metric time series. This capability makes it easier to monitor...
Read more >
Multi-dimensional analysis views for service metrics and ...
Dynatrace enables you to leverage data captured via request attributes to build your own custom multi-dimensional analysis charts.
Read more >
Target tracking scaling policies for Amazon EC2 Auto Scaling
To help optimize scaling performance, you can use multiple target tracking scaling policies together, provided that each of them uses a different metric....
Read more >
[GA4] Custom dimensions and metrics - Analytics Help
Create dimensions and metrics from event parameters and user properties so you can easily access data in reports and explorationsCustom dimensions and.
Read more >
Logs-to-Metrics
Set up rules to extract or create metrics from log data.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found