npmpackage.info

Gathering detailed insights and metrics for @toolisticon/oc-routes-prometheus-exporter

@toolisticon/oc-routes-prometheus-exporter - 1.2.19 | npmpackage.info

@toolisticon/oc-routes-prometheus-exporter

Monitor OpenShift Routes in Prometheus

1.2.19

MIT

JavaScript

40.19 kB

4.5

Installations

npm install @toolisticon/oc-routes-prometheus-exporter

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

18.20.3

NPM Version

10.7.0 Pull Requests

Open

9

Total

450

Closed

80

Merged

361

Issues

Open

3

Total

8

Closed

5

Releases

1.2.19

v1.2.19

Updated on Jun 14, 2024

Version 1.2.18

v1.2.18

Updated on Jul 02, 2023

Version 1.2.17

v1.2.17

Updated on Jul 02, 2023

Version 1.2.16

v1.2.16

Updated on Apr 30, 2023

Version 1.2.15

v1.2.15

Updated on Apr 03, 2023

Version 1.2.14

v1.2.14

Updated on Feb 04, 2023

View All 34 releases

Languages

JavaScript

Dockerfile

Shell

JavaScript (63.91%)

Dockerfile (30.96%)

Shell (5.14%)

Developer

toolisticon

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

3 Stars

781 Commits

1 Forks

2 Watchers

12 Branches

1 Contributors

Updated on Jul 04, 2025

Maintainers

View All 1 Contributors

Package Meta Information

Latest Version

1.2.19

Package Id

@toolisticon/oc-routes-prometheus-exporter@1.2.19

Unpacked Size

40.19 kB

Size

14.02 kB

File Count

NPM Version

10.7.0

Node Version

18.20.3

Published on

Jun 14, 2024

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

cron openshift-rest-client @toolisticon/ssl-hostinfo-prometheus-exporter

Dev Dependencies

eslint jasmine nodemon eslint-plugin-n eslint-plugin-react eslint-plugin-import eslint-plugin-jasmine eslint-plugin-promise eslint-config-standard conventional-changelog-cli eslint-config-semistandard

Monitor OpenShift Routes in Prometheus

Usage

This nodejs application assumes that the container in which the application is running has already a valid OpenShift session. The entrypoint will try to autologin via a service account. So all you need is to create a image with the desired openschift installed:

FROM toolisticon/oc-routes-prometheus-exporter:latest

ENV SUMMARY="openshift-ssl-verify runtime image"
ENV DESCRIPTION="openshift-ssl-verify runtime"
ENV TZ="Europe/Berlin"
ENV OPENSHIFT_VERSION=3.10.0
ENV NVM_DIR="$HOME/.nvm"
ENV CONSOLE_LOG="true"
ENV LOG_LEVEL="INFO"

LABEL summary="$SUMMARY" \
      description="$DESCRIPTION" \
      io.k8s.description="$DESCRIPTION" \
      io.k8s.display-name="sslverify" \
      io.openshift.tags="security,sslverify,platform" \
      com.redhat.component="sslverify-container"

USER 0

# Update
RUN yum -y update && yum clean all && rm -rf /var/cache/yum

# Install oc and jq
RUN yum -y install centos-release-openshift-origin && \
    yum -y install origin-clients-${OPENSHIFT_VERSION} && \
    yum -y install epel-release && yum -y install jq

USER 1000

The pod should start with this output:

Now using node v8.15.0 (npm v6.4.1)
[2019-01-18T14:59:04.929Z] prometheus-exporter listening at 9000
[2019-01-18T15:00:00.005Z] Triggering check
[2019-01-18T15:00:00.006Z] Start reading route information.
[2019-01-18T15:00:05.133Z] Start triggering scan.

Sample Values

The metrics are available via via localhost:9000 on the pod:

security_ssl_mozilla_observatory{algorithm_version="2",end_time="1548079211000",grade="D",hidden="false",likelihood_indicator="MEDIUM",scan_id="9806703",score="35",start_time="1548079207000",state="FINISHED",status_code="404",tests_failed="3",tests_passed="9",tests_quantity="12",url="sample-config.sample.com",name="sample-config",namespace="project2",labels_app="myapp",labels_environment="dev",} 35.0
security_ssl_details{valid="true",valid_from="1545553135000",valid_to="1553329135000",days_remaining="60",url="api-test.sample.com",status="200",name="api-test",namespace="project1",labels_app="myapp",labels_environment="test",} 200.0
security_ssl_expire_days_remaining{url="api-test.sample.com",name="api-test",namespace="project1",labels_app="myapp",labels_environment="test",} 60.0

If you want to complete use

Configuration

You can override the config via environment variables:

   OPENSHIFT_MASTER_URL
   SERVER_PORT: // set desired port for prometheus endpoint, defaults to 9000
   CRON: // set cron pattern, default is '0 0 * * * *',
   LOG_LEVEL: // set log level, default is 'ERROR' ('INFO' outputs details info),
   CONSOLE_LOG: // set to true to omit logging to file, otherwise logs will be written to `logs` dir

You'll find a Grafana Dashboard here:

Troubleshooting

Access denied

If the service account does not have access to projects, you will see this message

Logged into "https://...:8443" as "system:serviceaccount:security:sslverify" using the token provided.

You don't have any projects. Contact your system administrator to request a project.
Welcome! See 'oc help' to get started.

SSL error

If you see this kind of error:

error: The server uses a certificate signed by unknown authority. You may need to use the --certificate-authority flag to provide the path to a certificate file for the certificate authority, or --insecure-skip-tls-verify to bypass the certificate check and use insecure connections.

you are using the internal kubernetes host which might be secured by self-signed certificates. Either use the public endpoint with proper ssl certificates or install the certificate to the keystore.

Development

Debug

To debug run the following command:

node --inspect-brk index.js

To debug unit tests:

npm run test:debug

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 0

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/build.yml/develop?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/build.yml/develop?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:33: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/build.yml/develop?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:44: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/build.yml/develop?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:45: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/build.yml/develop?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/build.yml:58: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/build.yml/develop?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/build.yml:79: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/build.yml/develop?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/codeql-analysis.yml/develop?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:46: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/codeql-analysis.yml/develop?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:57: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/codeql-analysis.yml/develop?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:71: update your workflow using https://app.stepsecurity.io/secureworkflow/toolisticon/oc-routes-prometheus-exporter/codeql-analysis.yml/develop?enable=pin
Warn: containerImage not pinned by hash: Dockerfile:1: pin your Docker image by updating registry.access.redhat.com/ubi8/ubi-init:latest to registry.access.redhat.com/ubi8/ubi-init:latest@sha256:e9cdaf857160a1ba1fecb788bcc8b784edafdf196d9094474d93542fbadec4ec
Warn: downloadThenRun not pinned by hash: Dockerfile:32-38
Warn: npmCommand not pinned by hash: Dockerfile:32-38
Info: 0 out of 9 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 2 third-party GitHubAction dependencies pinned
Info: 0 out of 1 npmCommand dependencies pinned
Info: 0 out of 1 containerImage dependencies pinned
Info: 0 out of 1 downloadThenRun dependencies pinned

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

4.5

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More