ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69286
|
Fri Jan 8 05:48:45 2021 |
| Alan Grant | agrant@winnipeg.ca | Question | Windows | 3.1.2 | Parsing log files | Sometimes we change the attributes in a config file for a given tab as time goes on, which naturally can get out of sync with the older data in that tab.
I can imagine some other Elog users have encounterd this too at some point so I'm wondering if there's a utilty or some way anyone knows of that I can use to parse a log file DIRECTLY to view the older data, without using the Elog GUI? |
69289
|
Fri Jan 8 15:28:06 2021 |
| Alan Grant | agrant@winnipeg.ca | Question | Linux | Windows | 3.1.2 | Re: Parsing log files |
John wrote: |
Hi Al; if I understand your situation correctly you want to access Elog db (logbooks) via another way. There are many ways depending on your knowledge, type of work needed, and ease of use. I have found that accessing whatever I need via Elog gui is satisfactory in many situations-- by simply exporting. THEN take the raw csv/xml file and manipulte it more easily from there. There are MANY free web sites that will take your data then, and put it in still another format that you choose (usually manipulating the rows/columns to your liking or doing mail-merge type work on your data). BTW WPS (Windows Office clone) is awesome at further 'mail-merg' techniques. THEN at that point you may have close to what you are trying to accomplish. I've also used PHP alot in this type of situation and have replicated Elog's data format for it's db (logbooks)..; so PHP is great in this maner, although of course it takes time to 'get-it-right' if you are not well versed in it. If you go into detail more of what type of format you want as the finalized product, maybe more suggestions will be made.
Happy belated New Years everyone,
John
Alan Grant wrote: |
Sometimes we change the attributes in a config file for a given tab as time goes on, which naturally can get out of sync with the older data in that tab.
I can imagine some other Elog users have encounterd this too at some point so I'm wondering if there's a utilty or some way anyone knows of that I can use to parse a log file DIRECTLY to view the older data, without using the Elog GUI?
|
|
Hi John. The problem with using the Find-->Export method is that some of the Attributes for the older data are no longer shown on that screen because the Config file has since changed. That's why I'm contemplating somehow parsing the log files directly instead. |
69386
|
Wed Jul 21 16:16:29 2021 |
| Alan Grant | agrant@winnipeg.ca | Question | Windows | 3.1.4 | Logging Main page entries, each with multiple ongoing events | Is there any way to log child events on the detail pages for a fixed number of entries on the main page? For example, I have 15 vehicles to enter on the main page, ID'd by Vehicle Number. Within each of those entries I will be logging ongoing repair service entries with certain attributes.
So how might I design this concept without having repeating vehicle entries on the main page for every service event, and preferably without splitting the information between two linked logbook tabs?
|
69389
|
Mon Aug 30 03:08:15 2021 |
| Alan Grant | agrant@winnipeg.ca | Question | Windows | 3.1.4 | Large log file size | Can the size of the application log file affect performance? |
69446
|
Tue Dec 14 19:16:57 2021 |
| Alan Grant | agrant@winnipeg.ca | Question | Windows | 3.1.4 | Log4j exploit | Is there any potential impact/concern with the Log4j exploit in Elog applications?
|
69536
|
Tue Jun 28 18:53:50 2022 |
| Alan Grant | agrant@winnipeg.ca | Question | Windows | 3.1.2 | Slow performance | We're up to 30 logbooks, 3.2GB data total and Elog damen has now become slow. Performance stats show 100%CPU on startup then reduces. Searches and general UI activity is slow. It runs on a VM with 4GB memory allocated. Up to 15 concurrent users.
Trimming and archiving some data files may help but I gather overall this is underpowered hardware in this instance so what is recommended system requirements for a config like this? |
65944
|
Fri Aug 8 00:44:26 2008 |
| dale cooper | agentdcooper@gmail.com | Question | All | 2.7.4x | 2 questions :: different colors in list view based on "type" + change verbage of "type" | hello all,
#1 i love ELOG : excellent app! i would like to ask/present a question here -- I have a couple of TYPE's defined as;
Options Type = Day Shift, Swing Shift, Night Shift
What I'd love to be able to do, is depending on what TYPE was selected during the creation of a NEW ENTRY in the ELOG "shift log" I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...
for example, if someone chose "Day Shift" that would be listed with a GREEN background, if someone chooses "Swing Shift" that gets a BLUE background, and so forth... I am wondering how one would go about implementing this?
second question... instead of listing the column named TYPE, can I just change it somewhere in the config to "SHIFT" so that in the list view, and even when in the NEW ENTRY form, I'd like it to show "Shift" instead of TYPE --- really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?
Thanks for the app, I look forward to any reponses! I been editing the CSS, and once done think I'll add it to yr Config Examples, as I don't see many CSS themes there...
-peace- |
65948
|
Mon Aug 11 06:56:56 2008 |
| dale cooper | agentdcooper@gmail.com | Question | All | 2.7.4x | Re: 2 questions :: different colors in list view based on "type" + change verbage of "type" | PERFECT, you answered my questions EXACTLY with what I am looking for! thanks soo much!
agentdcooper
Yoshio Imai wrote: |
dale cooper wrote: | I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected... |
You can achieve this by using a "style" directive for this attribute. E.g. if your attribute is called "Shift" and entries with value "Day" should be green, value "Swing" should be blue, you should addStyle Shift Day = background-color:green
Style Shift Swing = background-color:blue (and so on) to the config file.
Quote: | really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable? |
As long as I am not missing a key point in your problem, you should be able to define the names of your logbook attributes simply with the "Attribute" directive. So, if you want the users to enter the shift and the name of the shift leader, you would put a lineAttributes = Shift, Shift leader
Options Shift = Day, Swing, ... <and so on>
Options Shift leader = Mike, Edward, John, ... <and so on> and the logbook display should correctly show "Shift" and "Shift leader" in the header line of each entry ... |
|
|