Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
K
km3mon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
km3py
km3mon
Commits
4a66abe5
Verified
Commit
4a66abe5
authored
4 weeks ago
by
Tamas Gal
Browse files
Options
Downloads
Patches
Plain Diff
Update README
parent
68235bab
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Pipeline
#62192
passed
4 weeks ago
Stage: docker
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+4
-1
4 additions, 1 deletion
README.md
with
4 additions
and
1 deletion
README.md
+
4
−
1
View file @
4a66abe5
...
...
@@ -45,6 +45,9 @@ To stop it it
## Monitoring the monitoring
Log files are kept in
`logs/`
, data dumps in
`data/`
and plots in
`plots/`
.
These folders can be used (mounted) by all services defined in the
`docker-compose.yml`
file. The
`frontent`
service for example which runs
the Webserver mounts
`plots/`
to have access to the plots.
To check the logs or follow them in real-time (
`-f`
) and limit the rewind
to a number of lines
`--tail=N`
, e.g.
...
...
@@ -87,7 +90,7 @@ monitoring_process:ztplot RUNNING pid 24, uptime 1 day, 5:21:06
reconstruction:time_residuals RUNNING pid 27, uptime 1 day, 5:21:06
```
The processes are grouped accordingly (logging, monitoring_process etc.) and
The processes are grouped accordingly (
`
logging
`
,
`
monitoring_process
`
etc.) and
automatically started in the right order.
You can stop and start individual services using
``supervisorctl stop
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment