Skip to main content

Command Palette

Search for a command to run...

DevOps, Day - 79

Now, the next step is to learn about the Prometheus. It's an open-source system for monitoring services and alerts based on a time series data model.

Published
2 min read
DevOps, Day - 79
V

💻 Python | Docker | Jenkins | Networking | Git | Linux 💻


Passionate about leveraging technology to drive efficiency and deliver innovative solutions. Proficient in Python development, Docker containerization, Jenkins automation, computer networking, Git version control, and Linux administration. Skilled in collaborating with diverse teams to deliver high-quality software products. Proficient in AWS EC2 instance management and deployment.

Seeking new opportunities to apply my expertise and contribute to impactful projects. Let's connect and explore how we can work together!


Inter-personal Skills:

Communication, Adaptability, Emotional intelligence, Active listening, Collaboration.


Happy To Connect🔗😊

Feel free to reach me out😃@ --> vrishnishreevb531@gmail.com 📬


The architecture of Prometheus Monitoring: Prometheus follows a pull-based model that scrapes metrics data from monitored targets. It uses a multi-dimensional data model to organize and query these metrics. The key components of Prometheus architecture include:

  • Prometheus Server: This central component collects and stores time-series data, evaluates alerting rules and exposes a web UI for visualization and querying.

  • Data Scrapers: These components, known as "exporters," are responsible for exposing metrics from the target systems, which Prometheus scrapes on a regular basis.

  • Alert Manager: Responsible for handling alerts sent by the Prometheus server and performing actions like silencing, aggregation, and routing them to appropriate receivers.

  • Pushgateway: An optional component that allows short-lived jobs to push their metrics to Prometheus.

  • Client Libraries: Various client libraries are available for instrumenting applications and exposing their metrics to Prometheus.


  1. Multi-dimensional Data Model: Metrics are identified by a unique combination of labels, allowing for rich querying and aggregation.

  2. PromQL Query Language: A powerful and expressive language for querying and alerting on metrics data.

  3. Service Discovery: Support for dynamic service discovery and monitoring of containerized applications.

  4. Alerting: Define alerts and use the Alert Manager to handle them.

  5. Scalability: Designed for horizontal scalability to handle large environments.

  6. Remote Storage and Long-Term Storage: Can be configured to store data in remote or long-term storage systems.

  7. Pull-Based Model: Efficiently collects data from targets, reducing network and target resource usage.

  8. Docker and Kubernetes Integration: Well-suited for containerized environments.

  9. Exporters: A variety of exporters for popular services and platforms are available.

  10. Built-in Web UI: Provides visualization of metrics data and query capabilities.


  1. Prometheus Server

  2. Data Scrapers/Exporters

  3. Alert Manager

  4. Pushgateway

  5. Client Libraries for Instrumentation


Database Used by Prometheus: Prometheus uses its own custom time-series database that is optimized for efficiently storing and querying time-series data.


Default Data Retention Period in Prometheus: By default, Prometheus retains data for 15 days. You can configure this retention period according to your needs by setting the --storage.tsdb.retention.time flag when starting the Prometheus server.


Thank you so much for reading

Follow me on LinkedIn to see interesting posts like this : )

Linkedin

More from this blog

Vrishni Blog

103 posts

Python | Docker | Jenkins | Networking | Git | Linux | AWS EC2 | Tech Enthusiast | Collaborative | Open to Opportunities | Email: vrishnishreevb531@gmail.com 📬