39 Matching Annotations
  1. Jun 2024
    1. The classic account of industrialisation was David Landes’s The Unbound Prometheus (1969), which argued that economic transformation was rooted in three crucial substitutions: of ‘machines ... for human skill and effort’, of ‘inanimate for animate sources of power’, and of ‘mineral for vegetable or animal substances’ as raw materials.
  2. Apr 2024
    1. Prometheus is the creative and rebellious spirit which, rejected by God, angrily defies him and asserts itself; Ganymede is the boyish self which is adored and seduced by God. One is the lone defiant, the other the yielding acolyte. As the humanist poet, Goethe presents both identities as aspects or forms of the human condition.

      Prometheus as representing mythos (creativity and rebellion) whereas Zeus represents logos.

    2. Both belong to the period 1770–1775. Prometheus (1774)

      Is Prometheus (Goethe) published in 1773 or 1774? (Sebastiaan van Bommel making a mistake?)

    3. "Prometheus" is a poem by Johann Wolfgang von Goethe, in which the character of the mythic Prometheus addresses God (as Zeus) in misotheist accusation and defiance. The poem was written between 1772 and 1774 and first published in 1789 after an anonymous and unauthorised publication in 1785 by Friedrich Heinrich Jacobi. It is an important work of the Sturm und Drang movement.
    1. humanity's seemingly unstoppable instinct toward creation. The psychoanalyst Gaston Bachelard coined a term that encapsulates this drive: the "Prometheus complex."

      for - progress trap - Prometheus complex - adjacency - progress trap - Prometheus complex - Gaston Bachelard - Gaston Bachelard - French philosopher

      adjacency - between - progress trap - Prometheus complex - Gaston Bachelard - adjacency statement - Prometheus complex and progress traps have much in common: - both look at the shadow side of innovation - The mythology of Icarus geting too close the sun is one common to both - Bachelard wrote a pith work on the analysis of the element of fire, in which he introduced the concept of the Prometheus complex - https://philpapers.org/rec/OSEPCA

    2. Our hands and our brains will, perhaps unconsciously, drift toward the very thing we’re debating if we should do.

      for - quote - Prometheus complex - progress trap

      quote - Prometheus complex - progress trap - (see below)

      • Our hands and our brains will,
        • perhaps unconsciously
      • drift towad the very thing we're debating if we should do
      • author - Jenny Thomson
    3. as the rational, intellectual part of ourselves wrestles with the decision, a deeper, Promethean part of ourselves has pressed it already.

      for - quote - Prometheus complex - progress trap

      quote - Prometheus complex - progress trap - (see below)

      • As the rational, intellectual part of ourselves wrestles with the decision,
        • a deeper Promethean part of ourselves has pressed it (the red button) already
      • author - Jenny Thomson
    4. for - progress trap - Prometheus complex - Dan Carlin - Gaston Bachelard - philosopher

      summary - This short article brings up an interesting connection between - the Prometheus complex, - a term coined by the French philosopher Gaston Bachelard and - progress traps, - the unintended consequences of progress - The key insight is that human beings may have an Achilles Heel - the desire to know, even at the cost of harm - could be such a powerful impulsive urge - that we throw caution to the wind and - Icarus mythology may be a self-fulfilling prophecy - This also echos the views of my colleague Gyuri Lajos, - that invention for invention sake possesses this very dark side. - This is an important adjacency - as it questions the ethics of knowledge for knowledge sake - As we know from - the history of - progress and its shadowy counterpart, - the progress trap - our impulsive urge to invent has harmful impacts on everyone, - and these continually compound with time

    5. At the core, it seems the deeper drive is to invent anything that we’re capable of inventing.

      for - impulsive urge - invention - adjacency - progress trap - impulsive urge to invent - Prometheus complex - Gyuri Lajos perspective

      Adjacency - between - progress trap - impulsive urge - Gyuri Lajos perspective - Prometheus complex - adjacency statement - It would seem that the the Prometheus complex - is an apt description of that which Gyuri objects to in innovation, namely - innovation for innovation sake - in other words, the impulsive urge merely to know - even if it brings a terrible price

    6. under the name of the Prometheus complex

      for - definition - Prometheus complex

      definition - Prometheus complex - All those tendencies which impel us to know - as much as our fathers, more than our fathers - as much as our teachers, more than our teachers - author - Gaston Bachelard

    7. poster boy for the Enlightenment.

      for - interesting fact - Prometheus myth - poster boy of Enlightenment - meme - poster boy of the Enlightenment

      comment - The link takes us to an analysis of Lord Byron's poem on Prometheus - A good analysis of the meaning of Lord Byron's poem is here: - https://blog.homeforfiction.com/2020/04/18/byron-prometheus-existential-empowerment/

    8. [I wonder] whether or not human society actually has the agency that we think we have to not invent something if we think it might be bad.

      for - quote - Dan Carlin - quote - progress trap - Prometheus complex - Dan Carlin

      quote - progress trap - Prometheus complex - (see below)

      • [I wonder] whether or not human society actually has the agency that we think we have
        • to not invent something if we think it might be bad.
      • If you look down the technological road in the distance and see something horrible, could humankind go,
        • ‘Oh, you know what? We’re just not going to go there.’
      • I’m not sure we have that agency.

      comment - Deep Humanity praxis proposes that a new discipline of Progress traps is what is needed to do exactly this - Give us a meta perspective so that we can assess future harm and damage as - AN ACTIONABLE FORESIGHT, not a - TREATABLE HINDSIGHT

    1. humans are powerful precisely because they are temporally-bound, finite creatures. We are born and we die, no exception

      for - mortality salience - Deep Humanity - mortality salience - Prometheus - poem - analysis - quote - mortality salience

      quote - mortality salience - (see below)

      • The lesson is that humans are powerful
        • precisely because they are
          • temporally-bound,
          • finite creatures.
      • We are born and we die, no exceptions.
      • Byron’s “Prometheus” tells us that there is a lot of power
        • in dying and, particularly,
        • in knowing that we will die.
      • To face one’s mortality is “a mighty lesson”,
        • beyond the grasp of any (hypothetical) god.
  3. Mar 2024
    1. PromQL Example - http requests total https://youtu.be/STVMGrYIlfg?t=417

    2. To understand Prometheus even better, let's have a look at its core features. The dimensional data model, the metrics transfer format, the query language, integrated alerting, and support for service discovery.
    3. All right, with that out of the way, let's have a look at the system architecture of a basic Prometheus monitoring setup.

      Prometheus Architecture


    1. Target

      A target is the definition of an object to scrape. For example, what labels to apply, any authentication required to connect, or other information that defines how the scrape will occur.

    2. Time Series

      The Prometheus time series are streams of timestamped values belonging to the same metric and the same set of labeled dimensions. Prometheus stores all data as time series.

      A sample is a single value at a point in time in a time series.

      In Prometheus, each sample consists of a float64 value and a millisecond-precision timestamp.

    3. throttles



    1. 要直接抓取on-premise服务的metrics,你需要掌握以下几个关键领域的知识:

      1. Prometheus基础知识

      • 理解Prometheus架构:了解Prometheus的组件,包括Prometheus服务器、服务发现、抓取(scrape)配置、存储、查询语言(PromQL)等。
      • 配置抓取(Scrape):熟悉如何配置Prometheus的抓取任务,包括设置抓取间隔、超时时间、目标服务的metrics路径等。
      • Prometheus配置文件:了解Prometheus的配置文件结构,能够编写或修改配置文件以添加或修改抓取任务。

      2. 网络知识

      • 网络可达性:确保Prometheus服务器能够访问on-premise服务的网络地址。这可能涉及到配置网络路由、防火墙规则等。
      • 安全通信:如果metrics需要安全传输(推荐),了解如何配置HTTPS或其他加密方法。

      3. 安全性和认证

      • 认证机制:如果on-premise服务的metrics端点需要认证,了解如何在Prometheus的抓取配置中设置认证信息。这可能包括基本认证、Bearer Token认证或其他自定义认证机制。
      • TLS/SSL:了解如何为Prometheus配置TLS证书,以安全地抓取支持HTTPS的服务。

      4. on-premise服务的监控和metrics暴露

      • 服务配置:了解如何在你的on-premise服务中启用和配置metrics的暴露。这通常涉及到在应用中集成Prometheus客户端库,并在特定端口和路径上暴露metrics。
      • Metrics命名和组织:了解Prometheus的metrics命名规范和最佳实践,以确保你的metrics易于理解和查询。

      5. PromQL和仪表盘

      • 查询语言(PromQL):了解如何使用PromQL查询语言来检索和分析metrics数据。
      • 可视化和仪表盘:熟悉如何使用Grafana或Prometheus自带的UI来创建仪表盘,以可视化和监控你的metrics数据。



      1. 确保服务可达:确保Prometheus实例能够网络访问到on-premise服务。
      2. 配置metrics暴露:在你的on-premise服务中启用metrics暴露,通常是在特定的HTTP端点。
      3. 添加抓取配置:在Prometheus配置文件中添加一个新的抓取任务,指向你的on-premise服务的metrics端点。
      4. 配置安全性(如果需要):根据需要为抓取任务配置HTTPS、认证等。
      5. 重启Prometheus(如果需要):应用新的配置后,根据你的部署方式,可能需要重启Prometheus服务。
      6. 验证和调整:使用Prometheus UI或Grafana验证metrics是否被正确抓取,并根据需要调整抓取配置或metrics暴露。


    2. "Federation"(联邦)这个术语在Prometheus的上下文中被用来描述一种特定的数据聚合模式,它允许从多个Prometheus实例中汇总数据到一个中心实例。这个概念源于更广泛的联邦理念,即不同实体(在这种情况下是Prometheus服务器)保持相对的自治,同时共享一些资源或数据以实现更大的目标。



      • 自治性:每个Prometheus实例可以独立监控其负责的特定服务或基础设施部分。这意味着每个实例可以有其自己的配置、规则、警报和存储策略,适应其监控目标的特定需求。
      • 共享:虽然每个实例都是自治的,但它们通过联邦机制共享一部分数据。这允许创建一个高层级的视图,整合了来自多个源的监控数据,以便进行全面的分析和报告。
      • 可扩展性和灵活性:联邦允许监控系统以可扩展和灵活的方式成长。可以根据需要添加更多的Prometheus实例来监控新的服务或基础设施部分,而不会影响到现有的监控设置或需要重建整个监控架构。
      • 减轻中心实例的负担:通过只从各个自治实例中汇总必要的数据,中心Prometheus实例的资源负担可以得到显著减轻。这使得中心实例可以更有效地处理数据,提供全局视图,而不必处理每个指标的全部细节。



      • 多层监控架构:在大型或复杂环境中,顶层Prometheus实例可以用于聚合和查看关键业务指标,而更底层的实例则负责监控具体的服务或基础设施组件。
      • 跨区域或跨数据中心监控:在地理上分散的环境中,每个位置可以有自己的Prometheus实例,而一个联邦实例则负责聚合这些数据,提供一个统一的监控视图。
      • 性能和可用性优化:联邦可以帮助优化性能和可用性,通过分散查询负载和降低单个实例的数据保留需求。


    3. Get metrics outside of prometheus

      要实现这个目标,你可以通过几种方法来配置Kubernetes中的Prometheus,使其能够监控集群外的on-premise services。以下是一些建议的解决方案:

      1. 使用Federation

      Prometheus支持使用联邦(Federation)功能来从其他Prometheus服务器中汇聚数据。你可以配置Kubernetes集群中的Prometheus实例作为一个联邦父节点,从集群外的on-premise Prometheus实例中抓取metrics。这种方法允许你从多个Prometheus实例中选择性地聚合数据。

      1. 在集群外的Prometheus配置中,确保它的metrics对外是可访问的,设置适当的权限和防火墙规则。
      2. 在Kubernetes集群的Prometheus配置中,添加一个新的scrape配置,指向集群外Prometheus的/federate端点,并使用match[]参数指定要抓取的metrics集。

      2. 直接抓取on-premise服务的metrics


      1. 在Kubernetes集群的Prometheus的配置文件(通常是prometheus.yaml),添加一个新的scrape job。
      2. 在这个job中,使用静态配置指定on-premise服务的地址和端口,类似于你在on-premise Prometheus中所做的。

      3. 使用Prometheus PushGateway

      如果直接抓取on-premise服务的metrics存在网络隔离或安全策略的问题,可以考虑使用Prometheus PushGateway。on-premise服务可以定期将metrics推送到PushGateway,而Kubernetes集群中的Prometheus则可以从PushGateway抓取这些metrics。

      1. 部署Prometheus PushGateway在一个对两个环境都可访问的位置。
      2. 配置on-premise服务将metrics推送到PushGateway。
      3. 在Kubernetes集群的Prometheus配置中,添加一个新的scrape job来抓取PushGateway的metrics。



    4. 在Prometheus的上下文中,当配置scrape jobs以收集来自不同服务的metrics时,安全性变得至关重要,尤其是当这些服务部署在不受信任的网络或者需要确保数据传输安全和访问控制时。Prometheus支持几种认证和加密机制来保证数据的安全传输和访问控制,包括基本认证、Bearer Token认证和通过TLS进行传输加密。下面是对这些机制的简要解释:

      基本认证(Basic Authentication)


      在Prometheus配置中,可以为特定的scrape job配置基本认证,示例如下:

      yaml scrape_configs: - job_name: 'my-secure-service' scheme: https # 确保使用https static_configs: - targets: ['secure-service.example.com:443'] basic_auth: username: 'myUsername' password: 'myPassword'

      Bearer Token认证

      Bearer Token认证是一种更安全的HTTP认证方法,通常用于OAuth 2.0等认证框架。在这种方法中,客户端发送一个Authorization请求头,包含一个安全令牌,这个令牌代表客户端的认证凭据。

      在Prometheus的场景中,Bearer Token可以用于访问需要OAuth2.0或类似机制保护的服务。配置示例如下:

      yaml scrape_configs: - job_name: 'my-oauth2-service' scheme: https # 使用https static_configs: - targets: ['oauth2-service.example.com:443'] authorization: type: 'Bearer' credentials: 'mySecretToken'




      yaml scrape_configs: - job_name: 'my-tls-service' scheme: https # 使用https static_configs: - targets: ['tls-service.example.com:443'] tls_config: ca_file: '/path/to/ca.crt' # CA证书,用于验证服务器证书 cert_file: '/path/to/client.crt' # 客户端证书 key_file: '/path/to/client.key' # 客户端密钥 # 如果服务使用的是自签名证书,则需要设置下面这个选项 insecure_skip_verify: false


    5. 在Prometheus中,"scrape job"是指定定时抓取(或称为"scraping")目标服务metrics的配置单元。每个scrape job定义了一组目标(targets),这些目标是Prometheus需要定期访问并收集metrics数据的服务或实例。scrape job的配置包括抓取频率、目标服务的地址、认证信息(如果需要的话)以及其他抓取行为的配置细节。


      • Job Name:每个scrape job都有一个唯一的名称,这个名称在Prometheus的metrics中用作job标签的值,用于区分来自不同scrape jobs的数据。
      • Targets:这些是Prometheus将要抓取metrics的具体服务实例。目标可以是静态配置的,也可以是通过服务发现动态发现的。
      • Scrape Interval:定义了Prometheus抓取每个目标metrics的频率。例如,scrape_interval: 15s意味着Prometheus每15秒向每个目标发送一次抓取请求。
      • Metrics Path:指定了目标服务暴露metrics的HTTP路径,默认值是/metrics
      • Scrape Timeout:指定了等待抓取请求返回的最长时间。如果超过这个时间目标还没有响应,抓取请求就会被取消。
      • Authentication and Authorization:如果目标服务需要认证,可以在scrape job配置中指定必要的认证信息,如基本认证、Bearer token或TLS配置。


      下面是一个简单的scrape job配置示例,它定义了一个名为my-service的scrape job,用于抓取运行在localhost:9090上的服务的metrics。

      yaml scrape_configs: - job_name: 'my-service' scrape_interval: '15s' static_configs: - targets: ['localhost:9090']


      Prometheus支持多种服务发现机制来动态发现scrape targets,比如Kubernetes、Consul、AWS EC2等。使用服务发现,Prometheus可以自动更新它的目标列表,以匹配动态变化的环境,例如在Kubernetes集群中自动发现和抓取新部署的服务。


      Scrape jobs是Prometheus监控配置的核心。它们确保Prometheus能够定期从配置的服务中收集metrics,从而提供系统和应用性能的实时视图。合理配置scrape jobs对于确保数据的准确性和时效性至关重要。

    6. Prometheus Federation 是一种机制,允许一个Prometheus服务器从另一个Prometheus服务器中抓取选定的数据。这种方法经常用于创建层次化的监控架构,其中高层级的Prometheus实例聚合和监控来自多个源的数据,而这些源可能是其他Prometheus实例。Federation特别适用于大规模环境、多层监控策略,或者当需要跨不同网络区域汇总监控数据时。




      要通过Federation抓取metrics,你需要在父Prometheus实例上配置一个新的scrape job,专门用于抓取来自子Prometheus实例的数据。这个配置可以指定要从子实例抓取哪些metrics,使用match[]参数来过滤。


      假设你想从一个on-premise Prometheus实例抓取特定的metrics到Kubernetes集群中的Prometheus实例。你可以在Kubernetes Prometheus的配置文件中添加类似以下的配置:

      yaml scrape_configs: - job_name: 'federate' scrape_interval: '15s' honor_labels: true metrics_path: '/federate' params: 'match[]': - '{job="prometheus"}' - '{__name__=~"job:.*"}' static_configs: - targets: - 'on-premise-prometheus.example.com:9090'


      • job_name:这个scrape job的名称。
      • scrape_interval:抓取数据的频率。
      • honor_labels:设置为true,意味着Prometheus将保留从源Prometheus实例获取的metrics的标签,避免标签冲突。
      • metrics_path:指向子实例的/federate端点。
      • params:定义了一个match[]列表,用于指定哪些metrics应该被抓取。在这个例子中,它匹配所有标签为job="prometheus"的metrics,以及所有名称与job:.*正则表达式匹配的metrics。
      • static_configs:定义了子Prometheus实例的地址。



      • 可扩展性:Federation允许构建可扩展的监控架构,通过在不同层次上聚合数据来管理大量的监控指标。
      • 灵活性:可以非常精细地控制哪些metrics被上层Prometheus实例抓取,允许构建定制的监控视图或汇总。


      • 性能:抓取大量metrics可能会对网络和Prometheus实例的性能产生影响。合理配置scrape_interval和选择要抓取的metrics非常重要。
      • 安全性:确保网络通信安全,特别是在跨网络边界进行Federation时,需要考虑加密和认证机制。


    1. Prometheus Architecture

      • the main Prometheus server which scrapes and stores time series data
      • client libraries for instrumenting application code
      • a push gateway for supporting short-lived jobs
      • special-purpose exporters for services like HAProxy, StatsD, Graphite, etc.
      • an alertmanager to handle alerts
      • various support tools
  4. Feb 2023
    1. Hesiod’s depictionof humans in the myth of Prometheus and Pandora. We consider theimplications of this myth for the Greek view of society and particularly of

      women and gender roles.

      If my perception of mythology and orality is correct, can we look at Indigenous stories, myth, and knowledge and draw parallels from their knowledge about women and gender to similar stories in the Western canon which have lost linkage to their narratives? What would this show us potentially about Western mythology and gender studies?

  5. Jan 2023
    1. tl;dw (best DevOps tools in 2023)

      1. Low-budget cloud computing : Civo (close to Scaleway)
      2. Infrastructure and Service Management: Crossplane
      3. App Management - manifests : cdk8s (yes, not Kustomize or Helm)
      4. App Management - k8s operators: tie between Knative and Crossplane
      5. App Management - managed services: Google Cloud Run
      6. Dev Envs: Okteto (yeap, not GitPod)
      7. CI/CD: GitHub Actions (as it's simplest to use)
      8. GitOps (CD): Argo CD (wins with Flux due to its adoption rate)
      9. Policy Management: Kyverno (simpler to use than industry's most powerful tool: OPA / Gatekeeper)
      10. Observability: OpenTelemetry (instrumentation of apps), VictoriaMetrics (metrics - yes not Prometheus), Grafana / Loki (logs), Grafana Tempo (tracing), Grafana (dashboards), Robusta (alerting), Komodor (troubleshooting)
  6. Dec 2021
    1. Support for exemplars is available for the Prometheus data source only

      the exemplar "feature" is not availble to all data sources.

  7. Mar 2021
    1. We use Prometheus to collect time-series metrics and Grafana for graphs, dashboards, and alerts.

      How Prometheus and Grafana can be used to collect information from running ML on K8s

  8. Dec 2019

      The novel’s subtitle invokes the trickster hero of Greek mythology, Prometheus, who defies the Gods by stealing fire (a symbol of knowledge) and giving it to humanity. Akin to Victor Frankenstein, Prometheus is also credited with the creation of man, which he fashions out of clay. As punishment for the disobedience, Zeus condemns Prometheus to eternal torment: he is chained to a rock for eternity while an eagle feeds on his liver. Shelley’s husband Percy would later take up the Prometheus myth in the closet drama Prometheus Unbound, published in 1819. Reading the novel against the myth, we can understand Prometheus’s punishment for the Gods akin to Victor’s psychological torment for defying nature.

  9. Mar 2019
    1. Grafana

      Parte do 1.o assunto no tópico 705 Service Operations: 705.1 IT Operations and Monitoring (weight: 4)

      Understand the architecture of Prometheus, including Exporters, Pushgateway, Alertmanager and Grafana

      Mais informações também nesse post de nosso blog.

    2. Prometheus

      Parte do 1.o assunto no tópico 705 Service Operations: 705.1 IT Operations and Monitoring (weight: 4)

      Understand the architecture of Prometheus, including Exporters, Pushgateway, Alertmanager and Grafana

      Mais informações também nesse post de nosso blog.

  10. Aug 2018
    1. for when they list into the womb That bred them they return, and howle and gnaw My Bowels, thir repast;

      This sounds similar toPrometheus, who was punished by Zeus for giving fire to man. Prometheus was bound in Tartarus, where a vulture every day gnawed out his liver.

  11. Jun 2017
    1. public void increment(String label, String topic) { + Stats.incr(label); + }

      import io.prometheus.client.Counter; public static final Counter requests = Counter.build() .name("requests_total").help("Total requests.").register();

      public void increment(String label, String topic) { requests.inc(); // Your code here. } }

    2. The component is pluggable, you can configure ingestion of metrics to any monitoring system by implementing MetricCollector interface. By default metrics are sent to Ostrich, statistic library bundled into secor.

      Just inject prometheus simple client into this module and you could get prometheus working for secor.

  12. Jul 2016