dexter/DBAdmin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

May 17, 2026, 11:40 PM

Browse Source
This commit is contained in:
Paweł Domański
2026-05-18 06:40:19 +00:00
commit 64944cf004
896 changed files with 310709 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
journals/2026-04-16.md
+45
View File
@@ -0,0 +1,45 @@
---
title: 2026-04-16 poniedziałek
type: DailyNote
tags: [daily, 2026]
---
No jestem ciekawy jak to wszystko zacznie działać i widzę, że chyba działa z tymi narzędziami co właśnie posiadam :) nie wiem jeszzcze jak z tego korzystać ale myślę, że będzie dobrze i zbuduje sobie graf wiedzy dla potrzeb baz danych i tylko tego .
# Propozycja Struktury Projektu DBAdmin (Korekta)
To jest **poprawiona wersja** struktury, uwzględniająca konieczność pozostawienia folderów `.vscode` i `.foam` w głównym katalogu projektu. Dziękuję za Twoją trafną uwagę.
```
DBAdmin/
├── .vscode/ # <--- Wymagany w głównym folderze dla ustawień VS Code
├── .foam/ # <--- Wymagany w głównym folderze dla działania Foam
│
├── 0_inbox/
├── 1_projects/
│ ├── 2024_Q1_Audyt_Bezpieczenstwa/
│ └── ...
├── 2_knowledge/
│ ├── postgresql/
│ ├── mariadb/
│ └── _general/
├── 3_procedures/
│ ├── postgresql/
│ └── ...
├── 4_snippets/
│ ├── postgresql/
│ └── ...
├── 5_archive/
│
└── _publishing/ # Folder na zasoby do publikacji (np. obrazki, layouty)
├── assets/
├── attachments/
└── _layouts/
```
### Kluczowe założenia (poprawione):
1. **`.vscode` i `.foam`**: Pozostają w głównym katalogu, aby zapewnić poprawne działanie edytora i rozszerzenia Foam.
2. **`1_projects`**: Służy do zarządzania bieżącą pracą i oddziela ją od bazy wiedzy.
3. **Podział na technologie**: Umożliwia szybkie odnajdywanie zasobów (wiedzy, procedur, skryptów) dla konkretnego systemu.
4. **`_publishing`**: Grupuje zasoby niezwiązane bezpośrednio z treścią merytoryczną, a raczej z jej ewentualną publikacją lub wyglądem.
journals/2026-04-22.md
+227
View File
@@ -0,0 +1,227 @@
---
title: 2026-04-22 środa
type: DailyNote
tags: [daily, 2026]
---
MIM Bridge Details
- INC #: INC0798812
- Short Description: Piccard Database - Degraded Performance - Switzerland
- Priority: P3
- Major Incident Accepted: Yes
- Impact Start Time: TBD
- Incident Resolution Time:
- SNOW SOW Link: https://dnbgatewayprod.service-now.com/now/sow/record/incident/b845b8db2f908750be82f34fafa4e36c/params/selected-tab-index/3/selected-tab/id%3Dcllanqdxq01av3b7srbf5i3t3%5Eroute%3Dmim-details
ECC2API named the meeting ECC P3 - INC0798812 - Piccard Database - Degraded Performance - Switzerland.
9:23 AM Meeting started
Facilitator has been turned on and is taking notes. How can you help us?
MIM Bridge Details
- INC #: INC0798812
- Short Description: Piccard Database - Degraded Performance - Switzerland
- Priority: P3
- Major Incident Accepted: Yes
- Impact Start Time: 4/21/2026 19:35 EST
- Incident Resolution Time: 4/22/2026 10:05 AM CET / 4:05 AM EST
- SNOW SOW Link: https://dnbgatewayprod.service-now.com/now/sow/record/incident/b845b8db2f908750be82f34fafa4e36c/params/selected-tab-index/3/selected-tab/id%3Dcllanqdxq01av3b7srbf5i3t3%5Eroute%3Dmim-details
Prod
08:50 disk space was added
Tentative issue start time 4/21/2026 19:35 EST
first warning SLANK: 0:45, issue started: 1:30, slank notification: 1:35, escalated to DBA team: 6:23, resolved: 8:50-8:55
I have another meeting and am leaving this one. Unfortunately, I can't offer much support here.
Best regards, Géraldine
Sure, thank you Ricci-Rubera, Geraldine
bisclxpbisjb01.bisnodech.local
1. Issue overview:
Primary issue: Piccard application database experienced disk space exhaustion, leading to database locking sessions and severe performance degradation.
The database ran out of disk space, preventing normal operations and causing application slowdowns and blockages.
Although additional disk space was subsequently added, residual locking sessions in the database continued to impact performance.
These locking sessions were identified as Hibernate sessions not closing correctly at the application layer, requiring application-level intervention.
2. Timeline (as discussed / confirmed)
~00:45 CET – First disk space warning received (20% remaining).
~01:30–01:35 CET – Disk became full; Splunk alert at ~01:35 CET confirmed 100% disk usage.
~06:23 CET – Issue escalated to DBA team.
08:50 CET – Additional disk space (~50 GB) added to the database (confirmed multiple times by Paweł/Adrian, also reflected in meeting chat).
Post disk extension: Database became accessible again, but locking sessions persisted, causing degraded performance.
(Exact issue start time for business impact aligned tentatively to 21 Apr 2026 ~19:35 EST, per meeting chat.)
3. Customer / Business Impact
Switzerland business users heavily impacted; Piccard is widely used by most Swiss business units.
Key impacts reported:
Users could log in, but:
Navigation extremely slow.
Every click took significant time.
Saving changes mostly hung indefinitely (loading cursor, no completion).
Debt reports and Trade Register notifications could not be loaded earlier in the day.
Import / shop jobs were not functioning during the incident window.
User confirmation (Daniela Pispico):
Application technically accessible.
Performance “very, very slow”.
Not usable for productive work.
Business users confirmed they were still blocked operationally despite disk extension.
4. Current Technical State (at time of discussion)
✅ Disk space issue mitigated temporarily by adding capacity.
❌ Database still affected by:
Blocking sessions.
Long‑running Hibernate sessions not closing.
❌ Application performance remains degraded.
⚠️ Working copy replication not running and intentionally deferred to avoid further business impact during working hours.
Risk identified:
Disk space growth has been persistently high (>80%) for some time, not a one‑off condition.
Sudden growth may also be linked to logs, dumps, or background processes, but no final RCA yet.
5. Key Technical Discussions / Decisions
Restart of Tomcat process identified as the next critical remediation step:
Purpose: Clear blocking sessions and stuck Hibernate connections.
Clarified explicitly that this is a Tomcat process restart, not a full server reboot.
Confirmed:
Restart should not negatively impact other applications.
Not all Piccard-related services are isolated, but risk is acceptable and understood.
Linux / AO Engineering involvement required to:
Prepare change.
Execute controlled Tomcat restart.
Database replication:
Acknowledged as necessary.
Agreed to postpone replication until end of business day to avoid further load and risk during peak usage.
Disk space must be closely monitored before replication is resumed.
6. Actions Being Taken (with ownership)
Immediate / In Progress
Add disk space to stabilize database
✅ Completed at ~08:50 CET.
Owner: Paweł (DBA)
Prepare and execute Tomcat process restart
To clear blocking and Hibernate sessions.
Owners:
Martin Woerner – identify affected Tomcat instance(s).
Oleksandr Lozinskyi / AO Linux team – prepare change and restart.
Status: Pending / being prepared during the meeting.
Validate application behaviour post‑restart
Confirm:
Navigation speed.
Ability to save changes.
Job execution.
Owners:
Business users (Daniela / Alessandro / DNO team).
IT Dev Switzerland.
Near‑Term / Planned
Resume database replication
Planned post business hours (around end of day).
Condition: Ensure sufficient disk space and stability.
Owners: DBA + IT Dev Switzerland
Monitor disk usage closely
During the rest of the day and overnight while replication/jobs run.
Owners: DBA / Engineering
Follow‑up / Preventive
Disk space monitoring and alerting review
Discussion raised that:
Disk‑full incidents are preventable and unacceptable operationally.
Proposal to raise incidents or bridges when disk reaches 98–99% usage.
To be taken offline as a post‑incident / peer review action.
Owners: Engineering / DBA leadership (to be defined)
7. Open Points / Risks
Root cause of:
Rapid disk consumption.
Long‑standing high utilization trend.
Need confirmation whether:
Logs, dumps, backups, or specific jobs caused the sudden growth.
Risk of disk filling up again once replication and jobs restart if not addressed structurally.
8. Overall Status (at meeting point)
Incident not yet resolved.
Service is in a degraded, partially usable state.
Restoration path agreed:
Clear blocking via Tomcat restart.
Validate performance with business.
Resume replication safely.
ECC bridge to remain active until performance and usability are confirmed restored.
CHG0136776
I’ll add this incident to the master problem we have open already
[olelozloc@bisclxpbisjb01 ~]$ date && sudo systemctl status tomcat.service
Wed Apr 22 10:04:21 CEST 2026
● tomcat.service - Apache Tomcat Web Application
Loaded: loaded (/etc/systemd/system/tomcat.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2026-04-21 15:13:25 CEST; 18h ago
Process: 11443 ExecStop=/usr/share/tomcat/bin/shutdown.sh (code=exited, status=0/SUCCESS)
Process: 11526 ExecStart=/usr/share/tomcat/bin/startup.sh (code=exited, status=0/SUCCESS)
Main PID: 11539 (java)
CGroup: /system.slice/tomcat.service
└─11539 /usr/bin/java -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache....
Apr 21 15:13:25 bisclxpbisjb01.bisnodech.local systemd[1]: Starting Apache Tomcat Web Application...
Apr 21 15:13:25 bisclxpbisjb01.bisnodech.local systemd[1]: Started Apache Tomcat Web Application.
[olelozloc@bisclxpbisjb01 ~]$ date && sudo systemctl restart tomcat.service
Wed Apr 22 10:04:55 CEST 2026
[olelozloc@bisclxpbisjb01 ~]$ date && sudo systemctl status tomcat.service
Wed Apr 22 10:05:04 CEST 2026
● tomcat.service - Apache Tomcat Web Application
Loaded: loaded (/etc/systemd/system/tomcat.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2026-04-22 10:05:01 CEST; 3s ago
Process: 18088 ExecStop=/usr/share/tomcat/bin/shutdown.sh (code=exited, status=0/SUCCESS)
Process: 18201 ExecStart=/usr/share/tomcat/bin/startup.sh (code=exited, status=0/SUCCESS)
Main PID: 18218 (java)
CGroup: /system.slice/tomcat.service
└─18218 /usr/bin/java -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.Class...
Apr 22 10:05:01 bisclxpbisjb01.bisnodech.local systemd[1]: Starting Apache Tomcat Web Application...
Apr 22 10:05:01 bisclxpbisjb01.bisnodech.local startup.sh[18201]: Existing PID file found during start.
Apr 22 10:05:01 bisclxpbisjb01.bisnodech.local startup.sh[18201]: Removing/clearing stale PID file.
Apr 22 10:05:01 bisclxpbisjb01.bisnodech.local systemd[1]: Started Apache Tomcat Web Application.
[olelozloc@bisclxpbisjb01 ~]$
Apr 21 15:13:25 bisclxpbisjb01.bisnodech.local systemd[1]: Started Apache Tomcat Web Application.
[olelozloc@bisclxpbisjb01 ~]$
Tomcat restart completed
no locks on database side
Tentative restoration time 4/22/2026 10:05 AM CET / 4:05 AM EST
Audit database: normal state - no locks, 25 connection from 'Collecting_Services'
Audit database: RED state: 6-7 locks, ~70 connection from 'Collecting_Services'
Yesterday we had restart of tomcat service on same server but related to another incident INC0798444, used change CHG0136652
INC0798320 -> Piccard Score is not working; we cannot perform the outsourcing (the same as yesterday). Please fix this as soon as possible and let us know. Thank you. related issue INC0798444
INC0797772 INC0797647 INC0798267 INC0797415 INC0797747 INC0797757 INC0797445 INC0797682 INC0797490- > (Splunk Observability) Disk = 100% [H:\] chsqlbkstoprw01.bisnodech.local - system backupowy się zapchał i przenoszę dane do S3 na OVH
Wczorajsze INC0798360 INC0798393-> (Splunk Observability) Disk > 90% [I:\] CHPICBUDB0NPW02 przeniosłem dane
INC0795723 INC0797683 INC0797760 INC0797672 INC0797760 INC0797696 INC0797768 INC0796110 -> (Splunk Observability) Disk > 90% [M:] CHPICBUDB0NPW01 - nie było konieczności powiększyłem dysk o 50 ponieważ nie mogłem odtworzyć bazy piccard
INC0798188 INC0798497 INC0797671 INC0798216-> (Splunk Observability) Disk > 90% [P:] CHPICBUDB0PRW01 - wykonałem shrink logu dla bazy Sync na piccard
INC0798748 INC0798753- (Splunk Observability) Disk > 80% [J:] CHPICBUDB0PRW01 - nie potrzeba nic robić bo to tempdb
INC0797669 -> (Splunk Observability) Disk = 100% [P:] CHPICBUDB0PRW01 - shrink databaze
INC0798753 - > (Splunk Observability) Disk = 100% [J:] CHPICBUDB0PRW01- disk resized but waiting for enable replication
SCTASK0724812 -> Enable Sync and feed job
Today tasks
SCTASK0722293 -> Fulfillment task for Request Database Support - nie mam dostępu do bazy danych i musiałem odtworzyć z ostatniego backupu jaki mam, ale
16370274
16370274
11516947
10124205
7985051
6556451
4771397
3613868
2977527
2387681
1543699
862179
journals/2026-04-23.md
+23
View File
@@ -0,0 +1,23 @@
---
title: 2026-04-23 środa
type: DailyNote
tags: [daily, 2026]
---
# Zamykanie incydentów
INC0798834 - Piccard database no longer working because it ran out of disk space. Also looks like transaction log of Piccard_Business database is full - było to spowodowane tym, że nie była włączona repkikacja w bazie piccard i zabrakło miejsca na logi, Łukasz mi pomógł i na czas rozwiązywania problenmów rozwiązaliśmy ten problem, wie=czorem wczoraj włączyłem replikacje i wszystko się wykręciło, dzisiaj nawet nie ma blokujących się sesji.
RITM0466075 -> zadanie z wczoraj na nadgodziny od 18:00 -> 21:00 Please reenable replicaton from Piccard_Business to working copy - włączyłem repkikację i monitorowałem co się dzieje, wszystko się uruchomiło prawidłowo
Dopisać do kalendarza
cały dzień CTASK0120940 -> Backup DB on CHDOCUWAPPPRW01.bisnodech.local
- TODO Dodatkowo sprawdzić czy mam tam dostęp
Do spotkania
Od Wieczorka
CHG0132442 -> tam jest uruchomienie skryptów na bazie i nie wiem czy tego nie powinien robić SUndaram
CHG0132414 -> przypsiany tam jest tylko backup
mam wrażenie że chcą żebyśmy wykonywali takie rzeczy sami :(
journals/2026-04-26.md
+9
View File
@@ -0,0 +1,9 @@
---
title: 2026-04-28 piątek
type: DailyNote
tags: [daily, 2026]
---
SCTASK0724456 -> General Database Request - CHPICBUDB0NPW02 - restore database piccard test
SCTASK0729448 General Database Request - PICCARD UI (CH) Hi Team, Business ID 1'345'196 need to be deleted on Piccard UI so we can reopen it properly from Business POV. The record is currently not usable. Thanks & regards -> nie manipulujemy danymi
SCTASK0692608 - General Database Request - CHPICBUDB0PRW01 Please run the attached query to insert the records into prod CHPICBUDB0PRW01 Piccard_business.dbo.business_business_operational_status
journals/2026-04-27.md
+12
View File
@@ -0,0 +1,12 @@
---
title: 2026-04-27 piątek
type: DailyNote
tags: [daily, 2026]
---
SCTASK0724394 - Database Access
SCTASK0692608 - General Database Request - CHPICBUDB0PRW01 -> wydaje mi się że to zadanie dla aplikacyjnego i w dodatku wydaje mi się na zmianę ponieważ to jest data manipulation
INC0800045 - (Splunk Observability) Disk > 80% [/var/log] chmybccdb0npl01.blue.bisnode.net -> przepisałem ponieważ jest to log systemowy
INC0797362 - (Splunk Observability) Disk > 80% [/var/log] chmybccdb0npl01.blue.bisnode.net -> przepisałem ponieważ jest to log systemowy
INC0798855 (Splunk Observability) Disk > 90% [J:] CHPICBUDB0PRW01
INC0800504 P4 On Hold (Splunk Observability) Disk = 100% [I:] CHWORK0DB0PRW01 -> to baza tmpdb i jest pusta na razie nie ma konieczności podejmowania akcji
journals/2026-04-30.md
+17
View File
@@ -0,0 +1,17 @@
---
title: 2026-04-30
type: DailyNote
tags: [daily, 2026]
---
Zamykam incydenty dowtytychasowe na CH Working copy -> dysk powiekszony
Instaluje skrypty dla Roderick -> zainstalowałem wszystko co jest potrzebne
Do sprawdzenia
euniappbakprl01.orange.bisnode.net
Oracle databases
product.bisnode.cz
public.bisnode.cz
journals/2026-05-05.md
+15
View File
@@ -0,0 +1,15 @@
---
type: DailyNote
Status: Active
---
# Dziennik 5 maja 2026 roku
Linki do ogarnięcia
[paulomac1000/ipbox-wizard-ai: Algorytm IP Box — Wizard AI dla programistów B2B](https://github.com/paulomac1000/ipbox-wizard-ai?utm_source=unknownews)
***
[Untitled](https://www.linkedin.com/feed/update/urn:li:groupPost:3063585-7457165830531997697?utm_source=social_share_video_v2\&utm_medium=android_app\&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw\&utm_campaign=whatsapp)[Untitled - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/20793880-1cbe-4e2b-9484-eb6a3ff923f0)
[Newsletter o AI – darmowy newsletter AI dla początkujących | AI z głową](https://aizglowa.pl/?utm_medium=paid\&utm_source=ig\&utm_id=52545871220324\&utm_content=52545919328324\&utm_term=52545871220124\&utm_campaign=52545871220324\&fbclid=PAdGRzdgRmXvNleHRuA2FlbQEwAGFkaWQAAC_M0217tHNydGMGYXBwX2lkDzU2NzA2NzM0MzM1MjQyNwABp0j4mdNMknSBI-M381dMoRNvtJ1-q7aZK7XAP4hRkHLFQXXlJSyL33WVFixr_aem_kfXUR4cYRxDgRR1Uet5eog)[Newsletter o AI – darmowy newsletter AI dla początkujących | AI z głową - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/b3a9703a-a39f-438b-a183-944e05bfaf30)
journals/2026-05-06.md
+794
View File
@@ -0,0 +1,794 @@
---
title: 2026-05-06
type: DailyNote
tags: [
- daily,
- 2026]
---
10:47
[#aicourse #aicheatsheet #aieducation #aicommunity | GenAI Works | 15 comments](https://www.linkedin.com/posts/genai-works_aicourse-aicheatsheet-aieducation-activity-7456957037852413953-Vpt2?utm_source=social_share_video_v2&utm_medium=android_app&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw&utm_campaign=whatsapp)[#aicourse #aicheatsheet #aieducation #aicommunity | GenAI Works | 15 comments - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/55111f3e-c4fa-4a37-b168-0fc57a09ddb8)
---
type: 'DailyNote'
title: May 2, 2026
date: '2026-05-02T00:00:00.000Z'
tags: []
---
15:25
[Most people are using 10% of Claude.That&#39;s like buying a Ferrari and only ever using it in a parking lot.Here&#39;s how to unlock the other 90% ...](https://www.linkedin.com/posts/gabriel-millien_most-people-are-using-10-of-claude-thats-activity-7449886699339300866-zQWA?utm_source=social_share_video_v2&utm_medium=android_app&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw&utm_campaign=whatsapp)[Most people are using 10% of Claude.That&#39;s like buying a Ferrari and only ever using it in a parking lot.Here&#39;s how to unlock the other 90% ... - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/7cf6b08c-42d5-4677-9a58-ec9b18da4172)
17:37
[Log in | Insy](https://insy.io/login?return_to=%2Fcreate&utm_source=ig&utm_medium=social&utm_content=link_in_bio&fbclid=PAdGRzdgRi-XRleHRuA2FlbQIxMQBzcnRjBmFwcF9pZA81NjcwNjczNDMzNTI0MjcAAaflfewQuR5ycmozf2VOm6Sq_i4oToFPHf9NFVJitLBFMLWtrotYXyDgFxN96g_aem_6gEN6fYbqWlRY_s9mTBazg)[Log in | Insy - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/f91e657e-2c60-4b11-9af4-4d680b7b2e4a)
---
type: 'DailyNote'
title: April 18, 2026
date: '2026-04-18T00:00:00.000Z'
tags: []
---
12:43
[#claudeskills #claudecourse #claudecheatsheet #aicommunity | GenAI Works | 33 comments](https://www.linkedin.com/posts/genai-works_claudeskills-claudecourse-claudecheatsheet-activity-7450796452496302080-XzEk?utm_source=share&utm_medium=member_android&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw)[#claudeskills #claudecourse #claudecheatsheet #aicommunity | GenAI Works | 33 comments - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/50c95d47-a62b-4c84-ac26-78b7a8c5f5af)
---
type: 'DailyNote'
title: April 17, 2026
date: '2026-04-17T00:00:00.000Z'
tags: []
---
13:02
[The Rapid Ascension Sytem](https://rapidascension.freeclientsystem.com/?utm_source=fb_paid_freeclientsystem&utm_medium=04%2F04%20%20I%20C28%20I%20A01%20I%20Tier%201%20I%2018-65%2BI%20M%2BF%20I%20BROAD&utm_campaign=C28%20I%20A01%20I%20IMG10&utm_id=120242858801740374&utm_content=120243976479740374&utm_term=120243976225730374&fbclid=PAdGRzdgRO8oFleHRuA2FlbQEwAGFkaWQBqzFCc_Te9nNydGMGYXBwX2lkDzU2NzA2NzM0MzM1MjQyNwABpwVue4fy4sqOScO0Iq5GkY48clG3yIYBTE0k8SQ1QFxPlyktCoOcjbDF3Vr__aem_iabSoPzbSimw60GPoL-5eQ)[The Rapid Ascension Sytem - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/48b2cc16-f8f8-49b8-abae-b20ec64ef613)
---
type: 'DailyNote'
title: April 16, 2026
date: '2026-04-16T00:00:00.000Z'
tags: []
---
07:37
[Most companies think they have an AI strategyThey have a tools list And in AI-powered digital marketing (2026), this confusion is where ROI disappear...](https://www.linkedin.com/posts/sangulati_most-companies-think-they-have-an-ai-strategy-activity-7450090595928346625-O9Ho?utm_source=social_share_video_v2&utm_medium=android_app&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw&utm_campaign=whatsapp)[Most companies think they have an AI strategyThey have a tools list And in AI-powered digital marketing (2026), this confusion is where ROI disappear... - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/cc7a5ba6-906f-4c58-81d4-f49db148dd57)
---
type: 'DailyNote'
title: April 15, 2026
date: '2026-04-15T00:00:00.000Z'
tags: []
---
15:17
[Stop using Claude just like an AI chatbot. Most people are using only 10% of what it can actually do. The real power of Claude starts when you underst...](https://www.linkedin.com/posts/maria-gharib-091779b9_stop-using-claude-just-like-an-ai-chatbot-activity-7449833883417772032-10pw?utm_source=social_share_video_v2&utm_medium=android_app&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw&utm_campaign=whatsapp)[Stop using Claude just like an AI chatbot. Most people are using only 10% of what it can actually do. The real power of Claude starts when you underst... - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/4ffdf47c-6901-4bd6-be40-4ca5a5e6f936)
15:17
[4 habits that make Claude Code more reliable in practice: 1---- Don’t turn CLAUDE. md into a giant instruction dump Use it for stable things: project ...](https://www.linkedin.com/posts/alexwang2911_4-habits-that-make-claude-code-more-reliable-activity-7450108988169576449-Cx8i?utm_source=social_share_video_v2&utm_medium=android_app&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw&utm_campaign=whatsapp)[4 habits that make Claude Code more reliable in practice: 1---- Don’t turn CLAUDE. md into a giant instruction dump Use it for stable things: project ... - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/4d7963ec-0d3d-4a44-adce-12e35e83d5c8)
15:20
[text | Rushikesh Meharwade posted on the topic | LinkedIn](https://www.linkedin.com/posts/rushikesh-meharwade-2807b842_%F0%9D%90%96%F0%9D%90%A1%F0%9D%90%B2-%F0%9D%90%8C%F0%9D%90%A8%F0%9D%90%AC%F0%9D%90%AD-%F0%9D%90%8F%F0%9D%90%9E%F0%9D%90%A8%F0%9D%90%A9%F0%9D%90%A5%F0%9D%90%9E-%F0%9D%90%85%F0%9D%90%9A%F0%9D%90%A2%F0%9D%90%A5-%F0%9D%90%9A%F0%9D%90%AD-activity-7448672839291002880-PjIv?utm_source=social_share_video_v2&utm_medium=android_app&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw&utm_campaign=whatsapp)[text | Rushikesh Meharwade posted on the topic | LinkedIn - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/16ba92bc-2e1c-47cb-bb86-d7f2c25004c8)
15:29
[10 Ways to Improve AI Responses with Better Prompt Design | GenAI Works posted on the topic | LinkedIn](https://www.linkedin.com/posts/genai-works_youve-probably-asked-claude-something-and-activity-7446447788592177152-8gWX?utm_source=social_share_video_v2&utm_medium=android_app&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw&utm_campaign=whatsapp)[10 Ways to Improve AI Responses with Better Prompt Design | GenAI Works posted on the topic | LinkedIn - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/a8452757-a117-4ffb-b57b-c53cb5a32672)
---
type: 'DailyNote'
title: April 14, 2026
date: '2026-04-14T00:00:00.000Z'
tags: []
---
21:14
[Instagram](https://www.instagram.com/reel/DWOaR3GiXcd/?igsh=MXAxb2RpcmVvd3hqOA==)[Instagram - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/d954f0d9-1674-413d-9f7d-0032c6deea3d)
---
type: 'DailyNote'
title: April 12, 2026
date: '2026-04-12T00:00:00.000Z'
tags: []
---
21:06
[Email Storyselling Playbook](https://emailstoryselling.ai/tools/playbook?utm_medium=cpc&utm_source=facebook&utm_campaign=ESS%20Playbook%20-%20Purchase%20-%20Testing&utm_content=Playbook%20Product%20Shot%20-%20Controversial&utm_term=Stripe%20-%20Worldwide&ad_id=120241419279890173&adset_id=120241419166270173&utm_id=120241344871540173&fbclid=PAdGRzdgRIzGtleHRuA2FlbQEwAGFkaWQBqy7wM1UxzXNydGMGYXBwX2lkDzU2NzA2NzM0MzM1MjQyNwABp04xR0Tvu3Q3Nl18W5hbhOK4WoE2Y3yzo4Jpk5gGasYffEjCPkcWdupyPPEI_aem_6tmlOSX8aR81MCEA_YdYtA)[Email Storyselling Playbook - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/ddc9f41d-453e-46a4-a1de-ea4607e302fa)
---
type: 'DailyNote'
title: April 6, 2026
date: '2026-04-06T00:00:00.000Z'
tags: []
---
16:19
[Zbuduj swoją stronę www w 1 godzinę!](https://cart.easy.tools/checkout/heartmade/zbuduj-swoja-strone-www-w-1-godzine?utm_medium=paid&utm_source=ig&utm_id=120249938373160777&utm_content=120249938374190777&utm_term=120249938373300777&utm_campaign=120249938373160777&fbclid=PAdGRzdgRAoCxleHRuA2FlbQEwAGFkaWQBqzaukMaMuXNydGMGYXBwX2lkDzU2NzA2NzM0MzM1MjQyNwABp_oPEzvZcJ7DNC2LK2XjA0E_oBZb4ZnSgV1u50uqw8JPYkcHk2A9OvXyHY2N_aem_DJ09ZgQyvtZy5tvOhD5wIg)[Zbuduj swoją stronę www w 1 godzinę! - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/0d4fee1b-1aa4-4e20-98d7-fb896b3e23c4)
16:21
[Hackuj swoją produktywność z AI](https://cart.easy.tools/checkout/10122947/hackuj-produktywnosc?utm_source=6793538121190&utm_content=video+4+-+screencast&utm_medium=paid&utm_id=6793538121190&utm_term=6844597498190&utm_campaign=6793538121190&fbclid=PAdGRzdgRAoLhleHRuA2FlbQEwAGFkaWQAAAZKCyceRnNydGMGYXBwX2lkDzU2NzA2NzM0MzM1MjQyNwABp6JHx9_Ws2YNcLZvwDRU3E3TprfotVIQ4zC5GZfoRUO4QKxKHlFh2L1bDhEA_aem_H7-DnuXjlLKQqDHRLlRLXQ)[Hackuj swoją produktywność z AI - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/489239d3-89a6-4d9d-88f8-e556afa0c54b)
---
type: 'DailyNote'
title: April 3, 2026
date: '2026-04-03T00:00:00.000Z'
tags: []
---
INC0791071 - Backup of production databaseMessageExecuted as user: BISNODECH\picdbsrv01. ...: 50% complete End Progress Progress: 2026-04-01 03:06:40.13 Source: Back Up Database Task Executing query "declare @backupSetId as int select @backupS
- Everything is fine. Backup complete
INC0789632 - (Zabbix) chsqlbkstoprw01.bisnodech.local:Windows EUROPE/SWITZERLAND:
- zapchał się backup gdzie są wykonywane backupy tygodniowe, odetkałem to i teraz muszę zrobić z tego jakąś automatyzację
- Disk cleaned by move database backup to the archive storage.
RITM0452584 - General Backup Request - CHPICBUDB0NPW01 -> restore bazy Piccard
Restore Piccard_Business backup from Prod (Guido already had a backup from CHPICBUDB0PRW01.bisnodech.local available) in test 10.146.11.71 (chpicbudb0npw01.bisnodech.local).
New restore requested for DEV load test of business_industry_code (see also CHG0131971)
RITM0436607 - General Database Request - SEBART0DB0PRW01 -> zamknięry
Create WINDOWS Cluster on SEBART0DB0PRW01.orange.bisnode.net and SEBART0DB0PRW01.orange.bisnode.net 
which will be needed to create SQL Server Always On. Installation is required before moving the BART system to a production environment.
This is according RITM0417111 and RITM0417112
RITM0436709 - General Database Request - EUUIPORDB0PRW01 -> czekam na Łukasza żeby zrobił backup wpisać jaki to CR
INC0791031 - The tables in database UserObjects are not loading in Microsoft SQL Server Management Studio on server CHWORK0DB0PRW01.bisnodech.local (10.41.70.205). This prevents me from working, as my tasks require access to these database tables
- raczej to nie probem z samym serwerem ale z ManagementStudio któe trzeba zrestartować, napisałem do użytkownika żeby to zrobił
RITM0454017 - General Database Request - CHWORK0DB0PRW01 -> Trigger sync of Piccard Working Copy, to get latest trade entries and exclude deleted invoices on PROD
- coś Guido robił ale nie mam zielonego pojęcia co to jest, szukam po skryptach i może to być SIIS
Forwarded to WIN - INC0791500 - (Splunk Observability) Critical Alert: Filesystem 100% [Y:] EUUIPORDB0PRW01.bisn
This disk is to small to perform backup and keep last database backup. Please resize to 100 GB
DONE RITM0455493 -> Database Access Piccard
INC0789624 P5 Resolved (Zabbix) chsqlbkstoprw01.bisnodech.local:Windows EUROPE/SWITZERLAND: Problem: We
03/29/2026 08:39:27
splunk_integration At least one alert has occurred for AARO...
INC0789632 P4 Resolved (Zabbix) chsqlbkstoprw01.bisnodech.local:Windows EUROPE/SWITZERLAND: Problem: We
03/29/2026 08:22:30
splunk_integration At least one alert has occurred for AARO...
INC0791011 P2 In Progress Our Piccard Working copy database can not be synced, which prevents Trade Team of finalizing critical analysis and data deliveries to customers, which should not be performed on PROD
04/01/2026 10:58:00
grgica Please describe your issue below :
Our P...
INC0791031 P3 Resolved The tables in database UserObjects are not loading in Microsoft SQL Server Management Studio on server CHWORK0DB0PRW01.bisnodech.local (10.41.70.205). This prevents me from working, as my tasks require access to these database tables. Below there i
04/01/2026 11:55:07
rungwatsangt Please describe your issue below :
The t...
INC0791071 P2 Resolved Backup of production databaseMessageExecuted as user: BISNODECH\picdbsrv01. ...: 50% complete End Progress Progress: 2026-04-01 03:06:40.13 Source: Back Up Database Task Executing query "declare @backupSetId as int select @backupS
04/01/2026 13:30:48
wieczorekp Please describe your issue below :
Backu...
SCTASK0610903 P4 On Hold Install / Configure Database Server - POSLOVNA.HR
11/17/2025 05:49:31
barlicg
SCTASK0679416 P4 On Hold General Database Request - EUUIPORDB0PRW01
02/25/2026 10:51:12
domanskip
SCTASK0679418 P4 On Hold General Database Request - DKNNERHDB0PRW01
02/25/2026 10:51:37
domanskip
SCTASK0692608 P4 Open General Database Request - CHPICBUDB0PRW01
03/10/2026 08:27:37
muelleru
SCTASK0707347 P4 Open General Database Request - CHWORK0DB0PRW01
03/30/2026 15:02:27
grgica
[https://www.mindmeister.com/app/map/3958338569](https://www.mindmeister.com/app/map/3958338569)
[https://www.shopclawmart.com/listings/content-machine-0c67b3b3](https://www.shopclawmart.com/listings/content-machine-0c67b3b3)
[https://www.skool.com/content-academy/classroom/5aa3a00c?md=58a59a23d51d45fb88bb14d917d4f692](https://www.skool.com/content-academy/classroom/5aa3a00c?md=58a59a23d51d45fb88bb14d917d4f692)
[https://github.com/teng-lin/notebooklm-py](https://github.com/teng-lin/notebooklm-py)
[https://github.com/aiming-lab/MetaClaw](https://github.com/aiming-lab/MetaClaw)
[https://github.com/NousResearch/hermes-agent?tab=readme-ov-file](https://github.com/NousResearch/hermes-agent?tab=readme-ov-file)
[https://github.com/domanskip_dnbgit/DBAdmin/tree/main/MSSQL/scripts/diagnostic](https://github.com/domanskip_dnbgit/DBAdmin/tree/main/MSSQL/scripts/diagnostic)
[https://github.com/kedharkamisetti/MSSQL_Server_DBA_Scripts/tree/main/Always%20on%20AG](https://github.com/kedharkamisetti/MSSQL_Server_DBA_Scripts/tree/main/Always%20on%20AG)
[https://dbadash.com/](https://dbadash.com/)
<!-- restart numbering -->
1. Muzli
[http://muz.li/](http://muz.li/)
1. Landing Picks
[https://www.landingpicks.com/](https://www.landingpicks.com/)
1. Maxi Best Of
[https://maxibestof.one/](https://maxibestof.one/)
1. Site of Sites
[https://www.siteofsites.co/](https://www.siteofsites.co/)
1. Landbook
opisz mi [https://land-book.com/](https://land-book.com/)
1. One Page Love
opisz mi [https://onepagelove.com/](https://onepagelove.com/)
1. CSS Design Awards
opisz mi [https://www.cssdesignawards.com/](https://www.cssdesignawards.com/)
1. Unsection
opisz mi [https://www.unsection.com/](https://www.unsection.com/)
1. Minimal Gallery
opisz mi [https://minimal.gallery/](https://minimal.gallery/)
1. Godly
opisz mi [https://godly.website/](https://godly.website/)
1. Lapa Ninja
opisz mi [https://www.lapa.ninja/](https://www.lapa.ninja/)
1. Landings
opisz mi [https://landings.dev/](https://landings.dev/)
1. Landing Folio
opisz mi [https://www.landingfolio.com/](https://www.landingfolio.com/)
1. Killer Portfolio
opisz mi [https://www.killerportfolio.com/](https://www.killerportfolio.com/)
1. CSS Winner
opisz mi [https://www.csswinner.com/](https://www.csswinner.com/)
1. FWA
opisz mi [https://thefwa.com/](https://thefwa.com/)
1. Commerce Cream
opisz mi [https://commercecream.com/](https://commercecream.com/)
1. Ecomm Design
opisz mi [https://ecomm.design/](https://ecomm.design/)
1. Awwwards
opisz mi [https://www.awwwards.com/](https://www.awwwards.com/)
1. CSS Nectar
opisz mi [https://cssnectar.com/](https://cssnectar.com/)
1. Webdesign-Inspiration
opisz mi [https://www.webdesign-inspiration.com/](https://www.webdesign-inspiration.com/)
1. Brutalists Websites
opisz mi [https://brutalistwebsites.com/](https://brutalistwebsites.com/)
1. Hover States
opisz mi [https://www.hoverstat.es/](https://www.hoverstat.es/)
1. Wix Inspiration
opisz mi [https://www.wix.com/studio/inspiration](https://www.wix.com/studio/inspiration)
1. Codrops
opisz mi [https://tympanus.net/codrops/](https://tympanus.net/codrops/)
1. Abduzeedo
opisz mi [https://abduzeedo.com/](https://abduzeedo.com/)
1. Fonts In Use
opisz mi [https://fontsinuse.com/](https://fontsinuse.com/)
1. Brand New
opisz mi [https://www.underconsideration.com/br](https://www.underconsideration.com/br)...
1. Dribbble
opisz mi [https://dribbble.com/](https://dribbble.com/)
1. Behance
opisz mi [https://www.behance.net/](https://www.behance.net/)
1. Pinterest
opisz mi [https://www.pinterest.com/](https://www.pinterest.com/)
1. Savee.it
opisz mi [https://savee.it/](https://savee.it/)
1. Cosmos
opisz mi [https://cosmos.so/](https://cosmos.so/)
1. Design Inspiration
opisz mi [https://www.designspiration.com/](https://www.designspiration.com/)
1. Showit Store
opisz mi [https://store.showit.com](https://store.showit.com)
1. Webflow Templates
opisz mi [https://webflow.com/templates](https://webflow.com/templates)
1. Curated Design
opisz mi [https://www.curated.design/](https://www.curated.design/)
1. SquareSpace Templates
opisz mi [https://www.squarespace.com/templates](https://www.squarespace.com/templates)...
Oracle
Development
10.10.220.147
devel1.bisnode.cz
Linux Red Hat
10.10.220.149
devel2.bisnode.cz
Linux Red Hat
Production
10.10.200.150
app-prod.bisnode.cz
Linux Red Hat
10.10.200.51
public.cekia.cz
Linux Red Hat
10.10.200.56
MS-INHOUSE.bisnode.cz
Windows 2019 Datacenter
10.10.200.98
product.bisnode.cz
Linux Red Hat
10.10.220.103
oracle-mgmt.bisnode.cz
Linux Red Hat
10.108.160.250
NOCREWPDB0NPW01.bisnor.local
Windows 2022 Datacenter
10.108.2.102
HRSM002ORAPRW01.egv.si
Windows 2022 Standard
10.108.2.106
HRSM002ORAPRW03.WLWhr.local
Windows 2016 Standard
10.131.170.8
oracledb-01.orange.bisnode.net
Linux Oracle
10.164.101.27
NOCREWPDB0PRW01.orange.bisnode.net
Windows 2022 Datacenter
Test
10.131.10.8
oracledb-01a.blue.bisnode.net
Linux Oracle
10.131.10.9
oracledb-01t.blue.bisnode.net
Linux Oracle
EUDPLOYAPPPRL01.bisnode.net
ansible-playbook -i inventories/prod/linux_new/file_inventory.yaml -T 60 splunk_otel_collector.yaml --diff -f 20 -l debuildse01.bisnode.net,prod-lb1.bisnor.local,k8s-app-slave1.prod.cluster1.orange.bisnode.net
ansible-playbook -i inventories/file_inventory.yaml splunk_otel_collector.yaml --ask-pass -e ansible_user=[USERNAME@BISNODE.NET](mailto:USERNAME@BISNODE.NET) -l server1,server2,server3
[https://github.com/shyftai/shyft-skills](https://github.com/shyftai/shyft-skills)
[https://github.com/affaan-m/everything-claude-code\](https://github.com/affaan-m/everything-claude-code\)
[https://github.com/shyftai/shyft-skills](https://github.com/shyftai/shyft-skills)
[https://github.com/shyftai/WEBOS](https://github.com/shyftai/WEBOS)
[https://github.com/NousResearch/hermes-agent](https://github.com/NousResearch/hermes-agent)
[https://github.com/garrytan/gstack](https://github.com/garrytan/gstack)
[https://github.com/bradwmorris/ra-h_os](https://github.com/bradwmorris/ra-h_os)
[https://github.com/DavidROliverBA/ArchitectKB](https://github.com/DavidROliverBA/ArchitectKB) - OBSIDIANOWA kb
[https://clawhub.ai/olliewazza/larry](https://clawhub.ai/olliewazza/larry) -. postowanie na Tiktoku z OpenClaw
Rize - Automatic Time Tracking for Agencies & Freelancers [https://share.google/MMxL1bkgEoQ2n4T0R](https://share.google/MMxL1bkgEoQ2n4T0R)
Pobierz aplikację Rize Time Tracker ze sklepu Microsoft Store [https://apps.microsoft.com/detail/xpdc57ftxpm1p5?ocid=webpdpshare](https://apps.microsoft.com/detail/xpdc57ftxpm1p5?ocid=webpdpshare)
Supernote Manta - Supernote [https://share.google/PbN48mo3qf0qwOXRh](https://share.google/PbN48mo3qf0qwOXRh)
w capacities mam 24 litego sporo materiału do ogarnięcia
[https://github.com/gyoridavid/ai_agents_az](https://github.com/gyoridavid/ai_agents_az)
[https://dba-multitool.org/](https://dba-multitool.org/)
[https://github.com/danhuss/awesome-sql?tab=readme-ov-file#sqlserver](https://github.com/danhuss/awesome-sql?tab=readme-ov-file#sqlserver)
[https://github.com/erikdarlingdata/DarlingData?tab=readme-ov-file](https://github.com/erikdarlingdata/DarlingData?tab=readme-ov-file)
[https://erikdarling.com/sp_loghunter/](https://erikdarling.com/sp_loghunter/)
[https://github.com/erikdarlingdata/PerformanceMonitor](https://github.com/erikdarlingdata/PerformanceMonitor)
[https://github.com/erikdarlingdata/PerformanceMonitor/](https://github.com/erikdarlingdata/PerformanceMonitor/)
[https://github.com/danielmiessler/Fabric](https://github.com/danielmiessler/Fabric)
[https://github.com/pprevos/emacs-writing-studio/tree/master](https://github.com/pprevos/emacs-writing-studio/tree/master)
[https://github.com/glittercowboy/taches-cc-resources](https://github.com/glittercowboy/taches-cc-resources)
[https://github.com/glittercowboy/taches-cc-resources](https://github.com/glittercowboy/taches-cc-resources)
[https://github.com/virattt/dexter](https://github.com/virattt/dexter)
[https://github.com/anthropics/claude-cookbooks/tree/main](https://github.com/anthropics/claude-cookbooks/tree/main)
[https://github.com/BehiSecc/awesome-claude-skills](https://github.com/BehiSecc/awesome-claude-skills)
[https://github.com/KarelDO/awesome-codex](https://github.com/KarelDO/awesome-codex)
[https://github.com/EinGuterWaran/awesome-opensource-boilerplates](https://github.com/EinGuterWaran/awesome-opensource-boilerplates)
[https://github.com/teng-lin/notebooklm-py](https://github.com/teng-lin/notebooklm-py)
[https://github.com/microsoft/generative-ai-for-beginners](https://github.com/microsoft/generative-ai-for-beginners)
[https://github.com/HKUDS/nanobot](https://github.com/HKUDS/nanobot)
[https://github.com/google-labs-code/stitch-skills](https://github.com/google-labs-code/stitch-skills)
[https://github.com/f/prompts.chat](https://github.com/f/prompts.chat)
[https://github.com/agent0ai/agent-zero](https://github.com/agent0ai/agent-zero)
[https://github.com/BlockRunAI/ClawRouter](https://github.com/BlockRunAI/ClawRouter)
[https://gist.github.com/mberman84/885c972f4216747abfb421bfbddb4eba](https://gist.github.com/mberman84/885c972f4216747abfb421bfbddb4eba)
[https://gist.github.com/mberman84/663a7eba2450afb06d3667b8c284515b](https://gist.github.com/mberman84/663a7eba2450afb06d3667b8c284515b)
[https://www.notion.so/2c7dff0fa84e800a883cd03929852e9d?v=2c7dff0fa84e806794f7000cafdee766](https://www.notion.so/2c7dff0fa84e800a883cd03929852e9d?v=2c7dff0fa84e806794f7000cafdee766)
[https://github.com/unclecode/crawl4ai](https://github.com/unclecode/crawl4ai)
[https://github.com/hesamsheikh/awesome-openclaw-usecases](https://github.com/hesamsheikh/awesome-openclaw-usecases)
[https://github.com/Curbob/LobsterBoard](https://github.com/Curbob/LobsterBoard)
[https://www.pingcap.com/blog/local-first-rag-using-sqlite-ai-agent-memory-openclaw/](https://www.pingcap.com/blog/local-first-rag-using-sqlite-ai-agent-memory-openclaw/)
[https://github.com/msitarzewski/agency-agents](https://github.com/msitarzewski/agency-agents)
[https://github.com/alirezarezvani/claude-skills](https://github.com/alirezarezvani/claude-skills)
[https://github.com/karpathy/autoresearch](https://github.com/karpathy/autoresearch)
Important
[https://medium.com/@rentierdigital/the-complete-openclaw-architecture-that-actually-scales-memory-cron-jobs-dashboard-and-the-c96e00ab3f35](https://medium.com/@rentierdigital/the-complete-openclaw-architecture-that-actually-scales-memory-cron-jobs-dashboard-and-the-c96e00ab3f35)
[https://alirezarezvani.medium.com/from-assistant-to-autonomous-engineer-the-9-month-technical-evolution-of-claude-code-1671362d6902](https://alirezarezvani.medium.com/from-assistant-to-autonomous-engineer-the-9-month-technical-evolution-of-claude-code-1671362d6902)
Here are 10 free Google courses worth taking:
1. Introduction to Generative Al
• Understand what Generative AI actually is and how it works.
• Learn how to build simple AI applications using Google tools
🔗 [https://lnkd.in/ghGR-kqa](https://lnkd.in/ghGR-kqa)
2. Introduction to Large Language Models
• Get a clear understanding of models like ChatGPT.
• Learn where LLMs are used, why they matter, and how they can be improved, without heavy tech terms.
🔗 [https://lnkd.in/gMKCQ7nf](https://lnkd.in/gMKCQ7nf)
3. Introduction to Responsible Al
• Learn how AI can be built ethically.
• Explore Google’s 7 core principles for creating fair, safe, and responsible AI systems.
🔗 [https://lnkd.in/g4EAJmGT](https://lnkd.in/g4EAJmGT)
4. Prompt Design in Vertex Al
• Learn how to write better prompts to get better results from AI.
• Practice creating text and images using Google’s AI tools with hands-on exercises.
🔗 [https://lnkd.in/gWJg-6aP](https://lnkd.in/gWJg-6aP)
5. Introduction to Image Generation
• Understand how AI creates images from scratch.
• Learn the core ideas behind modern image-generation models.
🔗 [https://lnkd.in/ggZWmem7](https://lnkd.in/ggZWmem7)
6. Encoder-Decoder Architecture
• Learn how AI translates languages, summarizes content, and generates text.
• A simple introduction to the backbone of language models.
🔗 [https://lnkd.in/gc-g3-fq](https://lnkd.in/gc-g3-fq)
7. Attention Mechanism
• See how AI learns to focus on important information in text and images.
• A quick and clear intro to one of the most important AI concepts.
🔗 [https://lnkd.in/gfXVJFPw](https://lnkd.in/gfXVJFPw)
8. Transformer Models and BERT Model
• Understand the models that changed modern AI.
• Learn how BERT understands context in language, and earn a digital badge on completion.
🔗 [https://lnkd.in/gGGKTCsS](https://lnkd.in/gGGKTCsS)
9. Create Image Captioning Models
• Build AI models that can understand images and describe them in words.
• Learn how vision and language work together.
🔗 [https://lnkd.in/g62aH2sf](https://lnkd.in/g62aH2sf)
10. Introduction to Generative Al Studio
• Explore Google’s platform for building AI applications.
• See real demos that show how ideas turn into working AI tools.
🔗 [https://lnkd.in/gRnedPKk](https://lnkd.in/gRnedPKk)
Which one are you starting with? Let me know in the comments below.
[https://dnbenterprise.atlassian.net/wiki/spaces/ioeu/pages/2265517075/DBA-+Responsibilities](https://dnbenterprise.atlassian.net/wiki/spaces/ioeu/pages/2265517075/DBA-+Responsibilities)
[https://dnbenterprise.atlassian.net/browse/DBETO-4039](https://dnbenterprise.atlassian.net/browse/DBETO-4039)
Guido 41793353181
Szczepan 792657587
Mariusz 604078929
Grzesiek 607382811
BISW12PFASTA02 - moje konto nie ma tam dostępu
BISW12PSQLDB01 - OKBISW12PSQLDB03 - brak dostępu do SQLi
BISW19PNAVDB01 - nie mogę się dobić RDpem
CHBCC00DB0PRW01 - OK
CHCONS0DB0NPW01 - OK
CHCONS0DB0PRW01 - OK
CHDOCUWAPPPRW01 - OK nie ma tutaj operatorów i alertów może warto wdrożyć
CHGDPRADB0PRW01 - OK
CHHRSALDB0PRW01 - OK
CHLOOKUDB0PRW01 - OK
CHMISFIDB0PRW01 - OK
CHONL00DB0PRW01 - OK
CHPICBUDB0PRW01 - OK
CHREPSTDB0PRW01 - OK
CHSWEXTDB0PRW01 - OK
CHVEEAMDB0PRW01 - OK
CHWORK0DB0PRW01 - OK
CHXMLBIDB0PRW01 - OK
BISW12PREPRT01 - brak dostępu do SQLa
CHREPRTDB1PRW01 - OK to jest reposr server
SCTASK0692608 - General Database Request - CHPICBUDB0PRW01 -> uruchomienie skryptu w bazie danych, moim zdaniem to zmiana, trzeba zaplanować
CHG0132414 -> K0116800 - Backup bazy piccard 6
SCTASK0705419 -> General Backup Request - CHPICBUDB0NPW01
Restore Piccard_Business backup from Prod (Guido already had a backup from CHPICBUDB0PRW01.bisnodech.local available) in test 10.146.11.71 (chpicbudb0npw01.bisnodech.local).
New restore requested for DEV load test of business_industry_code (see also CHG0131971)
CHG0131971 -> CTASK0116937 - Create backup of Piccard_Business 03/28/2026 11:00:00
RITM0449061 -> czekam na dyski do polcostamHR
RITM0436704 -. dodanie backup do Veem on RITM0436704
RITM0436709 -> moje sprawdzenie backupów na EUUIPORDB0PRW01 - czekam na veem
RITM0436607 -> Create WINDOWS Cluster on SEBART0DB0PRW01.orange.bisnode.net and SEBART0DB0PRW01.orange.bisnode.net 
which will be needed to create SQL Server Always On. Installation is required before moving the BART system to a production environment.
This is according RITM0417111 and RITM0417112
//MSSQL - create splunk user
USE master;
GO
CREATE LOGIN [splunk] WITH PASSWORD = 'SplMon!123', CHECK_POLICY = OFF;
GO
GRANT VIEW SERVER STATE TO [splunk];
GO
GRANT VIEW ANY DEFINITION TO [splunk];
GO
$SqlInstances = 'BISW12PMISDB01.bisnodech.local','10.41.70.205','BISW19PNAVDB01.bisnodech.local','CHURSHAB.bisnodech.local','bisw12pbccdb01.bisnodech.local','bisw12ponldb01.bisnodech.local','bisw12prpsdb01.bisnodech.local','bisw12psqldb01.bisnodech.local','bisw12psqldb02.bisnodech.local','bisw12pxmldb01.bisnodech.local','dnbw08plookup1.dnb.bisnodech.local','piccard.dnbswitzerland.ch'
$wincred = Get-Credential dnbint\domanskip
Get-DbaAgentJob -SqlInstance $SqlInstances -SqlCredential $wincred | format-table
[https://docs.microsoft.com/en-us/sql/database-engine/install-windows/install-sql-server-from-the-command-prompt?#lnstall](https://docs.microsoft.com/en-us/sql/database-engine/install-windows/install-sql-server-from-the-command-prompt?#lnstall)
CREATE USER 'zbx_monitor'@'%' IDENTIFIED BY 'P@ssw0rd102#';
cat > /var/lib/zabbix/dot.my.cnf << EOF
[client]
user="zbx_monitor"
password="<P@ssw0rd102#"
> EOF
1/04/2026
[Failed] SQL Server Job System: 'CHPICBUDB0PRW01_Full.Daily_0300' completed on \CHPICBUDB0PRW01. -> nie wykonał się backup uruchamiam miesięczny
RITM0452584 -> General Backup Request - CHPICBUDB0NPW01
Restore Piccard_Business backup from Prod (Guido already had a backup from CHPICBUDB0PRW01.bisnodech.local available) in test 10.146.11.71 (chpicbudb0npw01.bisnodech.local).
New restore requested for DEV load test of business_industry_code (see also CHG0131971)
"10.215.0.58","SQL01","sa","6H8YdB1x"
"10.215.0.73","SQL04","sa","6H8YdB1x"
EUINFRADB0NPL01
10.214.69.107
EUINFRADB0NPL02
10.214.69.108
EUINFRADB0NPW01
EUINFRADB0NPW02
ColdAutumn2025!
74,77
Q0B}HD4|9DH;<IeL
CREATE USER 'N-2492-DBA-MySQL-01'@'%' IDENTIFIED BY 'P4ssw0rD123!';
CREATE USER 'N-2492-DBA-MySQL-01'@'10.120.4.11' IDENTIFIED BY 'P4ssw0rD123';
CREATE USER 'N-2492-DBA-MySQL-02'@'%' IDENTIFIED BY 'P4ssw0rD123!';
CREATE USER 'N-2492-DBA-MySQL-03'@'%' IDENTIFIED BY 'P4ssw0rD123!';
CREATE USER 'cya-mysql-recon'@'%' IDENTIFIED BY 'P4ssw0rD123';
CREATE USER 'cya-mysql-recon'@'10.120.4.11' IDENTIFIED BY 'P4ssw0rD123';
GRANT CREATE USER ON *.* to 'cya-mysql-recon'@'%';
FLUSH PRIVILEGES;
alter USER 'N-2492-DBA-MySQL-01'@'%' IDENTIFIED BY 'P4ssw0rD123456';
ALTER USER 'N-2492-DBA-MySQL-01'@'10.120.4.11' IDENTIFIED BY 'P4ssw0rD123';
alter USER 'cya-mysql-recon'@'10.120.4.11' IDENTIFIED with mysql_native_password by 'P4ssw0rD123';
alter USER 'N-2492-DBA-MySQL-01'@'10.120.4.11' IDENTIFIED with mysql_native_password by 'P4ssw0rD123';
---
type: 'DailyNote'
title: April 1, 2026
date: '2026-04-01T00:00:00.000Z'
tags: []
---
[https://github.com/shyftai/shyft-skills](https://github.com/shyftai/shyft-skills)
[https://github.com/affaan-m/everything-claude-code\](https://github.com/affaan-m/everything-claude-code\)
[https://github.com/shyftai/shyft-skills](https://github.com/shyftai/shyft-skills)
[https://github.com/shyftai/WEBOS](https://github.com/shyftai/WEBOS)
[https://github.com/NousResearch/hermes-agent](https://github.com/NousResearch/hermes-agent)
[https://github.com/garrytan/gstack](https://github.com/garrytan/gstack)
[https://github.com/bradwmorris/ra-h_os](https://github.com/bradwmorris/ra-h_os)
[https://github.com/DavidROliverBA/ArchitectKB](https://github.com/DavidROliverBA/ArchitectKB) - OBSIDIANOWA kb
[https://clawhub.ai/olliewazza/larry](https://clawhub.ai/olliewazza/larry) -. postowanie na Tiktoku z OpenClaw
Rize - Automatic Time Tracking for Agencies & Freelancers [https://share.google/MMxL1bkgEoQ2n4T0R](https://share.google/MMxL1bkgEoQ2n4T0R)
Pobierz aplikację Rize Time Tracker ze sklepu Microsoft Store [https://apps.microsoft.com/detail/xpdc57ftxpm1p5?ocid=webpdpshare](https://apps.microsoft.com/detail/xpdc57ftxpm1p5?ocid=webpdpshare)
Supernote Manta - Supernote [https://share.google/PbN48mo3qf0qwOXRh](https://share.google/PbN48mo3qf0qwOXRh)
w capacities mam 24 litego sporo materiału do ogarnięcia
[https://github.com/gyoridavid/ai_agents_az](https://github.com/gyoridavid/ai_agents_az)
[https://dba-multitool.org/](https://dba-multitool.org/)
[https://github.com/danhuss/awesome-sql?tab=readme-ov-file#sqlserver](https://github.com/danhuss/awesome-sql?tab=readme-ov-file#sqlserver)
[https://github.com/erikdarlingdata/DarlingData?tab=readme-ov-file](https://github.com/erikdarlingdata/DarlingData?tab=readme-ov-file)
[https://erikdarling.com/sp_loghunter/](https://erikdarling.com/sp_loghunter/)
[https://github.com/erikdarlingdata/PerformanceMonitor](https://github.com/erikdarlingdata/PerformanceMonitor)
[https://github.com/erikdarlingdata/PerformanceMonitor/](https://github.com/erikdarlingdata/PerformanceMonitor/)
[https://github.com/danielmiessler/Fabric](https://github.com/danielmiessler/Fabric)
[https://github.com/pprevos/emacs-writing-studio/tree/master](https://github.com/pprevos/emacs-writing-studio/tree/master)
[https://github.com/glittercowboy/taches-cc-resources](https://github.com/glittercowboy/taches-cc-resources)
[https://github.com/glittercowboy/taches-cc-resources](https://github.com/glittercowboy/taches-cc-resources)
[https://github.com/virattt/dexter](https://github.com/virattt/dexter)
[https://github.com/anthropics/claude-cookbooks/tree/main](https://github.com/anthropics/claude-cookbooks/tree/main)
[https://github.com/BehiSecc/awesome-claude-skills](https://github.com/BehiSecc/awesome-claude-skills)
[https://github.com/KarelDO/awesome-codex](https://github.com/KarelDO/awesome-codex)
[https://github.com/EinGuterWaran/awesome-opensource-boilerplates](https://github.com/EinGuterWaran/awesome-opensource-boilerplates)
[https://github.com/teng-lin/notebooklm-py](https://github.com/teng-lin/notebooklm-py)
[https://github.com/microsoft/generative-ai-for-beginners](https://github.com/microsoft/generative-ai-for-beginners)
[https://github.com/HKUDS/nanobot](https://github.com/HKUDS/nanobot)
[https://github.com/google-labs-code/stitch-skills](https://github.com/google-labs-code/stitch-skills)
[https://github.com/f/prompts.chat](https://github.com/f/prompts.chat)
[https://github.com/agent0ai/agent-zero](https://github.com/agent0ai/agent-zero)
[https://github.com/BlockRunAI/ClawRouter](https://github.com/BlockRunAI/ClawRouter)
[https://gist.github.com/mberman84/885c972f4216747abfb421bfbddb4eba](https://gist.github.com/mberman84/885c972f4216747abfb421bfbddb4eba)
[https://gist.github.com/mberman84/663a7eba2450afb06d3667b8c284515b](https://gist.github.com/mberman84/663a7eba2450afb06d3667b8c284515b)
[https://www.notion.so/2c7dff0fa84e800a883cd03929852e9d?v=2c7dff0fa84e806794f7000cafdee766](https://www.notion.so/2c7dff0fa84e800a883cd03929852e9d?v=2c7dff0fa84e806794f7000cafdee766)
[https://github.com/unclecode/crawl4ai](https://github.com/unclecode/crawl4ai)
[https://github.com/hesamsheikh/awesome-openclaw-usecases](https://github.com/hesamsheikh/awesome-openclaw-usecases)
[https://github.com/Curbob/LobsterBoard](https://github.com/Curbob/LobsterBoard)
[https://www.pingcap.com/blog/local-first-rag-using-sqlite-ai-agent-memory-openclaw/](https://www.pingcap.com/blog/local-first-rag-using-sqlite-ai-agent-memory-openclaw/)
[https://github.com/msitarzewski/agency-agents](https://github.com/msitarzewski/agency-agents)
[https://github.com/alirezarezvani/claude-skills](https://github.com/alirezarezvani/claude-skills)
[https://github.com/karpathy/autoresearch](https://github.com/karpathy/autoresearch)
Important
[https://medium.com/@rentierdigital/the-complete-openclaw-architecture-that-actually-scales-memory-cron-jobs-dashboard-and-the-c96e00ab3f35](https://medium.com/@rentierdigital/the-complete-openclaw-architecture-that-actually-scales-memory-cron-jobs-dashboard-and-the-c96e00ab3f35)
[https://alirezarezvani.medium.com/from-assistant-to-autonomous-engineer-the-9-month-technical-evolution-of-claude-code-1671362d6902](https://alirezarezvani.medium.com/from-assistant-to-autonomous-engineer-the-9-month-technical-evolution-of-claude-code-1671362d6902)
Here are 10 free Google courses worth taking:
1. Introduction to Generative Al
• Understand what Generative AI actually is and how it works.
• Learn how to build simple AI applications using Google tools
🔗 [https://lnkd.in/ghGR-kqa](https://lnkd.in/ghGR-kqa)
2. Introduction to Large Language Models
• Get a clear understanding of models like ChatGPT.
• Learn where LLMs are used, why they matter, and how they can be improved, without heavy tech terms.
🔗 [https://lnkd.in/gMKCQ7nf](https://lnkd.in/gMKCQ7nf)
3. Introduction to Responsible Al
• Learn how AI can be built ethically.
• Explore Google’s 7 core principles for creating fair, safe, and responsible AI systems.
🔗 [https://lnkd.in/g4EAJmGT](https://lnkd.in/g4EAJmGT)
4. Prompt Design in Vertex Al
• Learn how to write better prompts to get better results from AI.
• Practice creating text and images using Google’s AI tools with hands-on exercises.
🔗 [https://lnkd.in/gWJg-6aP](https://lnkd.in/gWJg-6aP)
5. Introduction to Image Generation
• Understand how AI creates images from scratch.
• Learn the core ideas behind modern image-generation models.
🔗 [https://lnkd.in/ggZWmem7](https://lnkd.in/ggZWmem7)
6. Encoder-Decoder Architecture
• Learn how AI translates languages, summarizes content, and generates text.
• A simple introduction to the backbone of language models.
🔗 [https://lnkd.in/gc-g3-fq](https://lnkd.in/gc-g3-fq)
7. Attention Mechanism
• See how AI learns to focus on important information in text and images.
• A quick and clear intro to one of the most important AI concepts.
🔗 [https://lnkd.in/gfXVJFPw](https://lnkd.in/gfXVJFPw)
8. Transformer Models and BERT Model
• Understand the models that changed modern AI.
• Learn how BERT understands context in language, and earn a digital badge on completion.
🔗 [https://lnkd.in/gGGKTCsS](https://lnkd.in/gGGKTCsS)
9. Create Image Captioning Models
• Build AI models that can understand images and describe them in words.
• Learn how vision and language work together.
🔗 [https://lnkd.in/g62aH2sf](https://lnkd.in/g62aH2sf)
10. Introduction to Generative Al Studio
• Explore Google’s platform for building AI applications.
• See real demos that show how ideas turn into working AI tools.
🔗 [https://lnkd.in/gRnedPKk](https://lnkd.in/gRnedPKk)
Which one are you starting with? Let me know in the comments below.
---
type: 'DailyNote'
title: March 28, 2026
date: '2026-03-28T00:00:00.000Z'
tags: []
---
15:47
15:48
[Stop using one AI tool for everything. I&#39;ve watched teams burn entire quartersdoing exactly this. They pick ChatGPT for everything.Or Claude for...](https://www.linkedin.com/posts/gabriel-millien_stop-using-one-ai-tool-for-everything-ive-activity-7441461202570018816-Js9H?utm_source=share&utm_medium=member_android&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw)[Stop using one AI tool for everything. I&#39;ve watched teams burn entire quartersdoing exactly this. They pick ChatGPT for everything.Or Claude for... - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/2b5b58f4-1d2a-469d-879f-2d593c12d6d1)
15:49
[Claude AI Features and Uses for Business | Chris Donnelly posted on the topic | LinkedIn](https://www.linkedin.com/posts/donnellychris_so-youve-followed-the-bangwagon-and-moved-activity-7441113696069824512-dUFl?utm_source=share&utm_medium=member_android&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw)[Claude AI Features and Uses for Business | Chris Donnelly posted on the topic | LinkedIn - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/827c4850-62f4-45ae-931d-163dd825281a)
15:51
[Maximizing AI with Human Touch: 3 Techniques for Effective Collaboration | GenAI Works posted on the topic | LinkedIn](https://www.linkedin.com/posts/genai-works_generativeai-cheatsheat-ai-activity-7442099169210744832-LOex?utm_source=share&utm_medium=member_android&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw)[Maximizing AI with Human Touch: 3 Techniques for Effective Collaboration | GenAI Works posted on the topic | LinkedIn - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/450737d8-e17b-4684-b186-c0bcb3f79a1f)
15:53
[RAG System Optimization: Focus on Pipeline, Not Just Retrieval | GenAI Works posted on the topic | LinkedIn](https://www.linkedin.com/posts/genai-works_ai-rag-generativeai-activity-7441733004198232064-lLTp?utm_source=share&utm_medium=member_android&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw)[RAG System Optimization: Focus on Pipeline, Not Just Retrieval | GenAI Works posted on the topic | LinkedIn - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/832840a3-31d3-42a4-bb5a-039fb398783e)
---
type: 'DailyNote'
title: March 25, 2026
date: '2026-03-25T00:00:00.000Z'
tags: []
---
![image](https://capacities-files.s3.eu-central-1.amazonaws.com/private/18897fd9-ca4f-4a44-9720-3f5a9247259f/raw.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA5VTNRR6EBR56K2NK%2F20260506%2Feu-central-1%2Fs3%2Faws4_request&X-Amz-Date=20260506T061736Z&X-Amz-Expires=43200&X-Amz-Signature=4a707395b44e2c2de951bdfc4b1bad9bfc6a162cd3732479f033081438e4515e&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)
[image - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/18897fd9-ca4f-4a44-9720-3f5a9247259f)
21:40
Guido 41793353181
Szczepan 792657587
Mariusz 604078929
Grzesiek 607382811
![alt text](image.png)
journals/2026-05-07.md
+180
View File
@@ -0,0 +1,180 @@
---
Status: Active
type: DailyNote
tag: [daily, 2026]
---
Muszę przyśpieszyć Instalacje [RITM0469393 | Requested Item | Prod](https://dnbgatewayprod.service-now.com/now/nav/ui/classic/params/target/sc_req_item.do%3Fsys_id%3D78db89e9cf64035081ff3d6b2c851c2a%26sysparm_stack%3Dsc_req_item_list.do%3Fsysparm_query%3Dactive%3Dtrue) uzytkownik sie troche się zaczyna niepokoić a że to jest
SCTASK0732693 -> BISW12PREPRT01 - Database User Access - Soundararajan Sundaram - We don't grant access to server, after investigation, was granted access as db_owner\
\
SCTASK0732692 -> CHCONS0DB0PRW01 - Database User Access - Soundararajan Sundaram - We don't grant access to server, after investigation, was granted access as db_owner
RITM0470195 -> SCTASK0731961 - Investigate potential optimization - EUNIAPPBAKPRL01
RITM0469393 -> SCTASK0731046 - General Database Request - CHHRSALDB0PRW01 - muszę zaplanować zmianę
***
08:18
[#llm #aiengineering #agenticai #aicommunity | GenAI Works | 40 comments](https://www.linkedin.com/posts/genai-works_llm-aiengineering-agenticai-activity-7457772432200851458-61ff?utm_source=social_share_video_v2\&utm_medium=android_app\&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw\&utm_campaign=whatsapp)[#llm #aiengineering #agenticai #aicommunity | GenAI Works | 40 comments - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/7c2c3264-b01e-43b5-bdbb-2c66c42ea11b)
08:31
[LLM vs RAG vs AI Agent vs Agentic AI: Which AI to Build | GenAI Works posted on the topic | LinkedIn](https://www.linkedin.com/posts/genai-works_llm-rag-aiagents-activity-7456594649130930176-MlYU?utm_source=social_share_video_v2\&utm_medium=android_app\&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw\&utm_campaign=whatsapp)[LLM vs RAG vs AI Agent vs Agentic AI: Which AI to Build | GenAI Works posted on the topic | LinkedIn - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/886050a0-4780-4f61-8d3b-5c5aae96cd27)
09:04
[AI isn’t just creating new tools, it’s creating entirely new careers. Great Share by: Kumud Deepali Rudraraju, SHRM CP Original Post Below ⬇️ ⬇️ ⬇️ AI...](https://www.linkedin.com/posts/ai-agent-in-action_ai-isnt-just-creating-new-tools-its-creating-activity-7449758375501881345-N1Fc?utm_source=social_share_video_v2\&utm_medium=android_app\&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw\&utm_campaign=whatsapp)[AI isn’t just creating new tools, it’s creating entirely new careers. Great Share by: Kumud Deepali Rudraraju, SHRM CP Original Post Below ⬇️ ⬇️ ⬇️ AI... - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/e2313d9b-16e8-4246-87a7-4e40b23a20ed)
09:06
[Are you guys using IBM Bob? One thing I’ve noticed while working with AI coding assistants: The productivity boost doesn’t come from “better prompts.”...](https://www.linkedin.com/posts/aakritiaggarwal13_are-you-guys-using-ibm-bob-one-thing-i-activity-7458020915692580864-pWk9?utm_source=social_share_video_v2\&utm_medium=android_app\&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw\&utm_campaign=whatsapp)[Are you guys using IBM Bob? One thing I’ve noticed while working with AI coding assistants: The productivity boost doesn’t come from “better prompts.”... - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/4735c177-0f74-481b-a882-44fa180ded1e)
09:06
[How Modern AI Actually Works: A 7-Layer Breakdown | Gabriel Millien posted on the topic | LinkedIn](https://www.linkedin.com/posts/gabriel-millien_most-people-talk-about-ai-but-very-few-activity-7449524311444590593-CrCN?utm_source=social_share_video_v2\&utm_medium=android_app\&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw\&utm_campaign=whatsapp)[How Modern AI Actually Works: A 7-Layer Breakdown | Gabriel Millien posted on the topic | LinkedIn - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/748d1ff7-9712-4e04-ac4e-21e6a47c3538)
09:07
[Untitled](https://www.linkedin.com/feed/update/urn:li:groupPost:3063585-7457835475437993986?utm_source=social_share_video_v2\&utm_medium=android_app\&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw\&utm_campaign=whatsapp)[Untitled - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/c5ccbcf3-c3b1-42db-ba38-b4caf24a60cb)
09:08
[10 faz marketingu z AI (LoTR edition). LVL 1 - ShireWchodzisz w ChatGPT i piszesz „daj mi 10 pomysłów na na X. Sielanka. Chill. LVL 2 - GollumKażesz...](https://www.linkedin.com/posts/miroburn_10-faz-marketingu-z-ai-lotr-edition-lvl-activity-7457744150495465472-sS3Z?utm_source=social_share_send\&utm_medium=android_app\&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw\&utm_campaign=whatsapp)[10 faz marketingu z AI (LoTR edition). LVL 1 - ShireWchodzisz w ChatGPT i piszesz „daj mi 10 pomysłów na na X. Sielanka. Chill. LVL 2 - GollumKażesz... - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/c2707854-6bff-41ae-a3df-213111113472)
09:09
[Most people think AI skills are about learning tools. They’re not. In 2027, the gap won’t be who uses AI. It will be who can design systems with it. H...](https://www.linkedin.com/posts/ashish--joshi_most-people-think-ai-skills-are-about-learning-activity-7450378191392694273-o0kw?utm_source=social_share_video_v2\&utm_medium=android_app\&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw\&utm_campaign=whatsapp)[Most people think AI skills are about learning tools. They’re not. In 2027, the gap won’t be who uses AI. It will be who can design systems with it. H... - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/d9d35d9a-db40-480a-b14c-c700ebd667b8)
09:10
[MSME Owners: AI Automation as a Business Decision | Sandeep Bonagiri posted on the topic | LinkedIn](https://www.linkedin.com/posts/bonagirisandeep_most-msme-owners-treat-ai-automation-like-activity-7448312170972463104-puaW?utm_source=social_share_video_v2\&utm_medium=android_app\&rcm=ACoAAABPPbABRj_Wz-uE6RNF1OovDvp_bVTBfEw\&utm_campaign=whatsapp)[MSME Owners: AI Automation as a Business Decision | Sandeep Bonagiri posted on the topic | LinkedIn - Notes](https://app.capacities.io/60b77bcb-1f4b-4404-bd65-db5272fe714a/b88ce4af-fd28-48bc-813c-f66f829fc9c7)
I am working on a project using Paperclip. I want to create a platform that helps people to get their complete WordPress website optimized for SEO and LLM’s. I want to create blog posts based on the information the website already has. All by getting access to an application password of the website. Based on this information, give me a Mission-Goal text.
Pracuję nad projektem wykorzystującym Paperclip. Chcę stworzyć platformę, która pomaga ludziom w pełni zoptymalizować ich stronę internetową WordPress pod kątem SEO oraz LLM-ów. Chcę tworzyć wpisy blogowe na podstawie informacji, które strona internetowa już zawiera. Wszystko to poprzez uzyskanie dostępu za pomocą hasła aplikacyjnego do strony internetowej. Na podstawie tych informacji przygotuj tekst Mission–Goal.
Znaleźć osoby (agentów), które będą skanować strony internetowe WordPress, optymalizować strony WordPress pod kątem SEO oraz LLM-ów, przeprowadzać badania na temat treści w celu pisania wpisów blogowych oraz wyszukiwać i tworzyć treści. Oraz inne agenty do wykonywania zadań, które są do tego potrzebne.
Pewnie — poniżej masz **klarowny, produktowy opis agentów AI**, rozpisany logicznie (tak, żeby nadawał się zarówno do dokumentacji, pitcha, jak i architektury systemu multi‑agentowego).
***
## Opis agentów AI w platformie
### 1. **Agent Skanowania Strony (Website Scanner Agent)**
**Rola:**\
\
Automatycznie skanuje istniejącą stronę WordPress po uzyskaniu dostępu przez hasło aplikacyjne.
**Zakres odpowiedzialności:**
- Analiza struktury strony (strony, wpisy, kategorie, tagi)
- Odczyt istniejących treści, meta‑danych, nagłówków (H1–H6)
- Identyfikacja braków SEO i problemów technicznych
- Przygotowanie surowych danych wejściowych dla pozostałych agentów
**Output:**\
\
Ustrukturyzowany model wiedzy o stronie (content map + metadata).
***
### 2. **Agent SEO i LLM Optimization (SEO & LLM Optimizer Agent)**
**Rola:**\
\
Optymalizuje stronę pod kątem klasycznego SEO oraz widoczności w systemach opartych na modelach językowych (LLM‑ready content).
**Zakres odpowiedzialności:**
- Analiza słów kluczowych i intencji użytkownika
- Optymalizacja nagłówków, opisów, struktury treści
- Dostosowanie treści do zasad „AI‑friendly content”
- Rekomendacje zmian on‑page i contentowych
**Output:**\
\
Zoptymalizowane wytyczne SEO + struktura treści gotowa do publikacji.
***
### 3. **Agent Badania Treści (Content Research Agent)**
**Rola:**\
\
Bada kontekst tematyczny strony i jej branży w celu rozszerzenia treści.
**Zakres odpowiedzialności:**
- Analiza tego, **o czym strona już mówi**
- Identyfikacja luk contentowych
- Research tematów, pytań użytkowników i trendów
- Propozycje tematów blogowych zgodnych z profilem strony
**Output:**\
\
Lista tematów i kierunków treści opartych o realny kontekst strony.
***
### 4. **Agent Pisania Treści (Content Writer Agent)**
**Rola:**\
\
Tworzy gotowe wpisy blogowe i treści marketingowe na podstawie danych z innych agentów.
**Zakres odpowiedzialności:**
- Generowanie artykułów blogowych opartych na istniejącej wiedzy strony
- Dopasowanie stylu do brand voice klienta
- Tworzenie treści zoptymalizowanych pod SEO i LLM
- Przygotowanie contentu gotowego do publikacji w WordPressie
**Output:**\
\
Gotowe wpisy blogowe i treści do bezpośredniego wdrożenia.
***
### 5. **Agent Orkiestrujący / Operacyjny (Orchestrator Agent)**
**Rola:**\
\
Zarządza współpracą pozostałych agentów i pilnuje kompletności procesu.
**Zakres odpowiedzialności:**
- Kolejkowanie zadań dla agentów
- Kontrola jakości wyników
- Pilnowanie zależności między etapami
- Uruchamianie dodatkowych agentów pomocniczych (np. audyt, QA)
**Output:**\
\
Spójny, kompletny proces optymalizacji i produkcji treści.
***
### 6. **Agenci Pomocniczy (Utility / Task Agents)**
**Rola:**\
\
Wykonują wyspecjalizowane zadania wspierające cały system.
**Przykłady:**
- Agent audytu technicznego
- Agent kontroli jakości treści
- Agent publikacji i synchronizacji z WordPressem
- Agent raportowania i podsumowań
***
## Podsumowanie (jednym zdaniem – pitch):
> System multi‑agentowy AI, który skanuje istniejące strony, optymalizuje je pod SEO i LLM‑y oraz automatycznie generuje wysokiej jakości treści blogowe na podstawie realnego kontekstu strony.
SCTASK0731046 -> General Database Request - CHHRSALDB0PRW01 Please install the SQL Server Full‑Text Search (FTS) on this SQL instance.
journals/2026-05-08.md
+47
View File
@@ -0,0 +1,47 @@
---
title: 2026-05-08
type: DailyNote
tags: [daily, 2026]
---
# TODO
- [x] ogarnąć narzędzia i zadania
## Gdzie łączą się SEO i AEO
```mermaid
flowchart LR
subgraph SEO ["SEO (Wyszukiwarki)"]
direction TB
S1["Pozycje na stronach wyników wyszukiwania (SERP)"]
S2["Linki zwrotne (backlinki) i autorytet domeny"]
S3["Słowa kluczowe i metatagi"]
S4["Szybkość strony i wydajność techniczna"]
S5["Współczynnik klikalności (CTR) i ruch"]
S_GOAL("Cel: Umieszczenie Twojej strony w wynikach")
end
subgraph COMMON ["Część wspólna"]
direction TB
C1["Wysokiej jakości, autorytatywne treści"]
C2["Wyraźna wiedza specjalistyczna (E-E-A-T)"]
C3["Regularne aktualizacje treści"]
C4["Optymalizacja mobilna"]
C5["Szybki czas ładowania"]
C6["Treści skupione na użytkowniku"]
end
subgraph AEO ["AEO (Silniki odpowiedzi AI)"]
direction TB
A1["Cytowania w odpowiedziach generowanych przez AI"]
A2["Polecane fragmenty i pola odp."]
A3["Schemat FAQ i dane strukturalne"]
A4["Jasne, bezpośrednie odpowiedzi"]
A5["Rozpoznawanie encji (bytów)"]
A_GOAL("Cel: Zacytowanie treści jako odpowiedzi")
end
SEO --- COMMON
COMMON --- AEO
```
journals/2026-05-11.md
+57
View File
@@ -0,0 +1,57 @@
---
type: "DailyNote"
title: Daily Note - 2026-05-12
date: 2026-05-12 08:06:11
tags: []
Status: Active
---
CREATE USER 'dnb_eu_dba'@'%' IDENTIFIED BY 'CommonDBA890!@#';
GRANT ALL PRIVILEGES ON * . * TO 'dnb_eu_dba'@'%' WITH GRANT OPTION;
ALTER USER 'dnb_eu_dba'@'%' PASSWORD EXPIRE NEVER;
FLUSH PRIVILEGES;
log-error=/var/log/mysql/error.log
slow_query_log = 1
slow_query_log_file = /var/log/mysql/slow-query.log
long_query_time = 5
innodb_file_per_table = 1
#bind-address=10.198.1.136
bind-address=0.0.0.0
port=3306
CREATE USER 'dnb_eu_dba'@'%' IDENTIFIED BY 'CommonDBA890!@#';
GRANT ALL PRIVILEGES ON * . * TO 'dnb_eu_dba'@'%' WITH GRANT OPTION;
ALTER USER 'dnb_eu_dba'@'%' PASSWORD EXPIRE NEVER;
FLUSH PRIVILEGES;
CREATE USER 'splunk'@'localhost' IDENTIFIED BY 'xPOfVfLbKpv4kHu!@#78';
GRANT SELECT ON performance_schema.* TO 'splunk'@'localhost';
GRANT RELOAD, PROCESS, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'splunk'@'localhost';
ALTER USER 'splunk'@'localhost' PASSWORD EXPIRE NEVER;
FLUSH PRIVILEGES;
chmybccdb0npl01 root
Cc-2ch019.$qsRa
GRANT SLAVE MONITOR
ON *.*
TO 'splunk'@'127.0.0.1';
FLUSH PRIVILEGES;
INC0805514 -> (Splunk Observability) Disk > 80% [G:] CHDBASQDB0NPW01.bisnodech.local - backup and truncate logs
INC0805145 -> (Splunk Observability) Disk > 80% [/var/log] chmybccdb0npl01.blue.bisnode.net - Monitoring issue, repair splunk otel
SCTASK0737627 -> General Database Request - BART DRN 3422 - preparation to migration - Full backup and restore ~1:10 + incremental backup ~20 min If is posibility to run backup and restore in one day
journals/2026-05-12.md
+13
View File
@@ -0,0 +1,13 @@
---
type: "DailyNote"
title: Daily Note - 2026-05-12
date: 2026-05-12 08:06:07
tags: []
Status: Active
---
INC0803163 INC0802900 INC0802882 INC0802800 INC0802778 INC0802767 INC0802759 -> (Splunk Observability) Disk > 80% [E:\] chsqlbkstoprw01.bisnodech.local - system backupowy się zapchał i przenoszę dane do S3 na OVH
SCTASK0737127 - Database Access - użytkownik ma dostęp do danych, problem z białym ekranem nie jest problemem bazodanowym. User have permission to read data
SCTASK0733968 - Windows User Access - Philip Armin Hainz - Solving this problem requires restarting the database and changing the configuration, which I need to issue the change for. -> zawiesiłem zgłoszenie
journals/2026-05-13.md
+9
View File
@@ -0,0 +1,9 @@
---
type: "DailyNote"
title: Daily Note - 2026-05-13
date: 2026-05-13 09:40:13
tags: []
Status: Active
---
9:30 #meeting [[2026-05-13-bi-weekly-DevOps]] -> notatki ze spotkania
journals/2026-05-14.md
+359
View File
@@ -0,0 +1,359 @@
---
type: "DailyNote"
title: Daily Note - 2026-05-14
date: 2026-05-14 08:05:53
tags: []
Status: Active
---
## Podsumowanie dnia
### 1. Zarządzanie uprawnieniami i dostępami (Access Management)
Większość Twojego dnia skupiała się na realizacji zgłoszeń dostępowych (SCTASK):
* **SCTASK0740526:** Potwierdziłeś nadanie uprawnień dla użytkownika Gagandeep Singh.
* **SCTASK0740469 (dla Philippa Kunza):** Utworzyłeś i skonfigurowałeś dostęp dla konta `axeed_export_job`. Użytkownik otrzymał rolę `db_datareader` w bazie `Piccard_Business` oraz dostęp do bazy `SwissExtract_GSRL_7`. Przeprowadziłeś również weryfikację uprawnień tego konta na serwerach `10.146.11.71` oraz `10.146.11.86`.
* **SCTASK0733968 (Philip Armin Hainz):** Skonfigurowałeś dostępy dla kont domenowych `BISNODE\hainz` oraz `BISNODE\eso9`. Zostały im przypisane role `db_owner` w kilkunastu bazach danych (m.in. *CERTIFICATES, CSAT_CZ, CSAT_SK, DRIFT, GBR_CZ, GBR_SK, OKBASE, UPGRADE_PRG, WORK, WORKDAY_CZ, WORKDAY_SK*).
### 2. Konfiguracja i zadania administracyjne (Maintenance)
* **SCTASK0727383 (CHMISFIDB0PRW01):** Zaktualizowałeś konfigurację wysyłki e-maili systemowych. Ze względu na to, że Guido Mark odszedł z firmy, zmieniłeś adres nadawcy z jego indywidualnego na grupowy adres zespołu: `dbetechops-monitoring@dnb.com`.
### 3. Rozwój bazy wiedzy i narzędzi AI (Wiki LLM)
Sporą część dnia spędziłeś na intensywnej rozbudowie swojej bazy wiedzy (Wiki):
* **Przetwarzanie i integracja nowych źródeł:** Dodałeś notatki, koncepcje i podsumowania dotyczące m.in. *Autoresearch*, *Software 2.0*, narzędzi AI w pracy (*Nanobanana workflow*, *Karpathy LLM Wiki*) oraz problemów *Accidental DBA*.
* **Tworzenie syntez:** Stworzyłeś nową stronę z zestawieniem i porównaniem strategii automatyzacji AI.
* **Prace strukturalne:** Rozpocząłeś inicjalizację fundamentów Wiki LLM, wykonałeś "Feynman Check" dla nowych materiałów i zrefaktoryzowałeś schemat (w tym plik `GEMINI.md`).
Dzień był bardzo produktywny, łączący bieżące gaszenie biletów (BAU) z ważną pracą nad długofalowymi procesami i bazą wiedzy!
SCTASK0740526 Database User Access - Gagandeep Singh miał nadane uprawnienia
SCTASK0740469 Database User Access - Philipp Kunz
USE [Piccard_Business]
GO
CREATE USER [BISNODECH\axeed_export_job] FOR LOGIN [BISNODECH\axeed_export_job]
GO
USE [Piccard_Business]
GO
ALTER ROLE [db_datareader] ADD MEMBER [BISNODECH\axeed_export_job]
GO
USE [SwissExtract_GSRL_7]
GO
CREATE USER [BISNODECH\axeed_export_job] FOR LOGIN [BISNODECH\axeed_export_job]
GO
on 10.146.11.71 user axeed_export_job has
read access BisnodeJobAudit
added read access to Piccard_Business SwissExtract_GSRL_7
on 10.146.11.86 user axeed_export_job already has access to db axeed_export_job
this is the same use because is in AD
SCTASK0733968 - Windows User Access - Philip Armin Hainz
USE [master]
GO
CREATE LOGIN [BISNODE\hainz] FROM WINDOWS WITH DEFAULT_DATABASE=[master]
GO
use [CERTIFICATES];
GO
use [WORKDAY_SK];
GO
USE [CERTIFICATES]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [CERTIFICATES]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
use [CSAT_CZ];
GO
use [CERTIFICATES];
GO
USE [CSAT_CZ]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [CSAT_CZ]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
use [CSAT_SK];
GO
use [CSAT_CZ];
GO
USE [CSAT_SK]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [CSAT_SK]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
use [DRIFT];
GO
use [CSAT_SK];
GO
USE [DRIFT]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [DRIFT]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
use [GBR_CZ];
GO
use [DRIFT];
GO
USE [GBR_CZ]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [GBR_CZ]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
use [GBR_SK];
GO
use [GBR_CZ];
GO
USE [GBR_SK]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [GBR_SK]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
use [OKBASE];
GO
use [GBR_SK];
GO
USE [OKBASE]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [OKBASE]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
use [UPGRADE_PRG];
GO
use [OKBASE];
GO
USE [UPGRADE_PRG]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [UPGRADE_PRG]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
use [WORK];
GO
use [UPGRADE_PRG];
GO
USE [WORK]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [WORK]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
use [WORKDAY_CZ];
GO
use [WORK];
GO
USE [WORKDAY_CZ]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [WORKDAY_CZ]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
use [WORKDAY_SK];
GO
use [WORKDAY_CZ];
GO
USE [WORKDAY_SK]
GO
CREATE USER [BISNODE\hainz] FOR LOGIN [BISNODE\hainz]
GO
USE [WORKDAY_SK]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\hainz]
GO
Msg 15025, Level 16, State 2, Line 3
The server principal 'BISNODE\hainz' already exists.
Msg 15023, Level 16, State 1, Line 11
User, group, or role 'BISNODE\hainz' already exists in the current database.
Msg 15023, Level 16, State 1, Line 23
User, group, or role 'BISNODE\hainz' already exists in the current database.
Msg 15023, Level 16, State 1, Line 35
User, group, or role 'BISNODE\hainz' already exists in the current database.
Msg 15023, Level 16, State 1, Line 47
User, group, or role 'BISNODE\hainz' already exists in the current database.
Msg 15023, Level 16, State 1, Line 59
User, group, or role 'BISNODE\hainz' already exists in the current database.
Msg 15023, Level 16, State 1, Line 71
User, group, or role 'BISNODE\hainz' already exists in the current database.
Msg 15023, Level 16, State 1, Line 95
User, group, or role 'BISNODE\hainz' already exists in the current database.
Msg 15023, Level 16, State 1, Line 107
User, group, or role 'BISNODE\hainz' already exists in the current database.
Msg 15023, Level 16, State 1, Line 119
User, group, or role 'BISNODE\hainz' already exists in the current database.
Msg 15023, Level 16, State 1, Line 131
User, group, or role 'BISNODE\hainz' already exists in the current database.
Completion time: 2026-05-14T11:34:39.8589764+02:00
USE [master]
GO
CREATE LOGIN [BISNODE\eso9] FROM WINDOWS WITH DEFAULT_DATABASE=[master]
GO
use [CERTIFICATES];
GO
use [WORKDAY_SK];
GO
USE [CERTIFICATES]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [CERTIFICATES]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
use [CSAT_CZ];
GO
use [CERTIFICATES];
GO
USE [CSAT_CZ]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [CSAT_CZ]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
use [CSAT_SK];
GO
use [CSAT_CZ];
GO
USE [CSAT_SK]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [CSAT_SK]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
use [DRIFT];
GO
use [CSAT_SK];
GO
USE [DRIFT]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [DRIFT]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
use [GBR_CZ];
GO
use [DRIFT];
GO
USE [GBR_CZ]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [GBR_CZ]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
use [GBR_SK];
GO
use [GBR_CZ];
GO
USE [GBR_SK]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [GBR_SK]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
use [OKBASE];
GO
use [GBR_SK];
GO
USE [OKBASE]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [OKBASE]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
use [UPGRADE_PRG];
GO
use [OKBASE];
GO
USE [UPGRADE_PRG]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [UPGRADE_PRG]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
use [WORK];
GO
use [UPGRADE_PRG];
GO
USE [WORK]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [WORK]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
use [WORKDAY_CZ];
GO
use [WORK];
GO
USE [WORKDAY_CZ]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [WORKDAY_CZ]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
use [WORKDAY_SK];
GO
use [WORKDAY_CZ];
GO
USE [WORKDAY_SK]
GO
CREATE USER [BISNODE\eso9] FOR LOGIN [BISNODE\eso9]
GO
USE [WORKDAY_SK]
GO
ALTER ROLE [db_owner] ADD MEMBER [BISNODE\eso9]
GO
Commands completed successfully.
Completion time: 2026-05-14T11:35:37.1466569+02:00
SCTASK0727383 - General Database Request - CHMISFIDB0PRW01 Please change the e-mail sender from markgu@dnb.com to an active e-mail address because Guido Mark had to leave the company. -> zmieniłem na nasz ogólny dbetechops-monitoring@dnb.com
journals/20_levels_of_ai_tools_mastery.md
+67
View File
@@ -0,0 +1,67 @@
**Tytuł:**
20 LEVELS OF AI TOOLS MASTERY
**1. LLMs**
Learn how to use LLMs or AI chat models like ChatGPT, Grok, Claude, and Gemini the best way.
**2. AI workspace productivity tools**
Learn how to use AI in workspace productivity tools like Notion, ClickUp, Asana, and Monday.
**3. AI for writing**
Use AI writing assistant tools like Grammarly and QuillBot to write fast on the go with AI suggestions to correct your mistakes.
**4. AI image generation**
Learn how to use various AI image generation tools like Midjourney, Ideogram, OpenAI 4o image generation, and more.
**5. AI video generation**
Learn how to use various AI video generation tools like Runway, Kling, Hailou, Luma, OpenAI Sora and more.
**6. AI content generation**
Learn how to use content marketing tools like Jasper and Writesonic to rank better on LLMs and Google Search.
**7. AI for meeting assistance**
Learn how to use various AI video generation tools like Runway, Kling, Hailou, Luma, OpenAI Sora and more.
*(Uwaga: Twórca grafiki popełnił tutaj błąd "kopiuj-wklej" i powielił opis z poziomu 5)*
**8. AI video editing**
Learn how to use tools like VEED, Opus, and Descript to create and edit videos fast.
**9. AI for analysis**
Learn how to use tools like Rows, Julius, and Quadratic to complete hours of analysis work in minutes.
**10. Create presentations with AI**
Use AI tools like Gamma and Decktopus to create presentations in minutes with AI.
**11. Creating websites with AI**
Use tools like Softr, Webflow, 10Web, Dora, and Wegic to create beautiful websites with AI.
**12. AI for customer support**
Use tools like Chatsimple and Dante to create customer support chatbots for your website that also help with inbound lead generation.
**13. AI for Email newsletters**
Use tools like Beehiiv to build, grow, write, and monetize your email newsletter with AI-powered writing tools.
**14. AI for email management**
Use tools like Gemini in Gmail and Superhuman Email to get help with managing your emails.
**15. AI for social media growth**
Master using tools like Taplio, Tweet Hunter, Later, and VidIQ to help you grow fast with AI on multiple social media platforms.
**16. AI for sales**
Use tools like Hubspot Breeze that revolutionise how you build relationships. Generate high-quality pipeline, engage prospects with personalized outreach, and navigate the sales process with efficiency to close more deals than ever before.
**17. AI for marketing operations**
Use tools like Hubspot Breeze that will transform how you connect with audiences. Generate qualified leads, automate personalised campaigns, and streamline content creation.
**18. AI for customer service operations**
Supercharge customer experience with AI tools like Hubspot Breeze that multiplies your service impact. Scale support operations without scaling complexity, respond to customers in real time, and turn service interactions into growth opportunities.
**19. AI for marketing operations**
Use AI tools like n8n, Zapier, and make to build workflow automations to complete hours of work in minutes.
*(Uwaga: Tytuł powielony z punktu 17, lecz opis dotyczy narzędzi no-code/automatyzacji)*
**20. AI for software development**
Use AI tools like Cursor, Windsurf, Devin, Bolt, and Lovable to accelerate software development work.
**Stopka grafiki:**
Subscribe to Mindstream to learn AI for free ⟶ www.mindstream.news
journals/inbox.md
+4615
View File
File diff suppressed because it is too large Load Diff
journals/incidents/INC0794075/after.sqlplan
BIN
View File
Binary file not shown.
journals/incidents/INC0794075/before.sqlplan
BIN
View File
Binary file not shown.
journals/incidents/INC0794075/index.md
+251
View File
@@ -0,0 +1,251 @@
Problem:
INC0794075 - XMBILLING process is very slow in recent days
Dostałem od Użytkownika informację że zapisy do danych nie działają optymalnie jest bardzo mała przepustowość i kolejka zaległości rośnie.
Informacje zawarte w INC
While reviewing the dashboard
https://app.eu0.signalfx.com/#/dashboard/HCvOOb9AIAM?groupId=HAX-r3yAIAU&configId=HCvOOb9AIAQ&density=2&startTime=-12h&endTime=Now
I noticed that the xmlbilling process, which transfers data from
10.146.11.194 (XMLBILLING database) to
10.146.11.103 (AboSystem_CH and AboSystem_DNB databases), is performing very slowly.
Its current peak processing speed is approximately 30 times lower than the average expected speed.
Could you please investigate this issue from the database side?
Niestety obciążenie bazy danych i sesji nie wskazywało na problem bezpośrednio z tym że coś na instancji nie są poprawnie ustawione, system utylizował zaledwie 40% swojej mocy, a sesji w bazie było zaledwie kilkadziesiąt, batch requestów było na poziomie 80 max.
[[r01.png]]
W trakcie analizy nie zidentyfikowałem żadnej sesji która wy próbowała wstawić dane do bazy. Zdiagnozowałem jednak że aplikacja uruchamia to zapytanie
select ol1_0.TransactionNo,ol1_0.AccessType,
ol1_0.Amount,ol1_0.AmountIncludingVAT,ol1_0.BID,
ol1_0.BillToCustomerNo,ol1_0.BookingDate,ol1_0.CampaignNo,
ol1_0.Description,ol1_0.GlobalUsageID,ol1_0.LineDiscount,
ol1_0.LineDiscountAmount,ol1_0.MasterSubscriptionNo,
ol1_0.OrderDate,ol1_0.OrderLineNo,ol1_0.OrderNo,
ol1_0.PricelistCode,ol1_0.ProductCode,
ol1_0.Quantity,ol1_0.QuantityInvoiced,ol1_0.QuantityShipped,
ol1_0.QuantityShippedNotInvoiced,
ol1_0.QuantityToInvoice,
ol1_0.QuantityToShip,
ol1_0.SellToCustomerNo,
ol1_0.ShipToCustomerNo,
ol1_0.ShipmentDate,
ol1_0.ShipmentNo,
ol1_0.ShippedNotInvoiced,ol1_0.SubjectCity,
ol1_0.SubjectCountryCode,ol1_0.SubjectName,
ol1_0.SubjectNo,ol1_0.SubjectSupplierCountryCode,
ol1_0.SubjectUserId,ol1_0.SubscriptionNo,
ol1_0.UnitCost,ol1_0.UnitOfMeasure,ol1_0.UnitPrice,ol1_0.VAT
from XML_SubscriptionOrderLine ol1_0 -- where ol1_0.OrderLineNo= @P0
Po analizie kodu aplikacji aplkikacja zanim wstawi dane musi pobrać dane które wykonuje wczesniej opisane zapytanie co dawało wiele wait typu PAGEOLATCH jak wskazałem na screenach poniżej
[[r02.png]]
[[r03.png]]
Wskazuje to jednoznacznie że zapytanie działa nieoptymalnie. Plan zapytania zanim wstawi dane musi zeskanować ponad 200 mln recordów co pokazuje poniższy rysunek
[[r04.png]]
Jednoznacznie brakuje na tej tabeli indeksu który jest poniżej.
USE [AboSystem_xx]
GO
CREATE NONCLUSTERED INDEX [idx_tmp_XML_SubscriptionOrderLine]
ON [dbo].[XML_SubscriptionOrderLine] ([OrderLineNo])
GO
Po symulacji i sprawdzeniu założyłem indeks na koluminie OrderLineNo. Po tym zabiegu zapytanie bezpośrednio sięga do rekordu w bazie i koszt zapytania spadł drastycznie co pokazuje plan poniżej.
[[r05.png]]
Po uruchomieniu aplikacji całość przyśpieszyła o kilka tysięcy procent co pokazuje poniższy rysunek
[[r06.png]]]]
Kolejka wszystkich zapytań skończyła się do 19:00 zamiast po 4 dniach.
ENG RCA
Poniżej masz **przeredagowaną, spójną i profesjonalną wersję w języku angielskim**, gotową do użycia w **INC / RCA / mailu technicznym**. Zachowałem sens techniczny, ale poprawiłem styl i klarowność.
***
### Incident Description and Root Cause Analysis
I received information from the user that **data write operations were not performing optimally**. The system throughput was very low, and the backlog queue was continuously increasing.
The details were described in the incident (INC).
***
### Initial Observations
While reviewing the monitoring dashboard:
<https://app.eu0.signalfx.com/#/dashboard/HCvOOb9AIAM?groupId=HAX-r3yAIAU&configId=HCvOOb9AIAQ&density=2&startTime=-12h&endTime=Now>
I noticed that the **xmlbilling process**, responsible for transferring data from:
* **10.146.11.194** (XMLBILLING database)
to
* **10.146.11.103** (AboSystem\_CH and AboSystem\_DNB databases),
was performing **significantly slower than expected**.
The current peak processing speed was approximately **30 times lower than the normal average throughput**.
As a result, I was asked to investigate the issue from the **database perspective**.
***
### Database Health Check
Unfortunately, the database instance itself did **not indicate any direct configuration or resource issues**:
* CPU utilization was only around **40%**
* The number of active database sessions was relatively low (only several dozen)
* Batch requests peaked at approximately **80**
This indicated that the instance was **far from resource saturation** and the problem was unlikely to be caused by general database load.
\[\[r01.png]]
***
### Query-Level Analysis
During the analysis, I did **not identify any active sessions inserting data into the target database**.
However, I discovered that the application was repeatedly executing the following SQL query:
```sql
SELECT
ol1_0.TransactionNo,
ol1_0.AccessType,
ol1_0.Amount,
ol1_0.AmountIncludingVAT,
ol1_0.BID,
ol1_0.BillToCustomerNo,
ol1_0.BookingDate,
ol1_0.CampaignNo,
ol1_0.Description,
ol1_0.GlobalUsageID,
ol1_0.LineDiscount,
ol1_0.LineDiscountAmount,
ol1_0.MasterSubscriptionNo,
ol1_0.OrderDate,
ol1_0.OrderLineNo,
ol1_0.OrderNo,
ol1_0.PricelistCode,
ol1_0.ProductCode,
ol1_0.Quantity,
ol1_0.QuantityInvoiced,
ol1_0.QuantityShipped,
ol1_0.QuantityShippedNotInvoiced,
ol1_0.QuantityToInvoice,
ol1_0.QuantityToShip,
ol1_0.SellToCustomerNo,
ol1_0.ShipToCustomerNo,
ol1_0.ShipmentDate,
ol1_0.ShipmentNo,
ol1_0.ShippedNotInvoiced,
ol1_0.SubjectCity,
ol1_0.SubjectCountryCode,
ol1_0.SubjectName,
ol1_0.SubjectNo,
ol1_0.SubjectSupplierCountryCode,
ol1_0.SubjectUserId,
ol1_0.SubscriptionNo,
ol1_0.UnitCost,
ol1_0.UnitOfMeasure,
ol1_0.UnitPrice,
ol1_0.VAT
FROM dbo.XML_SubscriptionOrderLine ol1_0
-- WHERE ol1_0.OrderLineNo = @P0
```
***
### Root Cause Identified
After reviewing the application logic, I confirmed that **before inserting any data**, the application was first reading data using the query shown above.
This query caused **significant PAGEIOLATCH waits**, as shown in the screenshots below:
\[\[r02.png]]
\[\[r03.png]]
This clearly indicated that the query was **not optimized**.
Further analysis of the execution plan revealed that:
* The query was performing a **full scan of more than 200 million records**
* This resulted in excessive I/O and severely degraded performance
\[\[r04.png]]
***
### Resolution
The root cause was identified as a **missing index** on the `XML_SubscriptionOrderLine` table.
The following index was required but did not exist:
```sql
USE [AboSystem_xx];
GO
CREATE NONCLUSTERED INDEX idx_tmp_XML_SubscriptionOrderLine
ON dbo.XML_SubscriptionOrderLine (OrderLineNo);
GO
```
After simulating the change and validating the execution plan, the index was created on the `OrderLineNo` column.
As a result:
* The query started performing **index seeks instead of full table scans**
* The query cost was reduced **drastically**, as shown below:
\[\[r05.png]]
***
### Result After Fix
After restarting the application, the overall system performance improved dramatically:
* Processing speed increased by **several thousand percent**
* The backlog queue was fully processed by **19:00**
* Without the fix, completion was estimated to take **approximately 4 days**
\[\[r06.png]]
***
### Summary
The performance issue was caused by a **missing nonclustered index**, which forced the application to perform full scans on a very large table before insert operations.
Once the index was added, database access became efficient, the application throughput returned to normal, and the backlog was cleared within hours.
***
Jeśli chcesz:
* mogę przygotować **krótszą wersję executive summary**
* albo wersję **strict RCA (Problem / Cause / Resolution / Prevention)**
* albo **wersję pod post‑mortem lub ServiceNow**
Daj znać 👍
journals/incidents/INC0794075/r01.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 37 KiB

journals/incidents/INC0794075/r02.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 18 KiB

journals/incidents/INC0794075/r03.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 22 KiB

journals/incidents/INC0794075/r04.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 34 KiB

journals/incidents/INC0794075/r05.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 4.0 KiB

journals/incidents/INC0794075/r06.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 42 KiB

journals/incidents/INC0794075/r07.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 52 KiB

journals/meetings/07-10-2025-dba.md
+149
View File
@@ -0,0 +1,149 @@
---
type: 'DailyNote'
title: October 7, 2025
date: '2025-10-07T00:00:00.000Z'
tags: [dba, migracja]
---
### Uporządkowane notatki ze spotkania
#### 1) Temat przewodni
- Przegląd zadań infrastrukturalnych i wpływu na DBA
- Szacunki czasowe i odpowiedzialności zespołów (DBA, Windows, Linux, Network)
- Porządkowanie procesu ticketów/obserwowalności i dokumentacji pracy
- Planowanie rebootów (server uptime) i migracji (m.in. HU)
#### 2) Decyzje i ustalenia
- Active Directory end-of-life:
- Decommissioning kontrolerów domeny w Europie (ok. 91 DC) – brak wpływu na bazy danych, bo nie dekomisjonujemy domen/AD.
- DHCP, KMS, serwery plików, Veeam, jump stations (Windows):
- Brak bezpośrednich zadań dla DBA, z wyjątkiem jump stations.
- Jump stations (Windows):
- Potrzebne klienty DB: SQL Server Management Studio (SSMS), MySQL client/workbench (freeware, ale wymagane zgłoszenie/proces).
- Konieczna migracja zapisanych połączeń/konfiguracji (uwaga: skopiować pełny zestaw plików konfiguracyjnych, nie 2/3).
- Integracja z CyberArk – zachować spójność po migracji.
- Szacunek pracy: wpisujemy 20 godzin (kompromis – w zespole są rozbieżne potrzeby od 2h do pełnego dnia/osobę).
- Server uptime / kwartalne restarty:
- Cel: każdy serwer restartowany raz na kwartał; przygotowanie procesu identyfikacji maszyn z długim uptime i bezpiecznych restartów.
- DBA: obecność standby podczas okien restartowych, weryfikacja dostępności instancji po restarcie, szybkie sanity checki.
- Szacunek przygotowawczy: 30 godzin (osobodzień DBA/kwartał na przeglądy i koordynację; BAU/KTLO później).
- Migracja HU (Węgry):
- 16 serwerów (gł. Windows). Zakres DBA zależny od tego, czy to będzie „lift-and-shift” VM czy równoległa modernizacja (np. 2012 → 2025).
- Jeśli 1:1 przeniesienie – kilka godzin DBA na walidację; jeśli modernizacja – większy nakład (kontrola kompatybilności, logins, joby, ustawienia instancji).
- Na teraz wpisane 50 godzin (do weryfikacji po doprecyzowaniu listy baz i sposobu migracji).
- Projekty end-of-life baz danych:
- Nie ma dodatkowych pozycji poza tymi widocznymi; migracje baz trwają ciągle (co miesiąc). To powinno być uwzględniane w planie rocznym.
- Inne:
- „Disable switchboards impaired by migration to GCP” – faza discovery przez ServiceNow/DB app (czeka na doprecyzowanie/scan).
#### 3) Wpływ na DBA – główne punkty
- Jump stations:
- Instalacja i konfiguracja klientów (SSMS, MySQL), przeniesienie profili/połączeń, dostosowanie CyberArk.
- Rebooty kwartalne:
- Standby i post-check po restarcie; test zapytań zdrowotnych; ewentualne odtworzenie dostępu.
- Migracje (ciągłe, miesięczne):
- Realny, stały nakład pracy nieodzwierciedlony w bieżącym arkuszu – potrzeba lepszej ewidencji.
- HU:
- Do potwierdzenia sposób migracji i lista instancji, możliwy większy effort przy modernizacji.
#### 4) Szacunki godzin (aktualne wpisy)
- Jump stations (DBA): 20h
- Server uptime (przygotowanie procesu, nie BAU): 30h
- Migracja HU: 50h
- Inne zespoły: w arkuszu łącznie ~60h dla Network/Linux/Windows (potwierdzone jako sensowne)
- Uwaga: migracje comiesięczne baz – duży, stały effort, którego nie widać w sumie godzin (do odzwierciedlenia).
#### 5) Ryzyka i uwagi
- Utrata zapisanych połączeń/konfiguracji na jump stations – konieczny pełny backup plików konfiguracyjnych klientów DB.
- Zależności od AD (konty serwisowe dla SQL/Agent), uprawnień i dostępów – czasochłonne i często niewidoczne w taskach głównych.
- Niska obserwowalność po stronie DB (brak pełnej integracji ze Splunk/Zabbix/ServiceNow) powoduje niedoszacowanie prac DBA.
- Długie cykle ticketów DBA i prace równoległe utrudniają rzetelne raportowanie czasu.
#### 6) Działania następne
- Jump stations:
- Sporządzić krótką instrukcję eksportu/importu konfiguracji klientów (SSMS, MySQL Workbench/CLI).
- Zgłosić instalacje freeware formalnym kanałem; potwierdzić zgodność z CyberArk.
- Server uptime:
- Zbudować proces: generowanie listy serwerów z długim uptime, planowe okna, lista kontrolna DB po restarcie, przypisanie odpowiedzialnych/standby.
- Migracja HU:
- Uzyskać inwentarz baz/instancji, potwierdzić tryb migracji (lift-and-shift vs modernizacja), zaktualizować estymaty.
- Widoczność pracy DBA:
- Ustalić automatyzację generowania ticketów z alertów (preferowany Splunk; ewentualnie mostkowanie Zabbix → ServiceNow).
- Zdefiniować minimalne logowanie czasu przy incydentach/projektach, aby tworzyć metryki (dashboard obciążenia i typów pracy).
- Przegląd listy odpowiedzialności DBA i dopisanie brakujących elementów do arkusza projektów (szczególnie migracje cykliczne).
- Komunikacja:
- W piątek wrócić do tematu metryk/ticketów i potwierdzić estymaty (zwłaszcza jump stations, server uptime, HU).
#### 7) Otwarte pytania
- Czy HU będzie czystym przeniesieniem VM, czy modernizacją systemów/SQL?
- Jaki dokładnie zestaw klientów DB ma być standardem na jump stations (wersje, polityka aktualizacji)?
- Które narzędzie do automatyzacji ticketów wybieramy (Splunk vs integracja Zabbix → ServiceNow) i jaki jest plan wdrożenia?
- Jak formalnie włączyć comiesięczne migracje DB do planu/arkusza (pozycja BAU/KTLO czy dedykowane projekty)?
Jeśli chcesz, przygotuję krótką checklistę dla:
- eksportu/importu profili połączeń SSMS i MySQL Workbench,
- sanity check po restarcie serwera dla SQL Server i MySQL,
- szablon zadania w ServiceNow dla „quarterly reboot DB check”.
journals/meetings/10-03-2026-dplunk-db.md
+25
View File
@@ -0,0 +1,25 @@
Meeting notes
Incident management
- Mariusz reported receiving multiple daily Splunk alerts about disk usage, resulting in duplicate incidents that affect statistics.
- Mariusz fixed eight database-related disk usage cases and escalated two cases to the Windows team for disk extension.
- Mariusz explained that the Windows team requires a five-day advance change request for disk extensions, causing delays in resolving incidents.
- Mariusz clarified that duplicate daily incidents are being generated from Zabbix via Splunk integration, not from Splunk observability alerts.
- Oleksandr explained that Splunk updates existing incidents instead of creating new tickets, while Zabbix integration creates multiple tickets due to its configuration.
- Mariusz described ongoing issues with duplicate incident tickets generated daily, which negatively affect team statistics.
System integration
- Mats mentioned ongoing testing of ServiceNow integration, which may be related to the incident creation process.
- Mariusz explained that some servers in the failover database cluster were never attached to Splunk due to port conflicts, despite the Splunk agent being installed.
- Mariusz described ongoing errors when attempting to update monitoring agents or add servers to Ansible, including connection failures and outdated agents.
- Kamil offered to mark servers missing in Splunk in Mariusz's file to help prioritize which servers to skip for now
System monitoring gaps
- Mariusz highlighted that several servers are not monitored by basic infrastructure templates, making it impossible to add database monitoring.
- Mats reported sending a ticket to Lashek after discovering many Windows servers missing from monitoring, while Linux servers were fully accounted for.
- Mats reported sending a ticket to Lashek after discovering many Windows servers missing from monitoring, while Linux servers were fully accounted for.
System troubleshooting
- Oleksandr suggested checking firewall settings and block lists as a possible cause for recent connection issues, but Mariusz noted the servers had worked a week ago.
- Oleksandr explained that connection issues may be due to disabled services or local firewall settings on Windows machines, and suggested testing with the Windows team
Follow-up tasks
| Task | Assigned to | Due date | Bucket |
| :-------------------------------------------------------------------------------------------------------------------------------------- | :---------- | :------- | :----- |
| Mariusz stated they will discuss the issue of excessive incident tickets with Adrian to address the impact on team statistics (Mariusz) | | | |
| Contact the Windows team to resolve Ansible connection issues for specific servers (Mariusz) | | | |
journals/meetings/2026-05-13-bi-weekly-DevOps.md
+77
View File
@@ -0,0 +1,77 @@
# Notatki ze spotkania (Bi-weekly DevOps)
**Data:** 13.05.2026
## Cel spotkania
Przegląd postępów w projektach i statusu operacyjnego.
## Decyzje
- Dodanie dni wolnych (tzw. "Squeeze Day") dla pracowników ze Szwecji w systemie HR.
- Zamknięcie projektu ***** i przejście do wsparcia operacyjnego.
- Obniżenie poziomu logowania Splunk w celu zmniejszenia wolumenu logów.
- Wykorzystanie skryptów NinjaRMM do aktualizacji plików konfiguracyjnych Splunk na serwerach Windows.
- Rozpoczęcie procesu akceptacji dla globalnego dostępu do Remote Desktop Manager.
## Otwarte pytania i problemy
- **System HR:** Wyjaśnienie kwestii szwedzkich dni wolnych i "Squeeze Days" w systemie HR.
- **Migracja firewalli:** Zbadanie incydentów związanych z migracją firewalli oraz problemów z asymetrycznym routingiem (wycofanie zmian nie wchodzi w grę z powodu końca wsparcia i braku odnowienia licencji starych urządzeń). Celem jest zakończenie migracji wszystkich firewalli CGI (w tym OVH, AWS i Węgry) na Palo Alto, zastępując firewalle Checkpoint, do końca listopada.
- **Licencje i patchowanie Red Hat:** Oczekiwanie na odnowienie licencji Red Hat po zakończeniu oceny ryzyka przez dostawcę. Opóźnienie wynika z wolnej odpowiedzi Red Hat na pytania. Około 10 nieprodukcyjnych serwerów Red Hat jest podatnych na nowe luki, ale ryzyko jest umiarkowane i patchowanie może poczekać w ramach 90-dniowego okna. Patchowanie planowane jest przed produkcyjnymi weekendami.
- **Monitorowanie licencji:** Konieczność poprawy procesu monitorowania licencji i powiadomień o odnowieniach (brak alertów z systemów wewnętrznych, powiadomienia przychodziły przez DocuSign).
## Status projektów
- Inżynierowie zakończyli projekt ***** (Kamil wyśle szczegółowe informacje).
- Zespół inżynierów rozpoczyna nowe projekty, w tym globalną automatyzację wymiany certyfikatów (pod przewodnictwem Kamila) oraz prace nad agentami logowania scen.
## Zadania
- [ ] **Ewa:** Dodanie dni wolnych dla wszystkich szwedzkich pracowników w systemie HR.
---
## Źródło (Source)
Decisions
Add public holiday (Squeeze Day) for Swedish workers in HR system.
Close ***** project and transition to operational support.
Lower Splunk logging level to reduce log volume.
Use NinjaRMM scripting to update Splunk config files on Windows servers.
Initiate approval process for Remote Desktop Manager global access.
Open questions
Clarify Swedish holidays and Squeeze Days in HR system.
Investigate firewall migration incidents and asymmetric routing problems.
Wait for Red Hat license renewal to complete risk assessment and patching.
Improve license monitoring and renewal notification process.
Agenda
Goal: Review project progress and operational status
Ewa updated the HR system to include the public holiday for Swedish workers, addressing the confusion about the upcoming days off.
Participants discussed the concept of "squeeze days" in Sweden, clarifying that these are days off between holidays and regular workdays, which are not common in Poland.
Ewa updated the HR system to include the public holiday for Swedish workers and planned to notify the Swedish team in their chat.
Project updates
Ewa announced that the engineering team completed the ***** project, and Kamil will send out more information to relevant people.
Ewa explained that the engineering team is starting new projects, including automating certificate replacement globally with Kamil leading, and working on scene logging agents.
Firewall migration
Participants discussed ongoing issues with undocumented firewall flows and unexpected failures during migration, noting that rollback is not an option due to end-of-life and non-renewal of licenses.
Ewa stated that the goal is to complete migration of all CGI firewalls, including OVH, AWS, and Hungary, to Palo Alto by the end of November, replacing Checkpoint firewalls.
Splunk logging
Leszek raised concerns about excessive Splunk logging obscuring problem analysis, and Jimmy suggested lowering the logging level and updating the config file across Windows servers.
Red Hat licensing and patching
Adrian explained that Red Hat license expiration is preventing patching of affected servers, and renewal is pending completion of Red Hat's risk assessment, with patching planned before production weekends.
Red Hat licensing
Adrian explained that the Red Hat license renewal process was delayed due to Red Hat's slow response to assessment questions, but he expects the contract to be renewed before production patching begins.
Red Hat vulnerabilities
Adrian stated that there are about 10 non-production Red Hat servers affected by the new vulnerability, but the risk is moderate and patching can wait within the allowed 90-day window.
License monitoring
Leszek asked about tools for monitoring license status, and Adrian clarified that notifications are typically received via DocuSign, but internal systems did not provide alerts for this renewal.
Follow-up tasks
Task Assigned to Due date Bucket
Add the public holiday for all Swedish workers in the HR system (Ewa)
journals/meetings/21-04-2026-Local Swiss System Piccard.md
+86
View File
@@ -0,0 +1,86 @@
📝 Notatka ze spotkania: Local Swiss System Piccard
Cel spotkania: Ujednolicenie oczekiwań oraz planu działań w związku z niedawnymi incydentami wydajnościowymi w systemie Piccard i innych systemach szwajcarskich.
🔍 Główne tematy dyskusji
Wpływ incydentów i odpowiedzialność: Ostatnie awarie miały bezpośredni wpływ na ciągłość biznesową w Szwajcarii (Antje). Ustalono, że konieczne jest jasne zdefiniowanie własności systemów i odpowiedzialności za rozwiązywanie problemów.
Zmiany organizacyjne i dług techniczny: Zespoły Sundarama, Radka i Luki raportują teraz do Sunila, a zespoły infrastrukturalne do Adriana. Po odejściu Guido (który dbał o doraźne łatki) zespół musi skupić się na eliminacji przyczyn źródłowych (Root Cause) zamiast stosowania obejść.
Zarządzanie incydentami: Należy poprawić jakość zgłoszeń (ticketów) i wykorzystywać tzw. "working bridges" (mostki) w celu szybszej i lepszej współpracy międzyzespołowej. Aby priorytetyzować prace nad przestarzałymi systemami, Antje zasugerowała mocniejsze wykorzystywanie procesów PIR (Post-Incident Review).
Problemy z bazą danych: Trwające problemy z blokującymi się sesjami i stabilnością dotyczą bazy audytowej frameworka Spring Batch, a nie głównej bazy biznesowej Piccard (Martin, Luca). Jest to powrót problemu sprzed 3 lat.
Propozycje rozwiązań technicznych:
Głęboka analiza pojemności i zmian we wzorcach użycia bazy audytowej (Antje).
Partycjonowanie danych – rozwiązanie, które w przeszłości zastosował Guido, gdy wolumen danych znacząco wzrósł (Luca).
Analiza zależności procesów, odpytywanie bazy o uruchomione zadania i ich sortowanie, aby zidentyfikować główne blokady (Leszek).
Aktualizacja systemu Piccard: Kompleksowy upgrade to duży projekt wymagający zmian strukturalnych w nowej bazie danych (Roberto).
🎯 Podjęte decyzje
Wszystkie stopniowe ulepszenia i wnioski z analiz będą na bieżąco dokumentowane w systemie śledzenia zadań.
Zostanie zaplanowane kolejne spotkanie (follow-up) w celu weryfikacji postępów prac.
❓ Otwarte pytania
Dokładna przyczyna źródłowa (Root Cause) ciągłego blokowania się bazy audytowej nadal wymaga zbadania.
Decyzja o aktualizacji (upgrade) całego systemu Piccard jest zawieszona – wymaga weryfikacji dostępnych zasobów i ustalenia priorytetów.
📋 Zadania do wykonania (Action Items)
[Antje, Adrian, Sundaram, Radek, Luca] – Doprecyzowanie odpowiedzialności i podziału zadań związanych z trwającymi incydentami w systemach szwajcarskich.
[Adrian, Luca, Martin, DB team, AO team] – Ustanowienie "incident bridge" dla awarii związanych z systemem Piccard w celu sprawnej współpracy i przypisywania zadań do odpowiedzialnych zespołów.
[Luca] – Przygotowanie listy wymaganych aktualizacji systemowych i ulepszeń dla szwajcarskich produktów (i udostępnienie jej na czacie).
[Adrian] – Rozpoczęcie analizy przyczyny źródłowej powtarzających się problemów z wykonywaniem zadań (jobów) w bazie audytowej.
[Paweł, Leszek, Luca] – Wypracowanie jasnego podziału na problemy leżące po stronie aplikacji vs problemy po stronie bazy danych, aby usprawnić troubleshooting.
[Zespoły techniczne] – Zaplanowanie regularnych sesji roboczych (deep dives / burze mózgów) w celu rozwiązywania cyklicznie powracających problemów.
--- source
Decisions
Document incremental improvements and findings in a tracking system.
Set up a follow-up meeting to review progress.
Open questions
Root cause of audit database blocking needs further investigation.
Feasibility of Picard system upgrade is unresolved due to priorities and resources.
Agenda
Goal: Align on expectations and actions regarding recent incidents in Piccard and other Swiss systems
Review recent incidents for Piccard and Swiss systems (10 min)
Discuss potential improvements in monitoring and alerting (10 min)
Align on expectations and actions for incident/engagement process (10 min)
Meeting notes
Incident impact and ownership
Antje explained that recent incidents in Piccard and other Swiss systems have caused disruptions to the local Swiss business, and highlighted the need to clarify ownership and responsibilities moving forward.
Roles and reporting structure
Antje confirmed that Sundaram, Radek, Luca, and their teams now report to Sunil, while infrastructure teams continue to report to Adrian.
System maintenance and transition
Adrian stated that Guido previously played a critical role in maintaining Swiss products, often implementing temporary fixes, and emphasized the need to address root causes now that Guido is no longer with the organization.
Luca confirmed that their team is actively working on improvements for recurring issues in Swiss products
Antje suggested using the PIR as a vehicle to prioritize backlog items for aging Swiss systems
Incident management
Antje discussed the importance of improving ticket quality and encouraged all teams to use working bridges for timely cross-team collaboration
Luca described ongoing collaboration with Paweł, Demchuk, and Martin to address daily database hanging sessions and improve system stability
System stability and database issues
Martin clarified that the recurring issues are caused by the audit database used by the Spring Batch framework, not the Picard business database.
Martin described that recurring job execution issues in the audit database have resurfaced, similar to incidents from three years ago, and emphasized that fixing these consumes significant daily effort.
Antje suggested conducting a deeper analysis of the audit database to investigate potential capacity issues and evolving usage patterns.
Luca recalled that Guido previously improved performance by partitioning the database when data volume reached a certain level, and proposed reviewing if similar action is needed now.
Leszek recommended breaking down processes, querying the database for running jobs, and sorting them by data dependencies to identify and resolve blocking issues.
Martin described that recurring job execution issues in the audit database have resurfaced, similar to incidents from three years ago, and emphasized that fixing these consumes significant daily effort.
Antje suggested conducting a deeper analysis of the audit database to investigate potential capacity issues and evolving usage patterns.
System upgrades and project scope
Roberto confirmed that structural changes to the new database would be required, making the upgrade a significant project.
System architecture
Luca clarified that the audit database is related to the Spring Batch environment and not to GDPR compliance, addressing previous confusion
Follow-up tasks
Task Assigned to Due date Bucket
Clarify ownership of tasks and responsibilities for ongoing incidents in Swiss systems (Antje, Adrian, Sundaram, Radek, Luca)
Establish an incident bridge for Picard-related incidents to enable cross-team collaboration and assign tasks to accountable teams (Adrian, Luca, Martin, DB team, AO team)
Compile a list of system upgrades and improvements needed for Swiss products and share in the chat (Luca)
Adrian proposed investigating the underlying cause of recurring job execution issues in the audit database after the meeting.
Clarify the distinction between application-level and database-level issues for more effective troubleshooting (Paweł, Leszek, Luca)
Antje suggested that the technical team hold regular working sessions to conduct deep dives and brainstorming on recurring issues
Compile a list of system upgrades and improvements needed for Swiss products and share in the chat (Luca)
journals/meetings/26-04-2026-Weekly Engineering & Operations Sync.md
+65
View File
@@ -0,0 +1,65 @@
Meeting notes
Meeting cadence
Ewa announced that the meeting will now be held weekly instead of bi-weekly based on feedback from the Engineering and Operations teams.
Project management
Ewa explained that a new "one project model" will be implemented, consolidating all initiatives and projects into a single Jira portfolio project called ONE.
Project updates
Ewa provided updates on ongoing projects, including completion of the CyberArk project, upcoming SIM logging implementation in Europe, and plans to automate certificate installations with the Venify team.
CyberArk project status
Ewa clarified that the CyberArk project is considered complete from the EU ONE perspective, with implementation finished for infrastructure and database engineering, but ongoing onboarding and developer support now fall under operations and security teams.
CyberArk technical limitations
Oleksandr Lozinskyi explained that CyberArk implementation is complete for Windows environments, but several limitations remain for Linux, such as inability to rotate SSH keys and lack of support for port forwarding, requiring manual intervention for key replacement.
CyberArk operational transition
Ewa stated that future policy decisions and developer onboarding for CyberArk will be managed by the security team, with requests handled through ticketing rather than ongoing project involvement.
Ewa stated that future policy decisions and developer onboarding for CyberArk are now the responsibility of the security team, and any new requirements will be handled as separate projects through ticketing.
CyberArk access policies
Jimmy clarified that all users are now required to use CyberArk for initial connections to jump stations, with approval for this process in place.
Oleksandr explained that general access remains possible, but root permissions must be obtained through CyberArk, resulting in dual management of keys for both CyberArk and general user accounts.
Jimmy clarified that all users must use CyberArk for initial connections to jump stations, but in emergency incidents, a break glass account may be used with approval from Adrian or another incident bridge manager.
Splunk alert management
Jimmy explained that disk alert incidents in Splunk can be grouped into a single incident by standardizing the alert subject naming, and new alerts will add comments to the existing incident.
Jimmy stated that while incidents cannot be assigned to specific teams in Splunk, X-Matters callouts can be configured to notify the appropriate team based on the type of disk alert.
Jimmy clarified that incidents in Splunk cannot be directly assigned to specific teams, but X-Matters callouts can be configured to notify the appropriate team based on the type of disk alert.
Incident response and monitoring
Adrian described a recent incident in Switzerland where database disk alerts were not acted upon for three weeks, resulting in disk space exhaustion and questions about monitoring redundancy.
Adrian stated that leadership in the US recommended database disk alerts should always go to the database team, as development teams often cannot resolve disk space issues.
Incident management and accountability
Adrian raised concerns about accountability for disk space incidents, emphasizing that application teams should be responsible for managing their own servers and infrastructure, not the infra team.
Ewa explained that the global process assigns responsibility for disk alerts and server maintenance to application teams, and noted that this approach will be reinforced as teams report to Sunil.
Disk space accountability
Adrian stated that DRN owners should be held accountable for disk space issues, not the infrastructure team, and suggested that clear communication is needed to reinforce this responsibility.
Disk alert management
Oleksandr reported that 56 tickets related to disk errors remain unattended by the application team, highlighting ongoing issues with disk alert management on Linux systems.
Communication to application teams
Ewa confirmed that application teams were previously informed about disk alert processes and responsibilities through meetings, emails, and Yammer posts, and that reminders have been sent recently.
Incident assignment process
Ewa stated that Splunk-generated incidents are assigned to application teams for initial investigation and validation, with further escalation if needed, and that this process aligns with the European global process.
Alert escalation improvements
Jimmy proposed adding additional alert levels and X-Matters callouts to notify both operations and application teams when disk space issues approach critical levels.
Application deployment requests
Ewa shared that the application team requested code implementation, and participants discussed that AO should handle deployment, not Operations or Engineering
Jimmy explained that infrastructure teams should build and maintain their own solutions for requests, rather than running scripts provided by development teams
Follow-up tasks
Task Assigned to Due date Bucket
Create documentation for processing CyberArk requests and ensure it covers details for all ADs and the Splunk process (Konrad, Leszek)
Adrian suggested that communication should be sent to clarify that DRN owners are accountable for disk space issues, not the infrastructure team.
Review the application team's code deployment request and determine if AO or Linux team should handle deployment (Leszek)
journals/overload/05-2026.md
+12
View File
@@ -0,0 +1,12 @@
---
type: nadgodziny
tags: [maj, 2026, nadgodziny, raport]
title: Nadgodziny
---
Employee ID Type Date Time Start Time End Hours Comment
Overtime in Cash 16/04/2026 16:30 17:30 01.00
Overtime in Cash 18/04/2026 9:00 21:00 12.00
Overtime in Cash 19/04/2026 9:00 21:00 12.00
Overtime in Cash 22/04/2026 18:00 21:00 03.00 RITM0466075
Overtime in Cash 25/04/2026 10:00 12:00 02.00 Patching
Overtime in Cash 26/04/2026 19:00 20:00 01.00 Patching