cdaguerre
Repos
74
Followers
27
Following
7

Events

Created at 12 hours ago
phpfpm_process_request_duration should not be a gauge

According to the php docs, phpfpm_process_request_duration should not be a gauge, it should be a counter.

It states:

| name | description | |-- | --| | requests | The total number of requests served. | | request duration | The total time in seconds spent serving requests. |

To get a gauge you'd have to caculate request duration / requests, which from the looks of the initial PR is not the case.

While I think this is a bug, this should be probably not be changed because I guess it could break a lot of setups since it's been around for 4 years... Introducing a new metric called phpfpm_process_average_request_duration (histogram) would probably be a better idea... Would solve https://github.com/hipages/php-fpm_exporter/issues/77

Related issues: https://github.com/hipages/php-fpm_exporter/issues/66 https://github.com/hipages/php-fpm_exporter/issues/205

Created at 12 hours ago
closed issue
TTL from Cache-Control header of backend response

Hi, is it possible to configure Souin (using the caddy plugin) to set the ttl from the Cache-Control header set by the backend?

Created at 1 day ago
issue comment
TTL from Cache-Control header of backend response

Arghh That makes sense. Could have figured that out by myself. RTFM ;) Thank you very much for your help.

Created at 1 day ago
issue comment
TTL from Cache-Control header of backend response

Hi @darkweak and thanks for your quick response:

This is an example of what I see:

| Header | Value | |----------------|-------------------| | Cache-Control | max-age=3600, public, s-maxage=3600 | | Age | 7 | | Cache-Status | Souin; hit; ttl=113 | | Vary | Accept |

In this example, to my understanding, you can see the TTL set for the cached request is 120, that it's already 7 seconds old and that it will remain in cache for 113 more seconds. I would expect it to be cached for as long as the s-maxage value states.

This is what my Caddyfile looks like, nothing special, really....

{
    debug
    order cache before rewrite
    cache {
        default_cache_control no-store
    }
}

:443 {
    cache
  
    reverse_proxy nginx:80
}

Is this a bug or am I missing something?

Created at 1 day ago
opened issue
TTL from Cache-Control header of backend response

Hi, is it possible to configure Souin (using the caddy plugin) to set the ttl from the Cache-Control header set by the backend?

Created at 2 days ago
pull request opened
add service annotations
Created at 3 days ago
create branch
cdaguerre create branch feat-annotations
Created at 3 days ago
Created at 3 days ago
cdaguerre create tag 0.0.32
Created at 1 week ago

chore: improve sentry exporter

Created at 1 week ago

chore: improve sentry exporter

Created at 1 week ago
pull request opened
Make zsh completion list configurable
Created at 3 weeks ago
create branch
cdaguerre create branch feat/make-zsh-completion-configurable
Created at 3 weeks ago
Created at 3 weeks ago
cdaguerre create tag 0.0.31
Created at 4 weeks ago
cdaguerre delete branch feat/message-strategy
Created at 4 weeks ago

feat: allow linking message span instead of forcing child

chore: add stamp specs

chore: document message link strategy

Created at 4 weeks ago
pull request closed
feat: allow linking message span instead of forcing child
Created at 4 weeks ago

chore: document message link strategy

Created at 4 weeks ago

chore: document message link strategy

Created at 4 weeks ago

chore: document message link strategy

Created at 4 weeks ago

chore: document message link strategy

Created at 4 weeks ago

chore: add stamp specs

Created at 4 weeks ago