need a briefing on what the hawkular agent is now doing with respect to inventory
by John Mazzitelli
Joel,
Now that the new inventory-into-metrics is in master and released, I need to know what you did :-D I suspect others will want to know what you did too.
Is it possible for you to write something up or have a 15-minute Blue Jeans session to discuss how inventory is stored in H-Metrics?
I am going to need to know this because I have to implement it in GoLang for HOSA, unless you want to do it :)
--John Mazz
7 minutes
BTM agent relationship with Hawkular agent
by Gary Brown
Hi
On the team call just now, Heiko raised a question about whether the BTM agent could work with the Hawkular agent. So thought I would start this discussion thread to see what the potential options are.
I currently see two issues:
1) The BTM agent must be configured on the jvm command line as a "-javaagent" to install ByteMan for instrumentation purposes. This is instantiated before the JBoss modules (and therefore subsystems etc) are initialised.
2) The hawkular agent won't necessarily be installed in all monitored servers, and instead remotely monitor some. The BTM agent would need to be installed in all servers where business transactions are executing.
One type of integration that may be possible is in terms of delivering the captured business transaction information to the backend? i.e. the BTM agent locally reports it to the Hawkular agent as a relay?
Thoughts?
Regards
Gary
2 hours, 59 minutes
logging in java agents is not trivial in WildFly / EAP
by John Mazzitelli
<tl;dr>
No matter if a java agent uses JBoss Logging or simply relies on the JRE's own Java logging, it still won't work in WildFly/EAP unless you set additional things to environment variables in standalone.conf. So no matter what logging is used, this means problems still need to be overcome when putting java agents in host controllers for EAP 7.0 domain mode.
</tl;dr>
I am looking at how Java Agents should log messages when attached to WildFly or EAP. I want to see if there is a way to implement a Java Agent and NOT have to set any special JAVA_OPTS values to pass to the VM to get it to work.
Turns out, it is not a trivial issue.
I wrote a silly little test agent [1] just to see what would happen if it simply logs a message using *java* logging and spins a thread logging a message every second again using *java* logging. So, no extra third party logging libraries, just using java.util.logging classes that are in the JRE already.
Adding just -javaagent to JAVA_OPTS (in standalone.conf, add something like "-javaagent:/where/it/is/ja.jar=foo=bar") is no good, the server bombs with this error, presumably because my agent already started logging using java logger:
Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
Well, catch-22, because if I set java.util.logging.manager=org.jboss.logmanager.LogManager in JAVA_OPTS, this happens when the test agent tries to log:
Could not load Logmanager "org.jboss.logmanager.LogManager"
java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
which then falls back to java logging, which then causes the server to bomb again because it wants JBoss Logging.
If I set this in standalone.conf:
JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman,org.jboss.logmanager"
the java agent still gets this error:
Could not load Logmanager "org.jboss.logmanager.LogManager"
java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
which is then followed by jboss modules error which causes the server to again to fail to start:
WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
...
at org.jboss.modules.Module.run(Module.java:320)
The ONLY way to get the server to start properly with this java agent installed (EVEN WITH the agent using ONLY java logging), you have to do all of the above plus add this to JAVA_OPTS:
-Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.4.Final.jar
So, in short, you need to add "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" to JAVA_OPTS, you need to add ",org.jboss.logmanager" to JBOSS_MODULES_SYSTEM_PKGS, and you need to add that -Xbootclasspath to JAVA_OPTS just to get a javaagent to work even if the javaagent simply uses nothing more than standard java logging.
---
[1] $ cat JavaAgent.java
import java.util.logging.*;
public class JavaAgent {
private static final Logger log = Logger.getLogger(JavaAgent.class.getName());
public static void premain(String args) {
log.severe("log in premain: " + args);
new Thread(new Runnable() {
public void run() {
while (true) {
try {
Thread.sleep(1000);
log.severe("log in premain loop: " + args);
} catch (Exception e) {
return;
}
}
}
}).start();
}
}
To build it:
$ echo "Premain-Class: JavaAgent" > manifest.mf
$ javac JavaAgent.java
$ jar cvfm ja.jar manifest.mf JavaAgent*
5 hours, 25 minutes
logging in java agents is not trivial in WildFly / EAP
by Mark Ambrose
>>> ... this means problems still need to be overcome when
>>> putting java agents in host controllers for EAP 7.0 domain mode.
>>> </tl;dr>
Is a solution to these problems for when putting java agents in host
controllers for EAP 7.0 domain mode known?
...
[Host Controller] 16:16:33,937 INFO [org.jboss.as.host.controller]
(Controller Boot Thread) WFLYHC0023: Starting server TestServer1a
16:16:33,968 INFO [org.jboss.as.process.Server:TestServer1a.status]
(ProcessController-threads - 3) WFLYPC0018: Starting process
'Server:TestServer1a'
[Server:TestServer1a] Could not load Logmanager
"org.jboss.logmanager.LogManager"
[Server:TestServer1a] java.lang.ClassNotFoundException:
org.jboss.logmanager.LogManager
[Server:TestServer1a] at
java.net.URLClassLoader.findClass(URLClassLoader.java:382)
...
Thanks,
Mark Ambrose
22 hours, 10 minutes
Are Live Casino Games Popular Among Pakistani Players?
by Kyle Linel
In recent years, live casino games have seen a significant rise in popularity worldwide, and Pakistan is no exception. With advancements in technology, players in Pakistan are increasingly opting for live dealer games over traditional online casino games in https://1wincasinoinpakistan.com/ . But what makes these games so appealing, and why are they gaining traction among Pakistani gamblers?
The Appeal of Live Casino Games
Live casino games offer a unique blend of online convenience and the immersive experience of a physical casino. Unlike standard online games, which rely on random number generators (RNGs), live casino games feature real dealers who interact with players in real-time. This creates a more authentic atmosphere and enhances the overall gaming experience. Whether it’s live blackjack, live roulette, or live baccarat, these games allow players to experience the thrill of a land-based casino from the comfort of their homes.
Factors Contributing to Popularity in Pakistan
Real-Time Interaction: One of the main reasons live casino games are gaining popularity in Pakistan is the real-time interaction with dealers. This human element offers a level of transparency and trustworthiness that appeals to many players who are wary of RNG-based games.
Convenience: Live dealer games can be played from any location with a reliable internet connection, making it convenient for players in Pakistan to enjoy their favorite games anytime, anywhere. The mobile-friendly nature of many live casino platforms also allows for a more flexible gaming experience.
Authentic Casino Experience: For many Pakistani players, live casino games replicate the atmosphere of a physical casino. The dealers are often professional and knowledgeable, enhancing the sense of excitement. This authentic experience is hard to beat and has helped live games stand out from traditional online offerings.
Access to International Games: Online casinos offering live dealer games often feature games hosted by international casinos, bringing global casino options to Pakistani players. This increases the variety of games available, allowing players to explore a wider selection than they would find at local brick-and-mortar establishments.
Challenges and Considerations
While live casino games are growing in popularity, there are a few challenges that Pakistani players may face. For instance, the internet connection needs to be fast and stable to ensure smooth gameplay without interruptions. Additionally, the legal landscape for online gambling in Pakistan remains unclear, and players must ensure they are gambling on licensed and reputable platforms to avoid any potential issues.
Conclusion
Live casino games are indeed becoming increasingly popular among Pakistani players due to their immersive, interactive, and authentic experience. The ability to play in real-time with professional dealers and the convenience of accessing these games from home makes them a favorite for many. However, players must remain cautious and ensure they are playing on safe and legal platforms. As the online gambling industry continues to evolve, live casino games are likely to maintain their popularity in Pakistan for years to come.
1 week, 3 days
playing with HOSA outside OS
by John Mazzitelli
I had a couple peeps ask me if they can run HOSA without needing to run it inside an OpenShift cluster (presumably to collect metrics from Prometheus and Jolokia-JMX endpoints that are also running outside of OpenShift). The answer is "yes" and if you are interested, here is a quick how-to.
First get a config.yaml used to configure HOSA (that's the wget command below - it just grabs the example config from github) and then run "docker run" to launch HOSA:
$ wget -O /tmp/config.yaml https://raw.githubusercontent.com/hawkular/hawkular-openshift-agent/maste...
$ docker run --net=host -v /tmp/config.yaml:/config.yaml hawkular/hawkular-openshift-agent --config=/config.yaml
This assumes you have Hawkular-Metrics server (or a full Hawkular-Services server) running on 127.0.0.1 listening to port 8080. If not, just edit config.yaml to point to your server. You can edit that config.yaml however you want.
By default, HOSA itself is a Prometheus endpoint and will collect its own metrics and store them (see config.yaml for its endpoints definitions). So by running HOSA you will automatically start getting "prometheus" data stored into your H-Metrics. You can add more endpoint definitions to the config to tell HOSA to collect from your own Prometheus and Jolokia-JMX endpoints.
You don't have to use docker - if you build the go executable locally (git clone the HOSA repo and "make build") you can run the executable directly. But it's easier to just docker run - no need to git clone, no need to install Go, no need to build anything.
1 week, 6 days
TRUSTWORTHY CRYPTO // BTC // USDT // RECOVERY SERVICE VISIT iFORCE HACKER RECOVERY
by Mike Thomas
Hi, I’m Mike Thomas, and I want to share how iForce Hacker Recovery helped me after I fell victim to a clever online scam. I thought I was tech savvy, but a fake rep from a major tech company tricked me into giving away sensitive info. My finances and identity were at risk, and I felt helpless. Then I found iForce Hacker Recovery. Their team was reassuring, knowledgeable, and guided me through every step of regaining control. I'm truly grateful they turned a nightmare into hope.
Contact iForce Hacker Recovery:
Email: iforcehk(a)consultant.com
WhatsApp: +1 (240) 803-3706
Website: iforcehackers.wixsite.com
2 weeks
MOST RELIABLE CRYPTOCURRENCY RECOVERY COMPANIES Call iFORCE HACKER RECOVERY
by Carol Beckett
In a vulnerable moment, I found myself targeted by blackmailers threatening to expose sensitive information. Fortunately, I discovered iForce Hacker Recovery, a professional service dedicated to cybersecurity and digital safety. Their expertise not only helped secure my data but also provided critical guidance on confronting the blackmailers. Thanks to their intervention, I regained control and peace of mind, turning a distressing situation into a lesson in resilience.
Website: https://iforcehackers.com
Email: iforcehk(a)consultant.com
WhatsApp: +1 240-803-3706
2 weeks, 1 day
FAST, SECURE AND RELIABLE CRYPTO RECOVERY SERVICES CONTACT BYTEPHANTOM CYBER RECOVERY
by Mihai Pope
I’ll never forget the sound of my coffee mug clinking against the desk as I sat down this morning. It was supposed to be an ordinary day. I opened my laptop, typed in my password, and waited for my wallet balance to appear. But instead of the familiar numbers, there was nothing. Zero. At first, I laughed nervously. It had to be a glitch. I refreshed the page, my finger trembling against the mouse. Refresh. Again. Again. But the emptiness didn’t change. My heart started to pound so loudly I could hear it echoing in my ears. I whispered out loud, almost like a prayer: “No… no, please… not this.” The room felt colder, the walls closing in on me. My coffee sat untouched, steam fading away as if mocking the warmth that had just drained from my body. I had been scammed. My crypto was gone. The apartment feels different now. Quiet, heavy, suffocating. I used to play music while I cooked dinner, but now the silence is unbearable. My phone buzzes with messages from friends, but I can’t bring myself to answer. What would I even say? I lie awake at night, staring at the ceiling, the shadows from the streetlight dancing across the walls. Every time I close my eyes, I see that empty wallet balance. My stomach twists, my chest aches. Shame clings to me like a second skin. I spent hours today scouring forums and websites. The same words keep coming up: “Once your crypto is gone, it’s gone forever.” That phrase feels like a knife twisting deeper into me each time I read it. In my desperation, I stumbled upon something called BytePhantom Cyber Recovery. I wanted to believe, but doubt immediately crept in. Was this just another cruel trick? Another illusion to take what little I had left? Still… I bookmarked the page. I told myself I’d sleep on it. But who am I kidding? I haven’t truly slept in weeks. I did it. I reached out to BytePhantom. My palms were sweating as I typed my story, my eyes burning from holding back tears. I expected them to reply with canned promises or fake reassurances. But they didn’t. Instead, they asked me to breathe. To tell them everything, from the start. And they listened. Really listened. The way they explained their process was so calm, so detailed, so human. For the first time since this nightmare began, I felt like I wasn’t completely alone in it. The BytePhantom team keeps me updated. They send me progress reports, screenshots, explanations of the blockchain paths they’re tracing. I don’t fully understand the technical side, but I understand their effort—and their determination. Each update is like a candle in a dark room. I feel my chest loosen, just a little. I even managed to eat a proper meal today without that heavy lump in my throat. Some days are harder than others. I still wake up with my heart racing, half-convinced it’s all over. But then I see their messages—patient, steady, unwavering. It amazes me that strangers on the other side of a screen care enough to fight for me like this. It feels like having guardians in the shadows, pulling me back from a cliff I almost fell off. I’ll remember this day for the rest of my life. I was sitting at the same desk where all this began, the same desk where I first saw the nightmare unfold. My phone buzzed. A message. My hands shook as I opened it “We’ve successfully recovered your funds.” I gasped so hard it hurt. I opened my wallet, my eyes blurring with tears. And there it was—my crypto. Back. Real. Solid. I burst into tears. Not quiet tears, but loud, raw sobs that shook my body. I fell back into my chair, hands covering my face, crying until I couldn’t breathe. Relief, gratitude, disbelief—all crashing over me in waves. I refreshed the page over and over, afraid it would vanish again. But it didn’t. It was real. It’s been two weeks since the recovery. I still wake up and check my wallet first thing, just to be sure. Each time I see the balance, I whisper a quiet “thank you.” BytePhantom didn’t just recover my stolen crypto—they gave me back something I thought I’d lost forever: my peace of mind, my belief in justice, and my faith that even in the darkest tunnels, there’s still light at the end. If you’re reading this and you’re where I was—broken, ashamed, hopeless—please don’t give up. I know the pain. I know the silence of sleepless nights. But I also know this: recovery is possible. BytePhantom turned my nightmare into a testimony. And I will carry that gratitude with me for the rest of my life.
2 weeks, 6 days
