Conversation
abravosuse
left a comment
abravosuse
left a comment
There was a problem hiding this comment.
Awesome job, @balanza . Just a couple of clarification requests and one note-to-self.
abravosuse
left a comment
abravosuse
left a comment
There was a problem hiding this comment.
Thank you @balanza . A few change requests (related to the fact that basic is now the default authentication method) and a couple of questions/suggestions.
| == {prometheus} integration | ||
|
|
||
| {prometheus} Server is a {trserver} component responsible for retrieving the memory and CPU utilization metrics collected by the `node-exporter` in the agent hosts and serving them to the web component. The web component renders the metrics as dynamic graphical charts in the details view of the registered hosts. | ||
| {prometheus} Server is a {trserver} component responsible for retrieving the memory and CPU utilization metrics from the agent hosts and serving them to the web component. The web component renders the metrics as dynamic graphical charts in the details view of the registered hosts. |
There was a problem hiding this comment.
Note to self to remember to update this paragraph when filesystem/swap utilization metrics are displayed in the UI. Also when metrics are exposed to MCP.
EMaksy
left a comment
EMaksy
left a comment
There was a problem hiding this comment.
Hey @balanza technicly the document can be merged, on the content nothing bit my eye :)
Clear the rest with @abravosuse and we should be fine to merge :)
balanza
force-pushed
the
prometheus-push
branch
from
c47ecec to
bd9015a
Compare
abravosuse
left a comment
abravosuse
left a comment
There was a problem hiding this comment.
@balanza explaining how to start prometheus with the --web.enable-remote-write-receiver flag in a sysconfig file scenario (which is what the user will have if they have followed our steps to install prometheus).
| ===== Enable the {prometheus} remote write receiver | ||
|
|
||
| {trento} supports basic authentication, bearer token, and mutual TLS (mTLS) on the agent side. Configure your reverse proxy to validate credentials using the method of your choice. | ||
| {prometheus} must be started with the `--web.enable-remote-write-receiver` flag. How to set this flag depends on how {prometheus} is managed on your platform (for example, via a sysconfig file, a systemd drop-in, or a command-line argument). |
There was a problem hiding this comment.
If the user has followed our manual steps to install Prometheus, it will be a sysconfig file scenario. I suggest we explain how to do it in that case. Something like the following:
{prometheus} must be started with the --web.enable-remote-write-receiver flag. How to set this flag depends on how {prometheus} is managed on your platform (for example, via a sysconfig file, a {systemd} drop-in, or a command-line argument). In a sysconfig file scenario, add ARGS="--web.enable-remote-write-receiver" to the /etc/sysconfig/prometheus configuration file.
3 participants
integrate user documentation to use Prometheus with Grafana Alloy