Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Re-mapped /prometheus/<end-point> to /victoriametrics/<end-point> but created aliases for users that still rely on the /prometheus/<end-point> in bookmarks and scripts

Description

The problem:

PMM users and support team who used to use /prometheus/ for troubleshooting are not aware of VM URLs if they'll go to the usual URL 

Proposed solution:

some simple "landing page" to explain what is available in VM and let the user go to listed URL's  

Reuse the content of https://www.percona.com/doc/percona-monitoring-and-management/2.x/details/victoria-metrics.html#remapped-targets-for-direct-prometheus-paths  but as working links according to current URL. Make links "no change" also working.  

Acceptance Criteria:

  • Target links should be clickable 

  • /victoriametrics is an alias to /prometheus, but some routes are not remapped (/alerts, /rules)

UI:

HTML with working links to important sections 

Out of scope:

  • the logic/content under every link

 

 

 

Original report:

After upgrading from 2.11.0 to 2.12.0 access to http://<pmm-ip>/prometheus is not working

How to test

None

How to document

None

Attachments

3

Smart Checklist

Activity

Jira Bot December 23, 2020 at 8:56 AM

To: Former user
CC:

Hi, I'm jira-bot, Percona's Jira automation tool. I've detected that someone from
Percona has made an edit to the Summary field of an issue that you reported.

I'm not sentient (yet) so I'm not sure whether the person fixed a typo, changed
a few words, or completely rewrote the text. In any case, it is Percona Engineering's
intention to make the Summary and Description of an issue as accurate as possible
so that we're fixing the actual problem you're encountering, and to avoid
misunderstandings about symptoms and causes.

If the current Summary does not accurately reflect the problem you are reporting,
or if you feel the change was otherwise inappropriate in some way, please add a
new comment explaining things and we'll address it as soon as we can.

This message will be added only once per issue, regardless of how many times
the Summary is edited.

message-code:summary-edited

Nailya Kutlubaeva December 21, 2020 at 10:03 AM

Everything looks ok, I've found the only few issues, they are not critical:
1. Add more spacing between lines on prometheus main page
2. Change “PMM grafana dashboard” to “PMM Grafana dashboard to explore all metrics” or something like that
3. Endpoint’s URL is a very long


4. Scrape duration is always=0.000s

Roma Novikov December 2, 2020 at 10:11 PM

 , I've Converted  this is to Improvement and we'll update doc  soon 

Puneet Kala December 2, 2020 at 6:32 PM
Edited

Targets should be available at /prometheus/targets end point, 

rules should be available at /prometheus/rules 

Alert triggered should be available at /prometheus/alerts

All should have text output without UI at this moment 

 

Daniel Guzman Burgos December 2, 2020 at 5:33 PM

Since VM doesn't have such page (https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4) how one can check things like Targets status and rules ?

Done

Details

Assignee

Reporter

Priority

Components

Labels

Needs QA

Yes

Fix versions

Story Points

Sprint

Affects versions

Smart Checklist

Created December 2, 2020 at 5:30 PM
Updated March 6, 2024 at 3:33 AM
Resolved December 29, 2020 at 10:12 PM