Monitoring– Metrics, Logs & Traces
You see at a glance how your services are doing. Metrics, logs and traces end up in one place. Each SecTepe.Comm service comes with a ready-made dashboard.
Request a demoAt a glance
- Metrics for every service
- Clear dashboards
- Logs collected in one place
- Request tracing
- Alert rules
- Pre-built dashboards
Features at a glance
All monitoring parts fit together and run right away. Metrics, logs and traces are linked to each other. So you find bugs fast and make your systems faster.
Metrics
A database stores values over time, such as load or response time. Many collectors feed it data. You analyze it with its own query language.
Dashboards
Charts show metrics, logs and traces clearly in one tool. You build dashboards, alerts and notes as you need them.
Logs
All logs end up in one place. You search by labels such as the service. As volumes grow, you add servers, and costs stay low.
Tracing
Follow a request through all services involved, from the entry point to the database. So you see where things get stuck. The data follows the open OpenTelemetry standard.
Alerting
Similar alerts are grouped and sent to the right team, by chat, email or on-call service. During maintenance, you mute them.
Pre-built Dashboards
Dashboards are ready to use. There is one for each SecTepe.Comm component, such as chat, video meetings and file storage.
Technology & integration
The monitoring is fully open source and follows the OpenTelemetry standard. All SecTepe.Comm services send metrics, logs and traces from day one. You see everything in one shared interface. Alerts go straight to chat rooms or email groups.
- • Metrics database with collectors for each service
- • Dashboards that are set up automatically
- • Log store with a collector for all containers
- • Tracing based on OpenTelemetry
- • Alerts by chat or email
- • Long-term storage for metrics
Technical foundation
SecTepe.Comm uses proven open-source building blocks. Prometheus with Node Exporter, cAdvisor, Alertmanager and Sloth handles metrics and alerts. Mimir or Thanos store them for the long term. Grafana and Grafana OnCall provide dashboards and on-call. Loki with Promtail collects logs, SigNoz on ClickHouse handles tracing. Alerts go via ntfy and Matrix. k6 runs the test scripts, OpenBao holds the keys. Wazuh with Falco detects attacks.
Your benefits
- Full visibility from day one
- One view of all your operations
- Early warning when something is out of line
- Find the root cause fast
- Alerts where you already work
- Keep data for a long time at low cost
- Fully open source
How monitoring works in practice
The stack handles three kinds of data: metrics, logs and traces. A metrics database collects metrics. A log collector sends container logs to the log store. Your own apps can send traces to a tracing server with its own fast database. The dashboards show metrics and logs side by side.
What is ready from the start
- One collector delivers server metrics like CPU, RAM and disk. Another adds metrics for each container.
- Ready-made dashboards cover sign-in, reverse proxy, VPN, DNS filter, chat, video, logs and more.
- Users sign in to the dashboards through the central login (single sign-on). Roles map to admin, editor and viewer. A local admin login stays as a fallback.
- Logs are kept for 30 days by default. In a simple container setup, metrics are also kept for 30 days. You can change both with one setting each.
- In the search view, you search logs with a query language. A filter narrows the search to one container, such as chat or sign-in.
Alerts and escalation
In a simple container setup, warnings go to a push notification channel. Critical alerts go to that channel, a chat room and email. On Kubernetes, critical alerts go to an on-call tool, which delivers them through chat. A phone step is built in but turned off.
Core services such as sign-in, mail and chat have service level objectives (SLOs), meaning agreed targets for availability. An alert fires when the allowed error budget runs out too fast. Test scripts try a login and a chat message every five minutes.
Operation and data control
All parts are open source and run in your own environment. On Kubernetes, the metrics database runs twice for high availability. It keeps only recent data on local disks. A helper moves older metrics to S3 storage at IONOS. Queries over longer periods then use that long-term store. The storage keys come from a vault.
Common questions
Do our own apps send traces without extra work? No. An app needs the OpenTelemetry library and the collector address. The docs show the setup for Python and Node.js.
Do the dashboards detect attacks? No. Detection of password guessing, web firewall hits and container events runs in the SIEM. The dashboards show volumes and trends. The metric alerts cover operations.
Can we watch SecTepe.Core here too? Yes. A metrics agent in each Core cluster sends selected metrics here. A separate folder holds four Core dashboards.
Ready for observability?
We design and run your observability stack. You get dashboards, alert rules and runbooks that fit the way your team works.
How we work with you
We want to work with you for the long run, not just deliver once. Our way of working has four steps. So you always know what comes next, who does what and what you get.
1. Free initial conversation
We learn where you stand and what you want. In 30 to 45 minutes we check if we are a good fit. We show you options and answer your questions. There is no obligation.
2. Current state review
We check where you stand today: tech, processes and rules. You get a list of strengths and gaps, sorted by urgency. Our offer is based on it.
3. Delivery with a dedicated lead
An experienced lead guides you through the project. You get clear goals, an open plan for time and cost, and a status every week. All results are written down and belong to you.
4. Running and reviewing
After the project we stay with you. We run systems for you, check them at set times and keep track of open tasks. When new threats or new rules come up, we get in touch.
Common questions
We hear these questions most often in a first call. For anything else, write to hello@sectepe.de or give us a call.
- How do we start working with SecTepe?
- Every project starts with a free first call. Then you get an offer with scope, timeline and result. If you like, we start small with a pilot. That way you get to know us before the real work starts.
- What company sizes and sectors do you support?
- We work for small and mid-sized firms, for parts of large groups and for operators of critical infrastructure (KRITIS). Often that means industry, trades, health, banks, energy and public bodies. Our focus is mid-sized firms in Germany, Austria and Switzerland.
- Do you work on site, remotely or hybrid?
- Both. Reviews, advice and most services run remotely from German data centers. For workshops, training and emergencies we come to you, mainly in North Rhine-Westphalia, the Rhineland and the Ruhr area. We travel further when needed.
- Which standards and regulations do you cover?
- We work to ISO 27001:2022, BSI IT-Grundschutz, TISAX, B3S KRITIS, NIS2 and DORA, plus sector-specific rules. Our methods build on known frameworks such as NIST CSF, MITRE ATT&CK, OWASP and OSSTMM. We combine them to fit each project.
- How do you protect the confidentiality of my data?
- By contract and by technology. Before every project, both sides sign a non-disclosure agreement. Your data stays in German data centers. Every access needs a second login factor and is checked one by one. Our whole team is bound to secrecy by contract and under the GDPR.