Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: passenger-memory-stats: add option to disable apache/nginx checks #2306

Closed
64kramsystem opened this issue Sep 18, 2020 · 0 comments · Fixed by #2307
Closed

Comments

@64kramsystem
Copy link
Contributor

64kramsystem commented Sep 18, 2020

Issue report

This is a feature request, so I'm keeping the information minimal, as it's not related to any specific O/S or Passenger aspect.

Question 1: What is the problem?

The tool passenger-memory-stats always check for both Apache and Nginx status. Since it's unlikely (I suppose) that both are active at the same time, any invocation inevitably causes a warning to be printed, cluttering the output (and potentially, the exit status).

My request is to add option(s) to disable the checks. The behavior can be left as is by default, so the additional logic affects exclusively invocations that explicitly disable the checks.

I'm going to create a prototype/proposed PR over the next days, so this is for tracking and discussion.

@64kramsystem 64kramsystem changed the title Feature requres: passenger-memory-stats: add option to disable apache/nginx checks Feature requrest: passenger-memory-stats: add option to disable apache/nginx checks Sep 18, 2020
@64kramsystem 64kramsystem changed the title Feature requrest: passenger-memory-stats: add option to disable apache/nginx checks Feature request: passenger-memory-stats: add option to disable apache/nginx checks Sep 18, 2020
64kramsystem added a commit to 64kramsystem/passenger-dev that referenced this issue Sep 18, 2020
Allow skipping the Apache/Nginx sections of the passenger-memory-stats output, through the `--no-apache` and `--no-nginx` commandline options.

The output without any option specified is the same.

When specifying each of the two options, the section is entirely removed. This causes a difference in spacing between sections, as the Apache section doesn't have leading newlines, while the Nginx/Passenger ones do. Example:

```
$ passenger-mem-stats
Version: 6.0.2
Date   : 2020-09-18 12:17:42 +0200
[APACHE SECTION]

[NGINX SECTION]

[PASSENGER SECTION]
$ passenger-mem-stats --no-nginx
Version: 6.0.2
Date   : 2020-09-18 12:17:42 +0200

[NGINX SECTION]

[PASSENGER SECTION]
```

This is arguably a negligible difference. I originally looked into removing it, but it seems that the Table class introduces a leading newline (after the escape sequences) for Nginx/Passenger, while it doesn't do it for Apache, so I thought it's not really worth changing that.

Closes phusion#2306.
CamJN pushed a commit that referenced this issue Sep 21, 2020
Allow skipping the Apache/Nginx sections of the passenger-memory-stats output, through the `--no-apache` and `--no-nginx` commandline options.

The output without any option specified is the same.

When specifying each of the two options, the section is entirely removed. This causes a difference in spacing between sections, as the Apache section doesn't have leading newlines, while the Nginx/Passenger ones do. Example:

```
$ passenger-mem-stats
Version: 6.0.2
Date   : 2020-09-18 12:17:42 +0200
[APACHE SECTION]

[NGINX SECTION]

[PASSENGER SECTION]
$ passenger-mem-stats --no-nginx
Version: 6.0.2
Date   : 2020-09-18 12:17:42 +0200

[NGINX SECTION]

[PASSENGER SECTION]
```

This is arguably a negligible difference. I originally looked into removing it, but it seems that the Table class introduces a leading newline (after the escape sequences) for Nginx/Passenger, while it doesn't do it for Apache, so I thought it's not really worth changing that.

Closes #2306.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants