Topic: MiningMonitor.com - Monitoring - SMS Notifications - Analytics[Monthly+CSV] (Read 9428 times)
December 22, 2012, 12:14:51 AM
Seems not
October 20, 2012, 10:15:23 AM
Is this service still alive?
September 19, 2011, 03:30:59 PM
I will put my entire cluster network on your service for a month. This may be what I have been needing to keep my network working.
.
.
August 25, 2011, 04:03:06 AM
At MiningMonitor.com, we seem to be on a pool adding spree!
rfcpool.com Support added
http://staticcdn.miningmonitor.com/rfcpool.png
As requested, support for rfcpool.com has been added!
OZCO.in Support added
http://staticcdn.miningmonitor.com/ozco.png
As requested, support for OZCO.in has been added!
As usual, thanks to all our users and please keep the suggestions coming!
Peter Azuolas
rfcpool.com Support added
http://staticcdn.miningmonitor.com/rfcpool.png
As requested, support for rfcpool.com has been added!
OZCO.in Support added
http://staticcdn.miningmonitor.com/ozco.png
As requested, support for OZCO.in has been added!
As usual, thanks to all our users and please keep the suggestions coming!
Peter Azuolas
August 22, 2011, 02:32:20 AM
Sunday Feature Push!
ABCPool.co Now Supported
http://staticcdn.miningmonitor.com/abcpool.png
As requested by a user, ABCPool.co is now supported
BTCPool24 Now Supported
http://staticcdn.miningmonitor.com/btcpool24.png
As requested by a user, ABCPool.co is now supported
Worker Up notifications removed
As requested
As usual, thanks to all our users!
Peter Azuolas
ABCPool.co Now Supported
http://staticcdn.miningmonitor.com/abcpool.png
As requested by a user, ABCPool.co is now supported
BTCPool24 Now Supported
http://staticcdn.miningmonitor.com/btcpool24.png
As requested by a user, ABCPool.co is now supported
Worker Up notifications removed
It would be nice if we didn't get "worker up" notifications for linked workers. For example, when I fallover from 1 pool to another, I do not need to be notified.
As requested
As usual, thanks to all our users!
Peter Azuolas
August 08, 2011, 11:22:56 AM
It would be nice if we didn't get "worker up" notifications for linked workers. For example, when I fallover from 1 pool to another, I do not need to be notified.
August 07, 2011, 10:12:27 PM
As requested, we bring you some new features on a sunday!
Monthly Stats
http://staticcdn.miningmonitor.com/monthly_export.png
Now, you can view your overall monthly stats.
Track your day by day performance and compare it to your historical data.
CSV Export
http://staticcdn.miningmonitor.com/export.png
When viewing your overall monthly, or daily stats, you can now download a CSV export of the data.
Perform your own analysis on the data with shares,stales,uptime,hashrate, and earnings all broken down on an hour by hour basis.
---
As usual, we thank all our members and keep the suggestions coming!
Peter Azuolas
Monthly Stats
http://staticcdn.miningmonitor.com/monthly_export.png
Now, you can view your overall monthly stats.
Track your day by day performance and compare it to your historical data.
CSV Export
http://staticcdn.miningmonitor.com/export.png
When viewing your overall monthly, or daily stats, you can now download a CSV export of the data.
Perform your own analysis on the data with shares,stales,uptime,hashrate, and earnings all broken down on an hour by hour basis.
---
As usual, we thank all our members and keep the suggestions coming!
Peter Azuolas
August 01, 2011, 12:18:56 PM
monthly/overall stats
+1. And/or csv export for stats. I'd even upgrade to platinum for that
August 01, 2011, 05:34:24 AM
monthly/overall stats
July 26, 2011, 03:32:45 AM
Monday is a good day for more features!
Arsbitcoin Support added
http://staticcdn.miningmonitor.com/arsbitcoin.png
As requested by multiple people, support for Arsbitcoin has been added
Beta MiningMonitor API
http://staticcdn.miningmonitor.com/apikey.png
You can now get information about your account , current pricing, and your quickstats from our JSON api. You can get your API key on your settings page
---
As usual, thanks to all our members! Keep the suggestions coming!
Peter Azuolas
Arsbitcoin Support added
http://staticcdn.miningmonitor.com/arsbitcoin.png
As requested by multiple people, support for Arsbitcoin has been added
Beta MiningMonitor API
http://staticcdn.miningmonitor.com/apikey.png
You can now get information about your account , current pricing, and your quickstats from our JSON api. You can get your API key on your settings page
---
As usual, thanks to all our members! Keep the suggestions coming!
Peter Azuolas
July 25, 2011, 06:12:47 AM
Please add support for ArsBitcoin. Thanks!
July 21, 2011, 04:01:49 PM
Still no monthly, overall stats, wut?
July 21, 2011, 01:09:17 PM
Feature Request: Tabular output. It would be nice to get most of the information MiningMonitor has in tabular form so that we can do our own analyses in Excel, etc.
I am thinking:
Date TotalShares StaleShares BTCEarned AverageHash Difficulty(at noon) and MtGox(at noon)
Or something like that.
Thoughts?
I am thinking:
Date TotalShares StaleShares BTCEarned AverageHash Difficulty(at noon) and MtGox(at noon)
Or something like that.
Thoughts?
I prefer CSV but yeah, it would be the tits to have export data.
July 21, 2011, 09:45:53 AM
Feature Request: Tabular output. It would be nice to get most of the information MiningMonitor has in tabular form so that we can do our own analyses in Excel, etc.
I am thinking:
Date TotalShares StaleShares BTCEarned AverageHash Difficulty(at noon) and MtGox(at noon)
Or something like that.
Thoughts?
I am thinking:
Date TotalShares StaleShares BTCEarned AverageHash Difficulty(at noon) and MtGox(at noon)
Or something like that.
Thoughts?
July 20, 2011, 09:38:48 PM
Sure. On MM, other pools (such as bitclockers) supports having multiple workers within each pool. This allows you to aggregate all of the workers from the pool together.
I wouldn't mind being able to create an "Eligius Pool" and then adding several wallet addresses as worker inside that pool. Right now, each worker is his own pool.
I wouldn't mind being able to create an "Eligius Pool" and then adding several wallet addresses as worker inside that pool. Right now, each worker is his own pool.
Ok I see what you mean. The problem with that is the API key for Eligius is the worker address. I'm sure Pete can create a workaround for that issue
July 20, 2011, 09:17:15 PM
Excellent! I am glad to see that added.
For consistency with the other pools, would it make more sense to have the Eligius API key (BTC address) as a worker property, not the pool? It would be nice if I could make an "Eligius Pool" (without any API information) and then added several workers (BTC adddresses). One of the major drawbacks of Eligius is that it does not support multiple workers. If MiningMonitor could add multiple workers to the Eligius pool I could keep an eye on aggregated stats.
Dan
For consistency with the other pools, would it make more sense to have the Eligius API key (BTC address) as a worker property, not the pool? It would be nice if I could make an "Eligius Pool" (without any API information) and then added several workers (BTC adddresses). One of the major drawbacks of Eligius is that it does not support multiple workers. If MiningMonitor could add multiple workers to the Eligius pool I could keep an eye on aggregated stats.
Dan
I think it would be as simple as having multiple wallet addresses, one per worker, and then naming the pools accordingly. So that you would have N-eligius-pools for however many workers you are using. Then you would get an email about whatever pool is offline, as each eligius pool is only capable of one worker/wallet address.
I was thinking if the Eligius pools could have sub-workers for each wallet address. That appears to be how the other pools work.
Not sure how that would work. Can you explain in more detail?
Sure. On MM, other pools (such as bitclockers) supports having multiple workers within each pool. This allows you to aggregate all of the workers from the pool together.
I wouldn't mind being able to create an "Eligius Pool" and then adding several wallet addresses as worker inside that pool. Right now, each worker is his own pool.
July 20, 2011, 07:27:17 PM
Excellent! I am glad to see that added.
For consistency with the other pools, would it make more sense to have the Eligius API key (BTC address) as a worker property, not the pool? It would be nice if I could make an "Eligius Pool" (without any API information) and then added several workers (BTC adddresses). One of the major drawbacks of Eligius is that it does not support multiple workers. If MiningMonitor could add multiple workers to the Eligius pool I could keep an eye on aggregated stats.
Dan
For consistency with the other pools, would it make more sense to have the Eligius API key (BTC address) as a worker property, not the pool? It would be nice if I could make an "Eligius Pool" (without any API information) and then added several workers (BTC adddresses). One of the major drawbacks of Eligius is that it does not support multiple workers. If MiningMonitor could add multiple workers to the Eligius pool I could keep an eye on aggregated stats.
Dan
I think it would be as simple as having multiple wallet addresses, one per worker, and then naming the pools accordingly. So that you would have N-eligius-pools for however many workers you are using. Then you would get an email about whatever pool is offline, as each eligius pool is only capable of one worker/wallet address.
I was thinking if the Eligius pools could have sub-workers for each wallet address. That appears to be how the other pools work.
Not sure how that would work. Can you explain in more detail?
July 20, 2011, 06:41:26 PM
Excellent! I am glad to see that added.
For consistency with the other pools, would it make more sense to have the Eligius API key (BTC address) as a worker property, not the pool? It would be nice if I could make an "Eligius Pool" (without any API information) and then added several workers (BTC adddresses). One of the major drawbacks of Eligius is that it does not support multiple workers. If MiningMonitor could add multiple workers to the Eligius pool I could keep an eye on aggregated stats.
Dan
For consistency with the other pools, would it make more sense to have the Eligius API key (BTC address) as a worker property, not the pool? It would be nice if I could make an "Eligius Pool" (without any API information) and then added several workers (BTC adddresses). One of the major drawbacks of Eligius is that it does not support multiple workers. If MiningMonitor could add multiple workers to the Eligius pool I could keep an eye on aggregated stats.
Dan
I think it would be as simple as having multiple wallet addresses, one per worker, and then naming the pools accordingly. So that you would have N-eligius-pools for however many workers you are using. Then you would get an email about whatever pool is offline, as each eligius pool is only capable of one worker/wallet address.
I was thinking if the Eligius pools could have sub-workers for each wallet address. That appears to be how the other pools work.
July 20, 2011, 03:22:10 PM
Excellent! I am glad to see that added.
For consistency with the other pools, would it make more sense to have the Eligius API key (BTC address) as a worker property, not the pool? It would be nice if I could make an "Eligius Pool" (without any API information) and then added several workers (BTC adddresses). One of the major drawbacks of Eligius is that it does not support multiple workers. If MiningMonitor could add multiple workers to the Eligius pool I could keep an eye on aggregated stats.
Dan
For consistency with the other pools, would it make more sense to have the Eligius API key (BTC address) as a worker property, not the pool? It would be nice if I could make an "Eligius Pool" (without any API information) and then added several workers (BTC adddresses). One of the major drawbacks of Eligius is that it does not support multiple workers. If MiningMonitor could add multiple workers to the Eligius pool I could keep an eye on aggregated stats.
Dan
I think it would be as simple as having multiple wallet addresses, one per worker, and then naming the pools accordingly. So that you would have N-eligius-pools for however many workers you are using. Then you would get an email about whatever pool is offline, as each eligius pool is only capable of one worker/wallet address.
July 20, 2011, 01:33:33 PM
Excellent! I am glad to see that added.
For consistency with the other pools, would it make more sense to have the Eligius API key (BTC address) as a worker property, not the pool? It would be nice if I could make an "Eligius Pool" (without any API information) and then added several workers (BTC adddresses). One of the major drawbacks of Eligius is that it does not support multiple workers. If MiningMonitor could add multiple workers to the Eligius pool I could keep an eye on aggregated stats.
Dan
For consistency with the other pools, would it make more sense to have the Eligius API key (BTC address) as a worker property, not the pool? It would be nice if I could make an "Eligius Pool" (without any API information) and then added several workers (BTC adddresses). One of the major drawbacks of Eligius is that it does not support multiple workers. If MiningMonitor could add multiple workers to the Eligius pool I could keep an eye on aggregated stats.
Dan
Jump to: