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

Renaming the exporter? What is your opinion? #113

Open
mrlhansen opened this issue Dec 19, 2024 · 5 comments
Open

Renaming the exporter? What is your opinion? #113

mrlhansen opened this issue Dec 19, 2024 · 5 comments

Comments

@mrlhansen
Copy link
Owner

This issue is for getting your feedback on potentially renaming the project.

There have been some requests for renaming the exporter, but I have been hesitant because it's impractical. Most notably, renaming the project will also mean renaming the Docker and Helm repository, which means that all installations using either will have the be migrated to the new repositories.

Even if I rename it, then there is the question of name. There are already several bmc and redfish exporters. I was thinking redfish_bmc_exporter which is unique from what I can see.

Yay or nay? Leave a comment below.

@mrlhansen mrlhansen pinned this issue Dec 19, 2024
@AlexG14
Copy link

AlexG14 commented Dec 19, 2024

Nay.
I can understand reasons behind this requests but consequences are a bit more than replacing a few symbols in a helm chart\docker compose file. You will lose all references (forums\mailing lists). Yes, you always can point to the new project and leave this one 'frozen' forever. Anyone can use any name for container so there is a very limited benefit from renaming.

@ilanni2460
Copy link

This issue is for getting your feedback on potentially renaming the project.

There have been some requests for renaming the exporter, but I have been hesitant because it's impractical. Most notably, renaming the project will also mean renaming the Docker and Helm repository, which means that all installations using either will have the be migrated to the new repositories.

Even if I rename it, then there is the question of name. There are already several bmc and redfish exporters. I was thinking redfish_bmc_exporter which is unique from what I can see.

Yay or nay? Leave a comment below.

I agree with your proposal. At first glance, IDRAC only supports Dell. In fact, it now supports data collection from many manufacturers.

@love6875520
Copy link

I think keep this name is better

@boxstep
Copy link

boxstep commented Jan 3, 2025

are there any plans to add more metrics? i get only about 100 returned, while other redfish_exporters return over 500. SNMP returns 2200+. Some metrics for various controller statuses are missing for example raid controller status

@mrlhansen
Copy link
Owner Author

@boxstep If there is a request for it and the metrics are useful in general, then yes. I am not adding every single ting that can possibly be exported as a metric. The goal is to have an exporter that exposes a uniform set of metrics for different systems. Your example with raid controller health could be added. If you want to discuss this further, please open a new issue.

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

No branches or pull requests

5 participants