Git Product home page Git Product logo

sexiauditor's People

Contributors

vmdude avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

carbonbit

sexiauditor's Issues

Add global search feature

It could be cool to add some global search to be able to lookup for some value cross object (host, cluster, vm, vcenter, etc..)

Add Host inventory

We should add host inventory with specific host info (model, cpu type, etc...) to let people search in it as well

Does metrics shoud be stored in MariaDb ?

Or should we use some metrics centric database (graphite, ...).

Even with data deduplication on MariaDb entries, it can grow quite a lot because of metric update.

Categorize settings

We should add a setting category in order to display them by tab, like module selector.

As we add several option during dev, it became a little loaded ^^

Purge all related data on VC remove

After we remove vcenter from credential store, we should remove all data related in other tables, to avoid waiting for garbage collector to purge old entries

Limit time consuming module execution

For module that are quite time consuming (orphanFiles, ESXBundle, ...) we should prevent them for executing too often.

We should modify UI to prevent them for being selected more often that daily, and prevent the --force execution to run them

Add advanced settings compliance

We should add the possibility to define some advanced settings compliance (setting=value).

We could store these in a json file and let user update it through web page.

Then a module will check all ESX and present servers that does not comply with these settings (aka cross vcenter host profile)

Use of uninitialized value $HOSTNAME in scalar chomp at /opt/vcron/scheduler.pl line 3066.

Some people saw these errors:

Use of uninitialized value $HOSTNAME in scalar chomp at /opt/vcron/scheduler.pl             line 3066.
Use of uninitialized value $HOSTNAME in scalar chomp at /opt/vcron/scheduler.pl             line 3066.
Use of uninitialized value $HOSTNAME in scalar chomp at /opt/vcron/scheduler.pl             line 3066.
Use of uninitialized value $HOSTNAME in scalar chomp at /opt/vcron/scheduler.pl             line 3066.
Use of uninitialized value $HOSTNAME in scalar chomp at /opt/vcron/scheduler.pl             line 3066.

TTB better display on low build count

We should remove the time slider from TTB page if number of build is lower as ##

This cause an empty look alike graph with just few builds.
As user will have few build at the beginning, it can be strange at first sight

Follow-up on checks

This issue (should be sticky) will track follow-up on checks development

VSAN

vCenter

  • Session Age
  • License Report
  • Permission report
  • Terminate session
  • Certificate Report

Cluster

  • Configuration Issues
  • Admission Control
  • Cluster Without HA
  • Datastore Consistency
  • Members Version
  • Members Overcommit
  • Members LUN Path count mismatch
  • vCPU pCPU table
  • TPS savings
  • AutoSlotSize
  • Profile

Host

  • LUN Path Dead
  • Profile Compliance
  • LocalSwapDatastore Compliance
  • SSH/shell check
  • NTP Check
  • DNS Check
  • Syslog Check
  • configuration issues
  • Hardware Status
  • Reboot required
  • FQDN/hostname mismatch
  • Maintenance Mode
  • ballooning/zip/swap
  • PowerManagement Policy
  • Bundle backup

Datastore

  • Space report
  • Orphaned VM Files report
  • Overallocation
  • SIOC disabled
  • maintenance mode
  • Accessible

Network

  • DVS ports free
  • DVPG AutoExpand
  • DVS profile

Virtual Machine

  • Snapshots age
  • phantom snapshot
  • consolidation needed
  • cpu/ram/hdd reservation
  • cpu/ram/hdd limits
  • cpu/ram hot-add
  • VM Tools Pivot Table
  • vHardware Pivot Table
  • balloon/zip/swap
  • multiwriter mode
  • Non persistent mode
  • scsi bus sharing
  • VM Invalid Or Inaccessible
  • Inconsistent Folder
  • Removable Connected
  • GuestId mismatch
  • Powered Off
  • GuestID Pivot Table
  • Misnamed based on FQDN

Global

  • Inventory
  • Alarms
  • Mail Alert

Add hardware S/N

We should add query of hardware serial number for physical ESX hosts, to be able to search quickly on this field

Separate each module execution time

In Time To Build page, we should separate each module execution time to be able to sort the time consuming ones.

It will need to revise the executionTime table as it's only global at this point.

Import/Export feature

As seen with SexiGraf, we should by default have an export/import feature to allow easy migration process.

We will discuss about size limitation and if we have to add data in this export (or just configuration).

Add Compliance feature

It should be nice to be add compliance feature, that can be summarize by:

  • user define a set of settings that should be use as reference
  • compliance check each object and compare it to the settings defined by user
  • global score is computed based on settings mismatch

Main goal should be to provide dashboard with global compliance level

Add CDP information repo

It could be nice to add CDP information repo for ESX servers as well, useful if you need CDP information when vmnic is disconnected

Support multi-datastore VM

Right now, VM is linked to a datastore based on its configuration location.

If VM si split on multiple datastore (with multiple VMDK for instance), the datastore shown will only be the one hosting the VM configuration.

We should add support for VM hosted on multiple datastore (on inventory part mainly)

Add grouping feature

It could be nice to let user create logical group and add ESX to them.

With this feature, it will be possible to create SLA group, etc...

And these group will be used for capacity planning for instance (to avoid showing each ESX values, which is not very meaningful on a per-server view)

Add feature for report check

It seems odd to have License Report check with exclamation point for instance.

We should add the availability for "Report" check that are only informational, and not flagged as issue.
H1 Title color and glyphicon should be different as well to remove the "critical" state.

Add link to logo

We should add link to index page from logo, it seems... empty as-is

Should we run all checks and use module selector only for front-end?

By default, checks will be run (and so data will be retrieved) only if user enable it on the module selector.

When the user will enable some checks, data will not yet be retrieved (as it will be on the next scheduler run).
This can be misinterpreted if user visit a page between the activation of the check and the run of the scheduler, as all checks will be GREEN (aka no error as there is no data).

So we could choose to:

  • run all checks by default, and module selector will only be used for front-end render
  • find a way to separate the 'no error' from the 'no data' state
  • better inform user of this situation

Create abstract vcenter groups

This will let create global report based on this vcenter list (one report per list), in order to let user create some perimeter setting.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.