Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more useful data into rabbitmq_cluster_vhost_status metric #10660

Closed
jonsbun opened this issue Mar 4, 2024 · 0 comments · May be fixed by #10670
Closed

Add more useful data into rabbitmq_cluster_vhost_status metric #10660

jonsbun opened this issue Mar 4, 2024 · 0 comments · May be fixed by #10670

Comments

@jonsbun
Copy link

jonsbun commented Mar 4, 2024

Is your feature request related to a problem? Please describe.

When a new virtual host is being created, a user can provide not only name, but also description and tags. Description and tags later are not visible in the GUI, but can be retrieved via /api/definitions/{vhost} API endpoint:

    "name": "test",
    "description": "testDescription",
    "tags": [
        "testTags"
    ],
    "default_queue_type": "quorum",
    "metadata": {
        "description": "testDescription",
        "tags": [
            "testTags"
        ],
        "default_queue_type": "quorum"
    },
    "tracing": false,
    "cluster_state": {
        "rabbit@server.local": "running"
    }
}

However, the same data is not available using RabbitMQ monitoring tools like Prometheus. This limitation allows filtering only by vhost name. Sometimes that is a big disadvantageous when creating Prometheus alerting rules because filtering is only available by vhost name and can't be achieved by vhost tags or description.

Describe the solution you'd like

Get RabbitMQ virtual host tags and description data when querying rabbitmq_cluster_vhost_status metric via Prometheus.

Describe alternatives you've considered

No response

Additional context

No response

@rabbitmq rabbitmq locked and limited conversation to collaborators Mar 5, 2024
@michaelklishin michaelklishin converted this issue into discussion #10678 Mar 5, 2024
@rabbitmq rabbitmq deleted a comment from jonsbun Mar 5, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant