Mike Belov

Thanks @dafvid! I'm no longer working at nginx, so I assume Amplify team will cover this one.

Thanks @seanmavley, it's a known issue, we need to start agent after the system has access to network. We will address this issue soon, please bear with us.

Hi, @kukulich! We automatically remove all objects (including FPM pools) which sent payload last time more than a week ago. Yes, a week is a long period, so we will...

@abhishek-plackal we transformed your question to a support ticket but you've never replied. @IWriteThings, @centminmod - as @gshulegaard said - please enable debug logging and share some lines from your...

@IWriteThings in the log lines above: `ut="-"` That means that upstream response time was not measured since it was not a request to any upstream. If you use nginx as...

Hi @centminmod! The agent doesn't work at all, right? May I ask you to share /var/log/amplify-agent/agent.log?

Hi @nan008 ! Current architecture is based on the system object as the root one. We can't currently separate NGINX objects from system. Are there any particular concerns about collecting...

@vietcgi interesting, is it a high-load system? how many requests per second do you have? can you share more lines from the agent log?

Thanks, @vietcgi. Well, you have a high-load system and it looks like we should re-engineer our logic for logs parsing. Right now it's pure python and regexes and it can't...

Thanks, @abhishek-plackal, we have plans to add the ability to choose the disk/volume for alerting.