Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Mon, 20 May 2024 15:42:29 +0000
[Locked] - Alerts
View Count: 1438
| [2018-05-01 19:15:58] |
| conr - Posts: 204 |
|
I referred to you Time&Sales and Alerts doc and still not sure what's going on. I'm getting multiple alerts for the same condition. Also in the Alert Manager, should all the alerts I have set up be showing under Symbol Alerts? Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) | Alert sound queue is full. Queue size: 24 Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) Time and Sales Alert: ESM8 [M] 5 Min #5 | Volume is Equal or Greater then 199 | Alert: sold (3) |
| [2018-05-01 19:37:14] |
| |
|
This does not seem unusual. Based on the Time and Sales Combining option you are using and the trading activity, you can have many alerts like this. Also in the Alert Manager, should all the alerts I have set up be showing under Symbol Alerts? No.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-05-01 19:52:49] |
| conr - Posts: 204 |
|
Okay then I need to change my settings. I believe you made some changes to T&S is that correct? I noticed that my filters were not working the way I hade them originally configured. I have 3 t&s widows set up for ES. I had one set for vol >= 10, another at 50>=, and the last one at 199>=. Then recently I noticed they were all letting all volume go through. Also I never had multiple alerts sent for the 199>= condition, only a single alert. For example. Just now at 14:48 there was a print of235 and the alert went off repeatedly where in the past it was just once.
|
| [2018-05-02 18:18:03] |
| |
|
OK we now understand the reason for the problem. This will be solved in the next release. Also I never had multiple alerts sent for the 199>= condition, only a single alert. We will look into this.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-05-02 19:26:59] |
| |
|
We do observe the multiple alert issue but nothing has changed from what we can tell which would cause this. It would seem to have always been the case. But we can see how it is a problem, so we are figuring out a solution.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-10-18 04:08:09] |
| abn2609 - Posts: 15 |
|
Has this been fixed? I'm getting the same issue too, with alerts ringing way too many times for a single trigger. It is getting annoying. Also, back to time&sales, I have a few questions: 1. What do the volume numbers represent for an exchange like Bitmex? Say BTC perpetual swap. The exchange trades with USD, so I expect to see 100k, 200k, 1M USD etc, but I see figures that look more like coins, single digits and decimals...but they're not even the correct conversion from USD to BTC. 2. Going into settings and using filtering or highlight&alert, what values am I supposed to put in here? What is the base currency going to be? USD or BTC? I doubt it's BTC in this field as you can't even put a decimal in the filtering. After a bit of testing, it doesn't look like either one is correct. This may relate to q 1. The value to enter in the field should be the same base as the values you see on the time&sales print! I shouldn't have to do some weird conversion first before selecting the value. Really needs some consistency here. I'm a new user, and for something that should be straight-forward, this is confusing as hell. |
| [2018-10-18 10:33:58] |
| |
|
There was a Time and Sales alert issue resolved relating to alerts being triggered more often than should have been. So update to the current version: Software Download: Fast Update When entering a Volume/Quantity in the Time and Sales settings where you would input one of those values, you just use numbers that correspond to the Volume field in the Time and Sales records list. And in the case of XBT contracts on BitMex they represent Satoshi units. There is no relationship to a quantity of a contract and a quote currency. Those are unrelated to each other. I'm a new user, and for something that should be straight-forward, this is confusing as hell. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-10-22 23:25:13
|
| [2018-10-18 11:54:39] |
| abn2609 - Posts: 15 |
|
There was a Time and Sales alert issue resolved relating to alerts being triggered more often than should have been. So update to the current version:
Software Download: Fast Update Still happening after update. When entering a Volume/quantity in the settings where you would input one of those values, you just use numbers that correspond to the Volume field in the Time and Sales list. And in the case of XBT contracts on BitMex they represent Satoshi units.
No, I am seeing USD now, not Satoshi. But I am happy with this because at least it now matches the exchange. However, if I try a different instrument, like ETHUSD perpetual swap, the prints are still in some other base that does not correspond to the Volume field in T&S. Please look into this. More products with the same issues: BTCUSD BITFINEX (Prints are in btc which match exchange, but settings fields are in a different base) Please look into this. We think you are confusing yourself.
No. Date Time Of Last Edit: 2018-10-18 13:50:29
|
| [2018-10-22 22:29:13] |
| abn2609 - Posts: 15 |
|
Hi everyone, Any updates? |
| [2018-10-22 22:58:47] |
| |
|
Still happening after update. We need very very clear details on specifically what you are referring to, and how you are coming to that conclusion. We do not believe there is any problem with time and sales alerts at this time.However, if I try a different instrument, like ETHUSD perpetual swap, the prints are still in some other base that does not correspond to the Volume field in T&S. Please look into this. More products with the same issues: BTCUSD BITFINEX (Prints are in btc which match exchange, but settings fields are in a different base) Please look into this. In general we understand what is meant by the term print. It usually is referring to a trade. But what are you referring to. Are you referring to the price, are you referring to the quantity, and what about those and what is the context. And what is the specific question. We have no idea what you are referring to here. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-10-22 23:03:14
|
| [2018-10-22 23:28:49] |
| |
|
At this point contact BitMex with your questions. The volumes and prices that you see in Sierra Chart from BitMex are as they are provided from BitMex. Your questions are not within the scope of Sierra Chart support and we are declining any questions about Bitfinex data. This thread is now locked. If there is an issue with time and sales alerts, make certain that you can thoroughly explain that with a high degree of detail to us and we will have a look at that but start a new thread. And it is very very very doubtful to us there remains a problem. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-10-22 23:29:42
|
To post a message in this thread, you need to log in with your Sierra Chart account: