We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
lsf_current_status index contains very old entries
have 2,146,965,961 documents in the lsf_current_status index, which is all the documents one shard can contain. When I query the data I see records in this index that date back 6 months. I believe their is some issue that requires fixing to as ent...
Add write_time timestamp column in Elastic Search for all LSF Explore Indexes
We believe it is vitally important to know when an entry was created in each index. This will tell us if their is delay in data being collected. It will let us know if we query for a full days data on day Y and see data from day X to know if our q...
To get pending slot information in LSF Explorer. There is information for running job slots, but not for pending job slots. This information was available in PA and is the accounting information. We have a number of existing reports that require P...
There is an index in LE, lsf_jobs_acct. When I tried to make chart in LE webGUI with lsf_jobs_active index, we found job status is a little bit strange. Even if job has end_time, its status is "RUN", as like following,"job_status" : "RUN","time_st...
The function that is related with decimal point number in LE customization chart.
In LE web GUI, there are some sample charts provided by IBM. Specially, in table chart, we can see decimal point number as like "xx.yy". But, If we tried to make customization chart and express some value as like run_time, its value is so long dec...
Unable to access array object of Explorer Data in ES
In Explorer Elasticsearch data, most of the indexes have used array objects. For example exec_host_list array in lsf_job_acct index and there are plenty of others indexes as well where array objects are used.
To add missing host level parameters in lsf_jobs_active and lsf_jobs_pending
Please add following execution host parameters in lsf_jobs_active and lsf_jobs_pend index Host_name, cpu_factor, host_type, host_model, host_group. These parameters are present in hostproperties.xml and hostgroup.xml loaders but these are not enab...
To include host level parameters in lsf_job_acct index
Currently the cpu_factor and cputime given in lsf_job_acct index is for a given job id. However if the job is executed on multi-hosts having different cpu factors, then it is not possible to calculate number of cores used x cputime per host x cpuf...
LSF Explorer flexusage data collection from remote (EU) data collector to (US)Explorer server signficantly lags
A data collection host in Europe takes more than 5 minutes to send data collected in past 5 minutes to ES located in US and cause data lagging. Expect to enhance the data transferring between continentals
Do not place IBM confidential, company confidential, or personal information into any field.