Removes the go-neb Matrix integration as it's discontinued.
Keeps only the two actively maintained Matrix integrations:
- matrix-alertmanager
- matrix-hookshot
Addresses final review comment on PR #2809.
Signed-off-by: Sibasis Padhi <sibasis.padhi@gmail.com>
Removes the PowerDNS exporter link entirely as the project
has not been updated in 11 years and no actively maintained
alternative is available.
Addresses review feedback on PR #2805.
Signed-off-by: Sibasis Padhi <sibasis.padhi@gmail.com>
Improves the download instructions by:
- Explaining the URL pattern with all placeholders clearly defined
- Listing what <VERSION>, <OS>, and <ARCH> mean with examples
- Using concrete example values (v1.10.2, linux-amd64) in commands
- Making it easier for new users to understand what to replace
Addresses review feedback on PR #2810.
Signed-off-by: Sibasis Padhi <sibasis.padhi@gmail.com>
Add warning blocks to console documentation explaining that console
templates and libraries are no longer bundled with Prometheus 3.0 and
must be provided by users via command-line flags. Update GitHub links
to reference release-2.55 branch instead of main, noting that 2.x
console libraries are unmaintained and contain known CVEs
Signed-off-by: Julien Pivotto <291750+roidelapluie@users.noreply.github.com>
Fixes #1896
Clarified download instructions for Node Exporter to help users:
- Select the appropriate bundle for their OS and architecture
- Added note about platform-specific downloads (linux-amd64, darwin-arm64, etc.)
- Made tar command more specific to match downloaded file pattern
- Improved clarity for new users
Signed-off-by: Sibasis Padhi <sibasis.padhi@gmail.com>
Fixes #2366
Replaced the link to go-neb (which has been discontinued) with
matrix-hookshot, the spiritual successor recommended in the
go-neb repository for Matrix notifications.
Signed-off-by: Sibasis Padhi <sibasis.padhi@gmail.com>
Fixes #1806
Added definition for 'mixin' to the glossary, explaining it as
a reusable set of Prometheus alerts, recording rules, and Grafana
dashboards typically packaged using Jsonnet for standardized
monitoring across infrastructure components.
Signed-off-by: Sibasis Padhi <sibasis.padhi@gmail.com>
Fixes #2222
The previous link to ledgr/powerdns_exporter returns 404.
Updated to janeczku/powerdns_exporter which is actively
maintained and the most popular PowerDNS exporter fork.
Signed-off-by: Sibasis Padhi <sibasis.padhi@gmail.com>
* Blog post about new relabeling visualizer in Prometheus 3.8.0
Signed-off-by: Julius Volz <julius.volz@gmail.com>
* Reword introduction section
Signed-off-by: Julius Volz <julius.volz@gmail.com>
* Allow screenshots + videos to be slightly taller
Signed-off-by: Julius Volz <julius.volz@gmail.com>
---------
Signed-off-by: Julius Volz <julius.volz@gmail.com>
When following a link to a fragment (#foo) on a long documentation page,
the browser would try to scroll to the fragment too early, before some
additional client-side layout shifts (could be due to font loading,
highlighting, etc.) would cause the scroll position to be wrong again. This
component waits for the layout to settle and then manually scrolls to the
requested fragment again.
You can see the problem by clicking on:
https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config
It usually does not scroll directly to the relabeling section, but
somewhere above it.
Signed-off-by: Julius Volz <julius.volz@gmail.com>
Make the exemplar timestamp a SHOULD in preparation for complex types
having multiple exemplars at a time. We'll explain why having timestamp
for exemplars of complex types is a good idea there.
Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
I noticed that the hyperlink to the blog content guide was leading to a 404 error on the live site, even though it worked correctly on GitHub. I think the issue was caused by using a relative link. I’ve updated the link to use an absolute URL so it resolves properly in the published blog.
Signed-off-by: Victoria Nduka <122698422+nwanduka@users.noreply.github.com>
* prw2(breaking): Move 2.0 CT to Sample; Rename to ST (Start Timestamp)
Given the recent movement for Prometheus native support of ST
([PROM-60](https://github.com/prometheus/proposals/pull/60)) and plans
for delta temporality
([PROM-48](https://github.com/prometheus/proposals/pull/48)) it might be
beneficial to make (hopefully) last change to Remote Write 2.0 before
stabilizing, so:
* Raname Created Timestamp to Start Timestamp
* Move CT/ST from TimeSeries to Sample and Histogram messages.
* Clarified optionality (0 value meaning unset)
See implementation change that will follow:
https://github.com/prometheus/prometheus/pull/17411. Notice that only
receiver part was implemented for CT/ST. Given no sending part was done
we expect this feature (ST/CT) not being used, thus breakage impact is
minimal. This has been confirmed with early adopters like Mimir
(Grafana), Chronosphere, Thanos, Cortex and Google.
See previous discussions and 3 expilcit approvals:
https://github.com/prometheus/prometheus/pull/17036
Additionally:
* I updated link to proto
* Updated links to new compliance tests
* Update native histogram spec link
Signed-off-by: bwplotka <bwplotka@gmail.com>
* Update docs/specs/prw/remote_write_spec_2_0.md
Co-authored-by: George Krajcsovits <krajorama@users.noreply.github.com>
Signed-off-by: Bartlomiej Plotka <bwplotka@gmail.com>
* Update docs/specs/prw/remote_write_spec_2_0.md
Signed-off-by: Bartlomiej Plotka <bwplotka@gmail.com>
---------
Signed-off-by: bwplotka <bwplotka@gmail.com>
Signed-off-by: Bartlomiej Plotka <bwplotka@gmail.com>
Co-authored-by: George Krajcsovits <krajorama@users.noreply.github.com>
