Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
D
docs
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Administrator
docs
Commits
102961bb
Commit
102961bb
authored
Jun 10, 2018
by
Richard Hartmann
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
docs/philosophy/: Feedback by @brian-brazil and typos
Signed-off-by:
Richard Hartmann
<
richih@richih.org
>
parent
5292ccc5
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
15 additions
and
9 deletions
+15
-9
goals.md
content/docs/philosophy/goals.md
+9
-3
philosophy.md
content/docs/philosophy/philosophy.md
+5
-5
philosophy_overview.md
content/docs/philosophy/philosophy_overview.md
+1
-1
No files found.
content/docs/philosophy/goals.md
View file @
102961bb
...
...
@@ -16,7 +16,7 @@ As a monitoring system, Prometheus is being relied upon to alert humans that
they need to take action in order to prevent undesired system state.
Thus, its most important function is to keep the pipeline of ingestion, rule
evaluation, and alert
hand-off
working.
evaluation, and alert
notifications
working.
The second most important function is to give humans context about these alerts
by allowing access to the most recent data Prometheus ingested
...
...
@@ -27,7 +27,7 @@ Note that this goal might result in widely different design decisions and thus
operational patterns for different parts of our ecosystem:
For Prometheus itself, this means running every instance as an island of data
completely detached from every other instance
, except for optional federation
.
completely detached from every other instance.
For Alertmanager on the other hand, it means the exact opposite: meshing all
instances closely together, sharing knowledge about alerts and their
...
...
@@ -35,13 +35,19 @@ notifications.
## Simple operation
Operation of Prometheus should be as
easy
and failure-tolerant as possible. We
Operation of Prometheus should be as
simple
and failure-tolerant as possible. We
try to put required complexity into earlier phases, going through them less
often and ideally still while under the control of a smaller subset of people.
One example of this would be the preference of statically linked binaries over
dynamically-built ones.
## Keep dependencies clear and limited
Any non-trivial system needs to integrate with other systems. To keep the
resulting complexity low, we will always try to have the fewest interfaces
possible and keep their resulting complexity as low as possible.
## Automation
Computers are good at doing the same thing over and over again, and quickly.
...
...
content/docs/philosophy/philosophy.md
View file @
102961bb
...
...
@@ -30,12 +30,12 @@ McIlroy's initial version from 1978](http://emulator.pdp-11.org.ru/misc/1978.07_
## Embrace cloud-native technologies
In many ways, the cloud-native approach mirrors the Unix philosphy, updating it
In many ways, the cloud-native approach mirrors the Unix philos
o
phy, updating it
for the modern world.
1.
Micro-services are the equivalent of doing one thing well
2.
Ubiquitous APIs enable interopera
t
bility in the cloud-native world
3.
Releasing early, re
a
leasing often, and failing quickly is important when
2.
Ubiquitous APIs enable interoperability in the cloud-native world
3.
Releasing early, releasing often, and failing quickly is important when
failure is part of expected operations
4.
Automation is key, freeing up humans to make more useful use of their time
...
...
@@ -54,7 +54,7 @@ charge.
Prometheus is a project of convicted and passionate individuals. As we do not
have a profit motive, nor quarterly projections, or any other requirement to
meet arbitrary business requirements, we can fo
x
us on getting things right. This
meet arbitrary business requirements, we can fo
c
us on getting things right. This
also means that we are free to suggest other implementations and projects if
they are a better fit for a particular use-case.
...
...
@@ -66,4 +66,4 @@ will always strive to be welcoming to everyone.
As an example of this, many of us are investing their personal time helping
individuals or communities by educating and helping them to be more productive
in the tech sector, as well as sponsoring diversity efforts, for example paying
for travel and accomodation at
[
PromCon
](
https://promcon.io
)
.
for travel and accom
m
odation at
[
PromCon
](
https://promcon.io
)
.
content/docs/philosophy/philosophy_overview.md
View file @
102961bb
...
...
@@ -3,7 +3,7 @@ title: Philosophy overview
sort_rank
:
1
---
We have structured our considerations for developing and working with Prometh
ue
s
We have structured our considerations for developing and working with Prometh
eu
s
into four groups in decreasing order of importance, and likelihood to change.
1.
Philosophy
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment