Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • rc/rc-node_exporter
  • ravi89/rc-node_exporter
2 results
Show changes
Commits on Source (7)
Hide whitespace changes
Inline Side-by-side
.gitignore
View file @ eeaab58f
*.tar.gz *.tar.gz
tmp/ tmp/
sha256sums.txt sha256sums.txt
.history/
.vscode/
README.md
View file @ eeaab58f
# rc-node_exporter # rc-node_exporter
This currently supports Linux systems that use Systemd
The Ansible code will download the `node_exporter` release archive, extract and copy the `node_exporter` binary to `/usr/local/bin`, create the `node_exporter` system user, followed by setting up the Systemd unit file and starting it.
## Getting started The code doesn't currently do anything to open the `{{ node_exporter_port }}` on the host firewall.
To make it easy for you to get started with GitLab, here's a list of recommended next steps. ## Running the Code
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! - Run it on the local host
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```shel
ansible-playbook -c local -i 'localhost,' node_exporter.yml
``` ```
cd existing_repo
git remote add origin https://gitlab.rc.uab.edu/rc/rc-node_exporter.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitlab.rc.uab.edu/rc/rc-node_exporter/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name - Run it on the local host using a different port `9300` than the default `9100`
Choose a self-explaining name for your project.
## Description ```shell
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. ansible-playbook -c local -i 'localhost,' -e node_exporter_port=9300 node_exporter.yml
```
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
install-node_exporter.sh deleted 100755 → 0
View file @ 2725c733
#!/usr/bin/env bash
ver="1.6.1"
file="node_exporter-${ver}.linux-amd64.tar.gz"
sha256=sha256sums.txt
# cd to the script directory, in case the user has run it from another directory
sriptdir=$(cd "$(dirname "$0")" && pwd)
cd $sriptdir
if [[ ! -f $file ]]; then
echo "Downloading $file from Github"
curl -L https://github.com/prometheus/node_exporter/releases/download/v${ver}/${file} -o $file
fi
echo "Downloading the $sha256 checksum file"
curl -L https://github.com/prometheus/node_exporter/releases/download/v${ver}/$sha256 -o $sha256
if ! grep $file $sha256 | sha256sum -c -; then
echo "checksum failed for $file, exitting" >&2
exit 1
else
echo "Checksum of $file: OK"
fi
if [[ ! -d tmp/${file%.tar.gz} ]]; then
echo "Extracting $file to tmp/"
tar -zxf $file -C tmp/
fi
echo "Adding system user: node_exporter"
useradd -rs /bin/false node_exporter
echo "Copying node_exporter binary to /usr/local/bin"
systemctl is-active --quiet node_exporter.service && systemctl stop node_exporter.service
cp tmp/${file%.tar.gz}/node_exporter /usr/local/bin/
chown root:root /usr/local/bin/node_exporter
echo "Creating /etc/systemd/system/node_exporter.service file"
cp node_exporter.service /etc/systemd/system/
echo "Starting node_exporter.service"
systemctl daemon-reload
systemctl enable node_exporter.service
systemctl start node_exporter.service
## Host based firewall rules to allow incoming scrapes on `9100/tcp`
## from the Prometheus public IP
#echo "Creating firewalld rule to allow Prometheus server access to 9100/tcp"
#firewall-cmd --zone=public --permanent --add-rich-rule='rule family="ipv4" source address="172.20.0.99" port protocol="tcp" port="9100" accept'
#firewall-cmd --zone=public --add-rich-rule='rule family="ipv4" source address="172.20.0.99" port protocol="tcp" port="9100" accept'
node_exporter.service deleted 100644 → 0
View file @ 2725c733
[Unit]
Description=Node Exporter
After=network.target
[Service]
User=node_exporter
Group=node_exporter
Type=simple
ExecStart=/usr/local/bin/node_exporter --collector.filesystem.mount-points-exclude "^/(dev|proc|run/user/.+|run/credentials/.+|sys|var/lib/docker/.+)($|/)" --collector.filesystem.fs-types-exclude "^(autofs|binfmt_misc|bpf|cgroup|tmpfs|sunrpc|cgroup2?|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|iso9660|mqueue|nsfs|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|selinuxfs|squashfs|sysfs|tracefs)$"
[Install]
WantedBy=multi-user.target
node_exporter.service.j2 0 → 100644
View file @ eeaab58f
[Unit]
Description=Node Exporter
After=network.target
[Service]
User={{ node_exporter_user }}
Group={{ node_exporter_group }}
Type=simple
ExecStart=/usr/local/bin/node_exporter --web.listen-address=:{{ node_exporter_port }} --collector.filesystem.mount-points-exclude "^/(dev|proc|run/user/.+|run/credentials/.+|sys|var/lib/docker/.+)($|/)" --collector.filesystem.fs-types-exclude "^(autofs|binfmt_misc|bpf|cgroup|tmpfs|sunrpc|cgroup2?|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|iso9660|mqueue|nsfs|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|selinuxfs|squashfs|sysfs|tracefs)$"
[Install]
WantedBy=multi-user.target
node_exporter.yml 0 → 100644
View file @ eeaab58f
---
- name: Deploy node_exporter
hosts: all
become: true
vars:
node_exporter_user: node_exporter
node_exporter_group: node_exporter
node_exporter_port: 9100
org: prometheus
repo: node_exporter
version: 1.8.2
filename: node_exporter-{{ version }}.linux-amd64
project_url: https://github.com/{{ org }}/{{ repo }}/releases/download/v{{ version }}
tasks:
- name: Download {{ filename }}
ansible.builtin.get_url:
url: '{{ project_url }}/{{ filename }}.tar.gz'
dest: /tmp/{{ filename }}.tar.gz
mode: '0440'
tags:
- download
- name: Unarchive {{ filename }}
ansible.builtin.unarchive:
src: /tmp/{{ filename }}.tar.gz
dest: /tmp/
remote_src: true
tags:
- extract
- name: Create system group for user account {{ node_exporter_group }}
ansible.builtin.group:
name: "{{ node_exporter_group }}"
system: true
state: present
tags:
- configuration
- name: Create system user account {{ node_exporter_user }}
ansible.builtin.user:
name: "{{ node_exporter_user }}"
comment: Prometheus node_exporter system account
group: "{{ node_exporter_group }}"
system: true
home: /var/lib/node_exporter
create_home: false
shell: /sbin/nologin
state: present
tags:
- configuration
- name: Copy node_exporter binary to /usr/local/bin
ansible.builtin.copy:
src: /tmp/{{ filename }}/node_exporter
dest: /usr/local/bin/node_exporter
owner: root
group: root
mode: '0755'
remote_src: true
tags:
- configuration
- name: Copy systemd unit file
ansible.builtin.template:
src: node_exporter.service.j2
dest: /etc/systemd/system/node_exporter.service
owner: root
group: root
mode: '0644'
notify:
- Reload systemd unit files
- Restart node_exporter systemd service
tags:
- configuration
- name: Ensure systemd service is running
ansible.builtin.systemd_service:
name: node_exporter.service
state: started
enabled: true
tags:
- configuration
handlers:
- name: Reload systemd unit files
ansible.builtin.systemd:
daemon_reload: true
tags:
- configuration
- name: Restart node_exporter systemd service
ansible.builtin.systemd:
name: node_exporter.service
state: restarted
tags:
- configuration