`service.version` is very useful to slice and dice metrics for root cause analysis
`deployment.environment`: it's the previous name for `deployment.environment.name` and many users still use this older attribute name
Signed-off-by: Cyrille Le Clerc <cyrille.leclerc@grafana.com>
* Fix header anchor CSS
This is a leftover from 60899b37d2, where
Font Awesome was removed. The missing font causes the link icon to show as
a tofu. Tabler, the new library that was introduced as a replacement has a
link icon CSS class we can use instead. I also adjusted the left pad.
Signed-off-by: Jeremy Rickards <jeremy.rickards@sap.com>
* Address PR comment
Signed-off-by: Jeremy Rickards <jeremy.rickards@sap.com>
---------
Signed-off-by: Jeremy Rickards <jeremy.rickards@sap.com>
* Fixup some more formatting issues.
* Remove references to IRC/Matrix briding, this has been removed.
* Update "Community" heading to be more descriptive.
Signed-off-by: SuperQ <superq@gmail.com>
To improve the style and add an automatic table of contents
and relative links, convert the community page from html to
Nanoc markdown.
Signed-off-by: SuperQ <superq@gmail.com>
Thomas Peitz got added in the previoun commit, but failed to approve
the PR in time. I remove his name again in this commit so that we can
easily revert once we hear back from him and can continue the
onboarding.
Signed-off-by: beorn7 <beorn@grafana.com>
idelta and irate are implemented now.
We also realized that the 1st histogram can be safely ignored if there
is a counter reset between the 1st and the 2nd histogram. Therefore,
we don't even have to error out on incompatible bucket layout in this
case.
Signed-off-by: beorn7 <beorn@grafana.com>
The security model is written in a very technical form that is hard to
understand for naive users. Naive users are, sadly, also most prone to
run Prometheus components exposed to the internet. I have little hope
that those users will read this page at all, but if they do, they
should get the message. Furthermore, we have had multiple incidents
where 3rd parties "uncover" "vulnerabilities and security flaws".
There is nothing to uncover, and the flagged behaviors are by design.
We have to make that more clear.
This partially addresses #2201, but I think we need to do more. In
particular, we should add a section about /pprof (and why we have it
on by default), be clearer about DoS'ing ("It is more likely that a
component will be accidentally taken out by a trusted user than by
malicious action." can easily be understood in an unintended way), and
provide more context about the usage of the word "untrusted".
Signed-off-by: beorn7 <beorn@grafana.com>
Add native histogram specification
It is partially more documentation than specification, but I assume
the specification section is still the least bad place for it.
This is intentionally not yet complete. TODOs mark the missing parts,
most of which cannot be resolved at the moment because implementation
work is still missing and/or decisions still have to be made.
The intention here is to finally get something out here, even if it is
pretty much still a "living document". It will probably take us
another year or so to resolve all TODOs.
Signed-off-by: beorn7 <beorn@grafana.com>
---------
Signed-off-by: beorn7 <beorn@grafana.com>
