Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
aura-engine
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
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
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
Lars Kruse
aura-engine
Commits
819ca4e7
Commit
819ca4e7
authored
4 years ago
by
David Trattnig
Browse files
Options
Downloads
Patches
Plain Diff
Documentation for monitoring.
parent
47153fdc
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/engine-features.md
+60
-0
60 additions, 0 deletions
docs/engine-features.md
with
60 additions
and
0 deletions
docs/engine-features.md
+
60
−
0
View file @
819ca4e7
...
...
@@ -167,6 +167,66 @@ schemas:
*
`/app/trackservice`
................. Web Application for displaying the Track-Service
*
`/app/clock`
........................ Web Application for displaying the studio clock
## Monitoring
You have following options to monitor the Engine:
*
Send mails on errors and warnings
*
Engine Status Information
*
Engine Heartbeat
### Send mails on errors and warnings
To activate you'll need to set some mail account within the
`[monitoring]`
section of your configuration.
```
ini
[monitoring]
mail_server
=
"mail.o94.at"
mail_server_port
=
"587"
mail_user
=
"aura@o94.at"
mail_pass
=
"---SECRET--PASSWORD---"
# If you want to send multiple adminmails, make them space separated
admin_mail
=
"david@subsquare.at"
# Which from mailadress should be used
from_mail
=
"monitoring@aura.engine"
# The beginning of the subject. With that you can easily apply filter rules using a mail client
mailsubject_prefix
=
"[Aura Engine]"
```
### Engine Status Information
You can get various status fields & flags using the
`/status`
endpoint.
> Please note this is a rather expensive call. If you need to call this on a regular basis
for continious monitoring, the
*Heartbeat*
option might be preferred.
### Engine Heartbeat
Instead of checking all status properties, the Heartbeat only validates the vital ones
required to run the engine. If all of those are valid, as network socket request is sent
to a defined server.
This heartbeat is sent continiously based on the configured
`heartbeat_frequency`
.
```
ini
# Server where heartbeat info is sent to
heartbeat_server
=
"127.0.0.1"
# Some UDP port
heartbeat_port
=
43334
# Seconds how often the vitality of the Engine should be checked (0 = disabled)
heartbeat_frequency
=
1
```
The service receiving this heartbeat ticks can decide what to do with that information.
One scenario could be switching to another Engine instance or any other failover scenario.
Under
`contrib/heartbeat-monitor`
you'll find some sample application digesting these
heartbeat signals.
## Read more
-
[
Overview
](
/README.md
)
...
...
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